From: Arjan van de Ven <arjanv@redhat.com>
To: Lev Lvovsky <lists1@sonous.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: older kernels + new glibc?
Date: Mon, 29 Mar 2004 23:36:50 +0200 [thread overview]
Message-ID: <20040329213650.GC26854@devserv.devel.redhat.com> (raw)
In-Reply-To: <D8E351AF-81C8-11D8-A0A8-000A959DCC8C@sonous.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Mon, Mar 29, 2004 at 01:34:23PM -0800, Lev Lvovsky wrote:
>
> On Mar 29, 2004, at 1:28 PM, Arjan van de Ven wrote:
> >>perfect - where does this variable get set? sorry for what now seems
> >>like OT glibc stuff.
> >
> >it's passed to glibc ./configure at build time; if you have an rpm
> >based
> >distro you'll see it in the specfile of the src.rpm
>
> ok, so this presents a bit of a problem in that case (assuming I'm
> understanding you) - I'm working backwards in this respect, as I'm
> using the "new" version of glibc, and an older version of the kernel
> than the one that glibc was told to remain compatible with - the
> important question, is does this order of operations (possibly) break
> things, or does the fact that I compiled the kernel on this new version
> of glibc remove any issues.
glibc will just plain refuse to operate (correctly). glibc makes assumptions
about not needing workarounds for older kernels if you tell it it can assume
a newer kernel...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-29 21:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 20:40 older kernels + new glibc? 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 [this message]
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
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=20040329213650.GC26854@devserv.devel.redhat.com \
--to=arjanv@redhat.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 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.