public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:28:34 +0200	[thread overview]
Message-ID: <20040329212832.GB26854@devserv.devel.redhat.com> (raw)
In-Reply-To: <ACFAE876-81C7-11D8-A0A8-000A959DCC8C@sonous.com>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]


On Mon, Mar 29, 2004 at 01:26:00PM -0800, Lev Lvovsky wrote:
> On Mar 29, 2004, at 1:22 PM, Arjan van de Ven wrote:
> 
> >On Mon, 2004-03-29 at 23:09, Lev Lvovsky wrote:
> >>We have the source of the drivers, but they are specific to the 2.2.x
> >>kernels.  I am not a kernel hacker, and this would be way beyond my
> >>area of expertise.
> >>
> >>And sadly, this doesn't answer the initial question.
> >
> >then to answer your question; at compile time you tell glibc what
> >minimum kernel version it can assume, and based on that glibc will
> >enable/disable certain features. So it depends on what your distro
> >supplied there if it'll work or not. if you tell glibc that at minimum
> >you do 2.4.1 for example, then no a 2.2 kernel won't work. I think most
> >distros do this (or an even later version) since a few years now.
> 
> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-03-29 21:29 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 [this message]
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
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=20040329212832.GB26854@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox