mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Lev Lvovsky <lists1@sonous.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: older kernels + new glibc?
Date: Tue, 30 Mar 2004 07:19:09 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403300717440.5144@chaos> (raw)
In-Reply-To: <35350CCA-81D4-11D8-A0A8-000A959DCC8C@sonous.com>

On Mon, 29 Mar 2004, Lev Lvovsky wrote:

>
> On Mar 29, 2004, at 2:10 PM, Richard B. Johnson wrote:
> > You didn't care to read what I said? I said to remove those sym-links.
> > They must be replaced by headers that were in-use around the time
> > the C library code was compiled, preferably the exact same headers.
> >
> > There must not be any sym-link in the /usr/include/... directories
> > pointing to any kernel headers. That way, you can add new kernels
> > without ever screwing up your compiler.
>
> Understood.  Incidentally, the glibc-kernheaders package included with
> RH 7.3 creates those files as symlinks, I'm sure however that they were
> there for the compilation of glibc.  The disconnect that I forsee, is
> that I will be running the 2.2.26 with kernel headers from a 2.4.x
> kernel - would this be the correct thing to do?

To be absolutely sure you don't end up making user-mode code that
doesn't work, I would remove those sym-links and replace them with
the actual headers that are known to work.

>
> I suppose I mirror the sentiments of DervishD on this from his post.
>
> -lev
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-03-30 12:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 20:40 Lev Lvovsky
2004-03-29 21:00 ` Arjan van de Ven
2004-03-29 21:09   ` Lev Lvovsky
2004-03-29 21:22     ` Arjan van de Ven
2004-03-29 21:26       ` Lev Lvovsky
2004-03-29 21:28         ` Arjan van de Ven
2004-03-29 21:34           ` Lev Lvovsky
2004-03-29 21:36             ` Arjan van de Ven
2004-03-29 21:45             ` Chris Meadors
2004-03-29 23:03             ` David T Hollis
2004-03-30 15:07       ` Adrian Bunk
2004-03-31  0:54         ` GOTO Masanori
2004-03-29 21:17 ` Richard B. Johnson
2004-03-29 21:36   ` Lev Lvovsky
2004-03-29 21:50     ` Richard B. Johnson
2004-03-29 21:55       ` Lev Lvovsky
2004-03-29 22:10         ` Richard B. Johnson
2004-03-29 22:55           ` Lev Lvovsky
2004-03-30 12:19             ` Richard B. Johnson [this message]
2004-03-29 22:27   ` DervishD
2004-03-29 23:55     ` Matthew Reppert
2004-03-30  0:09       ` Lev Lvovsky
2004-03-30 14:50       ` DervishD
2004-03-30 15:15         ` Richard B. Johnson
2004-03-30 17:10           ` DervishD
2004-03-30 12:16     ` Richard B. Johnson
2004-03-30 15:20       ` DervishD

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=Pine.LNX.4.53.0403300717440.5144@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists1@sonous.com \
    /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

all inboxes | Powered by JetHome®