This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: should libgcc depend on libc?
- From: Richard Henderson <rth at redhat dot com>
- To: Thorsten Glaser <tg at 66h dot 42h dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 11 Jul 2005 09:41:12 -0700
- Subject: Re: should libgcc depend on libc?
- References: <Pine.BSO.4.63L.0507091946350.9470@odem.66h.42h.de>
On Sat, Jul 09, 2005 at 07:48:47PM +0000, Thorsten Glaser wrote:
> Should I really not use -nostandardlibs for libgcc_s ?
Yes, I'm pretty sure you should not do that.
> I just got a linker warning because I had bumped libc
> from .36.1 to .37.0 and am recompiling gcc... this
> yields executables linking against libgcc_s (.1.1)
> and libc (.37.0 AND .36.1). No problems, but a warning.
Welcome to the pain of bumping so versions.
> Also, libgcc could be used with libc-replacements this
> way (not truly an issue with libgcc.so, but think of
> bootloaders).
>
> Do I overlook something?
Static linking? That would seem to be standard-operating procedure
with bootloaders.
r~