Fileutils compilation problem

Lesende, Emiliano - (Ext Arg) Emiliano.Lesende at
Wed Jul 11 08:40:47 PDT 2001

I have built an LFS system following the instructions on the CVS book. I
gcc-3.0 and glibc-2.2.3. All the software was optimized with -O3 and
except mawk. It's running over a week whitout a single crash. No single
has segfaulted on me.

IMHO, people who want to build his/her own linux system, wants total control
total freedom. I dont think we should take that away from them beacouse we
that it isn't very stable. May we add both compilation instructions?
GCC-2.95.2 and
GCC-3.0? Let the final user choose which one.

Thanks for reading 

-----Mensaje original-----
De: Gerard Beekmans [mailto:gerard at]
Enviado el: Miércoles, 11 de Julio de 2001 12:05 p.m.
Asunto: Re: Fileutils compilation problem

> But now I'm confronted with what looks like a unsolved problem : after
> recompiling dynamically fileutils, I got an error configuring the next
> program (grep), a seg fault while testing ls -t. So I got back to
> fileutils, recompiled it in the basic env (a Mandrake 7.2 with Gcc
> 2.95.3 and Glibc 2.1.3, after throwing away a Mdk 8.0 with that $%*#&{
> Gcc 2.96). Then I got back ls working. But the problem remains.
> What can I do for this one ? Looks like a Glibc problem, doesn't it ?

It does yes. The CVS book uses gcc-3.0 and glibc-2.2.3. They aren't too
stable yet, especially gcc-3.0. It'll be better to replace gcc-3.0 with
gcc- and glibc-2.2.3 with glibc-2.2.1 - ala the 3.0-pre4 book.
The CVS book is not very usable at this moment to build a stable system
Gerard Beekmans

-*- If Linux doesn't have the solution, you have the wrong problem -*-
Unsubscribe: send email to lfs-discuss-request at
and put unsubscribe in the subject header of the message
Este mensaje es confidencial. El mismo contiene información reservada 
y que no puede ser difundida. Si usted ha recibido este e-mail 
por error, por favor avísenos inmediatamente vía e-mail y tenga la 
amabilidad de eliminarlo de su sistema; no deberá copiar el mensaje 
ni divulgar su contenido a ninguna persona. Muchas gracias.
This message is confidential. It contains information that is privileged and
legally exempt from disclosure. If you have received this e-mail by mistake,

please let us know immediately by e-mail and delete it from your system; 
you should also not copy the message nor disclose its contents to anyone. 
Thank You.

Unsubscribe: send email to lfs-discuss-request at
and put unsubscribe in the subject header of the message

More information about the lfs-dev mailing list