public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Hufnus <tonyb@thekrnl.sysdev.org>
To: linux-msdos@vger.kernel.org
Cc: Maciek Stopa <maciek@genesilico.pl>
Subject: Re: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Tue, 12 Jul 2005 16:15:22 -0800	[thread overview]
Message-ID: <20050712161523.5f58ce04.tonyb@sysdev.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507131122380.31990@enm-bo-lt.localnet>

On Wed, 13 Jul 2005 11:35:03 +1200 (NZST)
Bart Oldeman <bartoldeman@users.sourceforge.net> wrote:

> On Tue, 12 Jul 2005, Hufnus wrote:
> 
> > On Tue, 12 Jul 2005 12:07:21 -0800
> > Hufnus <tonyb@sysdev.org> 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 related to
> > > symbols like__u32 etc....
> > >
> > > Now, if I relink 'ln -sf linux-2.4.31 linux' it still complains
> > > about using -malign-????? is obsolete to use -falign-????? but
> > > it builds fine.
> >
> > I know I am using Skackware's default symbolic link
> > /usr/include/linux -> /usr/src/linux-2.6.7/include/linux !!!
> 
> This is not its default symbolic link. You must have created it
> yourself, manually.
> 
> > My question is what should I do ....
> >
> I've go a deja vu feeling here, this has been discussed before.
> You need to install Slackware's kernel-headers package (it's in the
> d series, over here for instance:
> ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/d/kernel-headers-2.4.31-i386-1.tgz
> They contain sanitized 2.4.31 headers that were used to compile
> glibc, and that is what user space (incl dosemu) sometimes sees
> indirectly.
> 
> Just don't mess with /usr/include/linux, unless you really know
> what you are doing and are willing to recompile glibc.
> 
> Bart

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.

Looking at /usr/include/linux headers, I think there is a bug in
<linux/pci.h>.  It #includes <linux/mod_devicetable.h>, at the
top and outside of an #ifdef __KERNEL__  which is located further
down, where #include <linux/types.h> is also present.  It seems
to me that inside the #ifdef __KERNEL__ is where it should be placed.

I tested just modifying <linux pci.h>, rather than having to modify
/usr/include/linux/mod_devicetable.h and dosemu's src/emu.c to add
the types.h and make it compile correctly and it worked too!

Maybe the kernel guys will pick that change up, if it carries no
other implications ...

TonyB

--
  __      __  _     I N C.               http://www.sysdev.org
/ __|\\// __||  \  __   __          /         tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers


  parent reply	other threads:[~2005-07-13  0:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 20:07 Dosemu 1.3.2 and linux 2.6.7 headers Hufnus
2005-07-12 20:21 ` Maciek Stopa
2005-07-12 20:49 ` Hufnus
2005-07-12 20:58   ` Maciek Stopa
2005-07-12 23:05     ` Hufnus
2005-07-12 23:35   ` Bart Oldeman
2005-07-12 23:43     ` Julius Schwartzenberg
2005-07-13  0:15     ` Hufnus [this message]
2005-07-13  1:44       ` Bart Oldeman
2005-07-13  4:20         ` Hufnus
  -- strict thread matches above, loose matches on Subject: below --
2005-07-13  3:47 Stas Sergeev
2005-07-13  4:36 ` Hufnus
2005-07-13  7:53 ` Bart Oldeman
2005-07-13 15:19 Stas Sergeev
2005-07-13 16:03 Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg
2005-07-14  4:03 Stas Sergeev
2005-07-14 10:01 ` Julius Schwartzenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050712161523.5f58ce04.tonyb@sysdev.org \
    --to=tonyb@thekrnl.sysdev.org \
    --cc=linux-msdos@vger.kernel.org \
    --cc=maciek@genesilico.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox