This is the mail archive of the
mailing list for the GCC project.
Re: Link tests after GCC_NO_EXECUTABLES
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Bernd Schmidt <bernds_cb1 at t-online dot de>
- Cc: Mark Mitchell <mark at codesourcery dot com>, Jie Zhang <jzhang918 at gmail dot com>, gcc at gcc dot gnu dot org, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 28 Nov 2007 01:10:15 +0000 (UTC)
- Subject: Re: Link tests after GCC_NO_EXECUTABLES
- References: <46EFBCC1.firstname.lastname@example.org> <46EFC383.email@example.com> <46EFC9E9.firstname.lastname@example.org> <46EFCEF9.email@example.com> <46EFCF7A.firstname.lastname@example.org> <46EFD236.email@example.com> <46EFDA4D.firstname.lastname@example.org> <474C0C52.email@example.com> <474C8FA4.firstname.lastname@example.org> <474C95BA.email@example.com> <474C96C1.firstname.lastname@example.org> <474C98AA.email@example.com>
On Tue, 27 Nov 2007, Bernd Schmidt wrote:
> We have two uses for the bfin-elf compiler - building standalone
> applications, and bootstrapping uClibc for
> bfin-uclinux/bfin-linux-uclibc. For the latter, we need -mfdpic and
> -mid-shared-library multilibs, to at least get a libgcc. This always
> worked since what is now "-msim" was default behaviour, but it started
> to fail the libstdc++ configury once Jie changed that to use
> target-specific linker scripts.
When you are building a compiler to bootstrap libc, with a view to
building a later full toolchain using that libc, the bootstrap compiler
should be C-only (and have most of the other runtime libraries apart from
libgcc disabled), so you only build libstdc++ after you have a libc.
The only exception would be if your libc contains C++ code and depends on
libstdc++ - I think this has been mentioned as an issue for Cygwin.
Joseph S. Myers