Problematic linking between glibc and shared libgcc

Eric W. Biederman ebiederm@xmission.com
Mon Feb 19 11:40:00 GMT 2001


Fergus Henderson <fjh@cs.mu.oz.au> writes:

> 
> However, touching /lib when --prefix=/usr would go against the
> documentation for --prefix.  Rather than doing that, I think configure
> should just print a big warning in that case (when --prefix=/usr
> and --slibdir is not set explicitly).  There should be another option
> that you can select which will put it in /lib.  Perhaps the
> combination `--prefix=/usr --slibdir=/lib' would suffice for that,
> although I don't think that will do the right thing with symlinks,
> and in any case it might be nicer to have a single option for
> configuring gcc as the "native" compiler.  The installation
> documentation and the warning for --prefix=/usr should both
> mention this option.
> 
> Does that sound like a good approach?

It sounds close.  But the problem is not so much as making gcc the
native compiler, but as making programs compiled with gcc native
programs.  A big fat warning about it is definitely in the right
direction.  

If you recompile and install a system binary (/bin/sh perhaps) with gcc
and then reboot you need a clue why it didn't work.

Eric



More information about the Gcc mailing list