public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] linux-headers
Date: Wed, 05 Jun 2002 20:01:43 +0200	[thread overview]
Message-ID: <71520000.1023300103@krabat.ahsoftware> (raw)
In-Reply-To: <200206051841.53304.arutha@gmx.de>

Hello,

--On Mittwoch, Juni 05, 2002 18:41:53 +0200 Alexander Gretencord 
<arutha@gmx.de> wrote:

> On Wednesday 05 June 2002 18:03, Brandon Low wrote:
>> The linux headers should only really be changed when you upgrade glibc,
>> otherwise things get out of sync, perhaps we should upgrade the headers
>> automatically in the glibc ebuild from the currently installed kernel.
>
> Right, I think the linux-headers should be no normal package but get
> installed  from the kernel includes that are present when you compile
> glibc. And perhaps  a lil reminder somwhere. Many people don't know that
> it's supposed to be this  way. (e.g. ppl coming from redhat only know
> about symlinks in that dir at  least in 6 it was that way, dunno about 7)

Yes. I've used an old SuSE 7.3 with many packages compiled by myself and 
haven't had any problems up to now. And I'm sure, the glibc was very old 
(so I think it was compiled with a 2.2.x kernel) and last I've used kernel 
2.4.18 with the includes pointing at that kernel.

Why should the usr/include/linux and asm reflect the state at glibc compile 
time? Is there any reading about that?

Alexander




  reply	other threads:[~2002-06-05 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 15:19 [gentoo-dev] linux-headers Alexander Holler
2002-06-05 16:03 ` Brandon Low
2002-06-05 16:41   ` Alexander Gretencord
2002-06-05 18:01     ` Alexander Holler [this message]
2002-06-05 18:16       ` Alexander Gretencord
2002-06-05 16:14 ` Spider

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=71520000.1023300103@krabat.ahsoftware \
    --to=holler@ahsoftware.de \
    --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