This is a discussion on gcc 3.2.3 inb/outb problem within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I am running slackware 9.1 on a KT4V-L with amd 2200+ and soyo 5ema with amd k6/2-500 gcc compiles ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am running slackware 9.1 on a KT4V-L with amd 2200+ and soyo 5ema with amd k6/2-500 gcc compiles my parallel port driver fine on the latter system but fails on the former with a complaint that its unable to access inb/outb commands. Is this a known problem ? Is there a fix for the KT4V-L system? RAZ |
| |||
| Razzel wrote: > I am running slackware 9.1 on a KT4V-L with amd 2200+ and soyo 5ema with > amd k6/2-500 gcc compiles my parallel port driver fine on the latter > system but fails on the former with a complaint that its unable to > access inb/outb commands. Is this a known problem ? > Is there a fix for the KT4V-L system? > RAZ Are you recompiling your kernel? What do you mean by compiling parallel port driver? You can read a little about inb and outb in the manual (man inb). You still may have a better luck if you post the exact error message. Try to capture it somehow. make | egrep -i "warning|inb|outb" >> errors.txt I think it would not hurt if you post the error message to a Linux drivers/programmer/kernel group. |
| ||||
| "Razzel" typed: > I am running slackware 9.1 on a KT4V-L with amd 2200+ and soyo 5ema > with amd k6/2-500 gcc compiles my parallel port driver fine on the > latter system but fails on the former with a complaint that its > unable to access inb/outb commands. Is this a known problem ? Is > there a fix for the KT4V-L system? Razzel, post back the exact and complete error messages gcc is throwing out. And, also, what arguments are you using with gcc to compile the module? -- Ayaz Ahmed Khan http://fast-ce.org/ayaz/ I was going through some code from 2002, frustrated at the lack of comments, cursing the moron who put this spaghetti together, only to realize later that I was the moron who had written it. -- CowboyRobot wrote on /. |