From: DervishD <disposable1@telefonica.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Compiling glibc
Date: Wed, 11 Aug 2004 12:10:56 +0200 [thread overview]
Message-ID: <20040811101056.GA3673@DervishD> (raw)
Hi all :)
Per section 1.8 of the glibc FAQ, I understand that if I build a
glibc using headers from 2.4.26, it not necessarily will run
correctly on 2.4.27. Is this true or this maybe-incompatibility
applies only for releases and not patchlevels (I mean, compiling in a
2.2.x and running on a 2.4.x)?
I want to build a new version of the glibc (I use 2.2.4 and I
want to upgrade to 2.3.3) and I need the headers of the kernel I'm
running (2.4.26 or .27 in my case) but, where? I mean: should I
install them under /usr/include? Now I have /usr/include/linux and
/usr/include/asm from my old 2.4.10 kernel, back when I built my old
glibc, they're not symlinks to my current kernel headers, as
recommended here a time ago.
I'm not sure if I have to put kernel headers from 2.4.26 in
/usr/include/linux and /usr/include/asm when building the new library
or after building it. In the glibc FAQ I cannot find an answer.
Could anyone help? Any help will be greatly appreciated :) Thanks
a lot in advance.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
reply other threads:[~2004-08-11 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040811101056.GA3673@DervishD \
--to=disposable1@telefonica.net \
--cc=linux-kernel@vger.kernel.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