This is a discussion on zipslack(2.0.37pre10) and /sys/io.h within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi, This particular version of Slackware was recommended as Parapin(circlemud.org)-friendly. But the parapin-0.96 Makefile(v.1.14) couldn't find include/sys/io.h, so I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, This particular version of Slackware was recommended as Parapin(circlemud.org)-friendly. But the parapin-0.96 Makefile(v.1.14) couldn't find include/sys/io.h, so I copied one over from my RedHat80 box. Now when I make I get the following: gcc -DPARAPIN_LINUX -O2 -g -Wall -c parapin.c In file included from parapin-linux.h:68, from parapin.c:109: /usr/include/sys/io.h:34: parse error before `__THROW' /usr/include/sys/io.h:34: warning: data definition has no type or storage class /usr/include/sys/io.h:39: parse error before `__THROW' /usr/include/sys/io.h:39: warning: data definition has no type or storage class parapin-linux.h: In function `pin_init_user': In file included from parapin.c:109: parapin-linux.h:198: warning: implicit declaration of function `ioperm' make: *** [parapin.o] Error 1 Am I using the wrong sys/io.h? If so, where can I get the right one? Thanks, Gil |
| |||
| Gil wrote : > But the parapin-0.96 Makefile(v.1.14) couldn't find include/sys/io.h, If you want to compile stuff yourself you'll have to install the glibc package. -- Thomas O. This area is designed to become quite warm during normal operation. |
| ||||
| In article <5l84b1-ka1.ln1@news.inet.tele.dk>, Thomas Overgaard wrote: >> But the parapin-0.96 Makefile(v.1.14) couldn't find include/sys/io.h, > > If you want to compile stuff yourself you'll have to install the glibc > package. Since that was Slackware 3.9, libc5-based, I'd say probably not. Perhaps the kernel source or kernel headers package? In those days I think the latter was called "include.tgz". -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |