Dosemu 1.3.2 and linux 2.6.7 headers
Quoted 1 line · Bart Oldeman
This is not its default symbolic link. You must have created it yourself, manually.
Hi Bart, actually I've seen such
a problem with Slackware in many different places, so I am starting to beleive it really uses a symlink. I remember Patrick Volkerding claimed in that very list that Slackware doesn't do this, but it looks like it was changed, or at least there is some bug...
If some distro really does this, then rooting out this tendency among users is going to be really troublesome:( And some people claim that even installing the 2.6 headers from the slackware package still gives an error! And only that the 2.4 headers work properly.
Maybe add the proper headers to the dosemu source tree as we did before? We can convince people to use the proper headers by answering the same question over and over again, but we really can't change the distribution.
Quoted 5 lines · On Wed, 13 Jul 2005 07:47:43 +0400 Stas Sergeev <[email protected]> wrote:
to beleive it really uses a symlink. I remember Patrick Volkerding claimed in that very list that Slackware doesn't do this, but it looks like it was changed, or at least there is some bug...
Quoted 8 lines
If some distro really does this, then rooting out this tendency among users is going to be really troublesome:( And some people claim that even installing the 2.6 headers from the slackware package still gives an error! And only that the 2.4 headers work properly.
After some googling I think I finally found the correct linux-libc-headers (as they are now called).
http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
So I will splice these to my devel box and see if 1.3.2 works better with Linux 2.6.7 (It does not work too bad with the 2.6.7 Kernel headers on 2.6.7, but not as well as with the 2.4.31 headers and kernel 2.4.31)
The thing about Slackware is that they stuck with the 2.4 kernel for a long time, since very conservative. It was just now that they have an alternate 2.6 kernel in the distribution and note that it is an alternate! So I have been using plain 2.6 kernel headers for 2.6 development (dangerous, but most of time works for my purposes) but now I am going to switch to the libc headers or "sanitized kernel headers", since they seem robust enough and I am now aware of them...
TonyB
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / [email protected] \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
Quoted 2 lines · Stas Sergeev
Maybe add the proper headers to the
dosemu source tree as we did before?
The question is which headers? Many headers include some linux/*.h file but it seems that only sys/pci.h is problematic. It's easy to get rid of that #include by simply putting some extra #define's in our src/include/pci.h.
But then is it just sys/pci.h? I mean sys/pci.h is undocumented as far as I can see (neither "info libc" nor man pages seem to mention it), but the same is true for sys/soundcard.h, sys/vt.h, sys/kd.h and perhaps some others. All goes to show that grepping headers isn't a good way to obtain "documentation"...
The LSB contains a really clean header system. But that's *too* clean for dosemu, as things like vm86 and *mntent functions are missing,
Bart