glibc configparms file unnecessary
jim at vardus.net
Mon Nov 27 06:19:56 PST 2000
I encountered a compilation error with gcc in chroot build. After tearing a
lot of hair out, losing sleep, etc. I discovered that configparms is spelt
configparms, not configparams. If you don't include configparms when
building glibc for lfs, it *does* install glibc in the wrong place and
subsequently you can't build dynamic binaries in the chroot stage.
This experience confuses me to what exactly you are arguing about. Have you
tried building a LFS without configparms?
----- Original Message -----
From: "Marcel Martin" <mmar at mail.com>
To: <lfs-discuss at linuxfromscratch.org>
Sent: Sunday, November 26, 2000 9:06 PM
Subject: glibc configparms file unnecessary
> from http://www.gnu.org/software/libc/glibc-FAQ.html#13:
> 13. ``How do I configure GNU libc so that the essential libraries like
> libc.so go into /lib and the other into /usr/lib?''
> To install the essential libraries which come with GNU libc in /lib one
> explicitly tell this (except on Linux, see below). Autoconf has no option
> this so you have to use the file where all user supplied additional
> information should go in: `configparms' (see the `INSTALL' file).
> the `configparms' file should contain:
> The first line specifies the directory for the essential libraries, the
> second line the directory for file which are by tradition placed in a
> directory named /etc.
> --> No rule without an exception: If you configure for Linux with
> --> --prefix=/usr, then slibdir and sysconfdir will automatically be
> --> defined as stated above.
> (emph. added)
> The LFS-Book explicitly instructs the reader to create the
> but it seems that this is not necessary. Maybe the instruction to create
> file should be replaced by an explanation why it is not necessary to do
> I hope this issue hasn't been raised before. I'm not subscribed to the
> mailing list, but thought this would be the most appropiate address to
> this note.
> _ _
> / V / Marcel Martin ICQ #83647876
> \ \ mmar at mail.com
> Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the lfs-dev