In-Reply-To: <1080604519.32741.8.camel@minerva>
References: <5516F046-81C1-11D8-A0A8-000A959DCC8C@sonous.com> <Pine.LNX.4.53.0403291602340.2893@chaos>  <20040329222710.GA8204@DervishD> <1080604519.32741.8.camel@minerva>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <75D673FF-81DE-11D8-A0A8-000A959DCC8C@sonous.com>
Content-Transfer-Encoding: 7bit
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
       DervishD <raul@pleyades.net>, linux-kernel@vger.kernel.org
From: Lev Lvovsky <lists1@sonous.com>
Subject: Re: older kernels + new glibc?
Date: Mon, 29 Mar 2004 16:09:06 -0800
To: Matthew Reppert <repp0017@tc.umn.edu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 961
Lines: 29


On Mar 29, 2004, at 3:55 PM, Matthew Reppert wrote:
>
> See http://www.kernelnewbies.org/faq/index.php3#headers
>
> The correct place, I've read, to get the headers for the current 
> running
> kernel is /lib/modules/$(uname -r)/build/include ... which of course
> assumes that you keep your kernel in the same place you built it from,
> but that's not a worse assumption than whatever you'd assume for
> /usr/include/{linux,asm} symlinks to work I'm sure.
>
> Basically, the potential problem as I understand it is binary
> incompatibility with the currently installed glibc.
>
> Matt

http://www.ussg.iu.edu/hypermail/linux/kernel/0007.3/0587.html

beautiful, this answers all questions :)

thanks everyone!
-lev

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/