This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Avoid use of libgcc_s and libgcc_eh when building glibc
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: Thomas Schwinge <thomas at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Fri, 8 Jun 2012 11:42:42 +0000 (UTC)
- Subject: Re: Avoid use of libgcc_s and libgcc_eh when building glibc
- References: <Pine.LNX.4.64.1205282140020.2726@digraph.polyomino.org.uk><20120529235232.E0F742C0B8@topped-with-meat.com><Pine.LNX.4.64.1205301052380.25659@digraph.polyomino.org.uk><877gvt8hi0.fsf@schwinge.name> <87txyoksdr.fsf@schwinge.name><20120606221104.AEA162C096@topped-with-meat.com>
On Wed, 6 Jun 2012, Roland McGrath wrote:
> > I can now do: binutils, GCC "configure --disable-shared --disable-threads
> > --without-headers --with-newlib" [...] complete GCC, [...]
>
> Do any of those configure options affect gcc proper, or only the target
> libraries? That is, is the "complete GCC" step rebuilding the compiler in
> a way that matters, or just completing the build of the target libraries?
At least --disable-shared does affect the specs built in to the GCC
driver.
--
Joseph S. Myers
joseph@codesourcery.com