public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Nielsen <lovechild@foolclan.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] linux-headers ebuild version.
Date: 20 Jun 2003 22:34:57 +0200	[thread overview]
Message-ID: <1056141297.1570.4.camel@pilot.stavtrup-st.dk> (raw)
In-Reply-To: <200306202240.54694.svyatogor@gentoo.org>

I had countless problems getting stuff to compile against 2.5 because of
2.4 headers being present in /usr/lib - this madness has to end, is
there no sane solution to this crap, basically we risk breaking
something at near random when we upgrade the kernel just because some
header changed and some program makes an assumption that is wrong like a
struct that has changed - right?

we need a sane way to work around this - I remember Martin Schlemmer 
once proposing a kernel API to make sure we always had a sane way of
working with the kernel without including kernel headers in userspace
which is the cause of many a problem.

- Lovechild

On Sat, 2003-06-21 at 00:40, Svyatogor wrote:
> On Friday 20 June 2003 19:25, Martin Schlemmer wrote:
> >
> > Anyhow, in general in Gentoo, if you compile something like iptable,
> > nvidia-kernel, alsa, etc, it use the kernel headers in /usr/src/linux,
> > as it is easier to manage (say you are running kernel from livecd,
> > but want to compile whatever for your kernel that you will be
> > booting ...).
> Exactly, so it shouldn't be installing the headers in /usr/include/linux, 
> which is what linux-headers does.


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-20 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 20:20 [gentoo-dev] linux-headers ebuild version Svyatogor
2003-06-20 18:03 ` Chris PeBenito
2003-06-20 19:25   ` Martin Schlemmer
2003-06-20 22:40     ` Svyatogor
2003-06-20 20:34       ` David Nielsen [this message]
2003-06-20 21:04         ` Adam Trilling

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=1056141297.1570.4.camel@pilot.stavtrup-st.dk \
    --to=lovechild@foolclan.com \
    --cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox