Stas Sergeev wrote:
The kernel header package that originally came with the version of
Slackware I was using would always solve the problems for me.
That's true and that's the 2.4 headers,
but can you comment on this wrt compiling
dosemu:
On Wed, 13 Jul 2005, Stas Sergeev wrote:
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
Hello.
Bart Oldeman wrote:
Maybe add the proper headers to the
dosemu source tree as we did before?
The question is which headers?
I think some of them can be located if
you symlink the kernel headers and try
to compile. Of course it is not guaranteed
to be all of them, but better than
Hello.
Hufnus wrote:
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/
http://ep09.pld-linux.org/%7Emmazur/linux-libc-headers/
Yes, that's the correct headers,
but unfortunately it doesn't
Stas Sergeev wrote:
those:( So the original suggestion
still stays - using the slackware
package of the 2.4 headers will work
the best:(
Yes. I think the thing is (I've also had this myself), that when
updating a kernel on Slackware, many people just download all the tgz
files from the
Hello.
Julius Schwartzenberg wrote:
The kernel header package that originally came
with the version of Slackware I was using would always solve the
problems for me.
That's true and that's the 2.4 headers,
but can you comment on this wrt compiling
dosemu:
Hufnus wrote:
Anybody runing 1.3.2 or trying with Linux 2.6
I can compile 1.3.2 with gcc 3.3.4 and Linux 2.4 headers,
and run it on Linux 2.6.7, but it has some keyboard press
problems. The same dosemu.bin works fine with our apps
in 2.4.31, though!
So I tried to compile with Linux 2.6.7
On Tue, 12 Jul 2005 12:07:21 -0800
Hufnus [EMAIL PROTECTED] wrote:
Anybody runing 1.3.2 or trying with Linux 2.6
So I tried to compile with Linux 2.6.7 headers, but the make
gets some obsolete warnings and then fails with many parse errors
in /usr/include/linux/mod_devicetable.h
Hufnus wrote:
On Tue, 12 Jul 2005 12:07:21 -0800
Hufnus [EMAIL PROTECTED] wrote:
Anybody runing 1.3.2 or trying with Linux 2.6
So I tried to compile with Linux 2.6.7 headers, but the make
gets some obsolete warnings and then fails with many parse errors
in
On Tue, 12 Jul 2005 22:58:32 +0200
Maciek Stopa [EMAIL PROTECTED] wrote:
Hufnus wrote:
On Tue, 12 Jul 2005 12:07:21 -0800
So I tried to compile with Linux 2.6.7 headers, but the make
gets some obsolete warnings and then fails with many parse errors
in /usr/include/linux/mod_devicetable.h
On Tue, 12 Jul 2005, Hufnus wrote:
On Tue, 12 Jul 2005 12:07:21 -0800
Hufnus [EMAIL PROTECTED] wrote:
Anybody runing 1.3.2 or trying with Linux 2.6
So I tried to compile with Linux 2.6.7 headers, but the make
gets some obsolete warnings and then fails with many parse errors
in
Bart Oldeman wrote:
This is not its default symbolic link. You must have created it yourself,
manually.
I had a problem with compiling Dosemu on Slackware also at some point.
That symlink turned out to be the problem. I believe Stas Sergeev
pointed me at it.
It hadn't created the symlink
On Wed, 13 Jul 2005 11:35:03 +1200 (NZST)
Bart Oldeman [EMAIL PROTECTED] wrote:
On Tue, 12 Jul 2005, Hufnus wrote:
On Tue, 12 Jul 2005 12:07:21 -0800
Hufnus [EMAIL PROTECTED] wrote:
Anybody runing 1.3.2 or trying with Linux 2.6
So I tried to compile with Linux 2.6.7
On Tue, 12 Jul 2005, Hufnus wrote:
Looking at those kernel headers vs the kernel distribution ones,
I guess that should work. Unfortunately I am usually in a higher
kernel than Slackware-current is, so always get in trouble.
Yes, but the deal is: that should not matter! In Slackware you
Bart Oldeman wrote:
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
On Wed, 13 Jul 2005 13:44:33 +1200 (NZST)
Bart Oldeman [EMAIL PROTECTED] wrote:
No, those are not the /usr/include/linux headers, the ones you are
talking about are those in include/linux in the kernel source code.
Maybe the kernel guys will pick that change up, if it carries no
other
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...
If some distro really does
17 matches
Mail list logo
