All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: Header files conflicts
Date: Tue, 23 Mar 1999 09:20:38 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92218116701467@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92212191626693@msgid-missing>

> 
> > 
> > Hello,
> > 
> > The header files in /usr/include/linux seriously conflict with some
> > from glibc-devel-2.0.7-29 in my ultrasparc-I box running UP-1.1.9 and
> > kernel 2.2.4.
> > 
> > Here is a sample example (using <sys/types.h>):
> [...]
> > What may have missed?
> > 
> > Thierry Lafage.
> 
> Here is another example (trying to include <linux/types.h>):

That's what you get on i386 with glibc as well, simply linux/types.h is
incompatible with glibc headers, it has been like that for quite some time.
Generally, you should use glibc headers and if you ever need something from
linux/ headers which include linux/types.h or similar headers, just handle
it somehow. If you look into most low level packages which do this, you'll
see they either use their own copy of kernel headers, thus are independent
on the actual kernel version installed during build (which is a good thing),
or #define some define which will prevent those headers to be included.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux  |  http://ultra.linux.cz/  |  http://ultra.penguin.cz/
Linux version 2.2.3 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________

      parent reply	other threads:[~1999-03-23  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-22 16:43 Header files conflicts Thierry Lafage
1999-03-23  9:11 ` Thierry Lafage
1999-03-23  9:20 ` Jakub Jelinek [this message]

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=marc-linux-ultrasparc-92218116701467@msgid-missing \
    --to=jj@sunsite.ms.mff.cuni.cz \
    --cc=ultralinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.