This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Build problem with 4.8.0 RC-20130316 and in-tree binutils
- From: Ian Lance Taylor <iant at google dot com>
- To: Matt Godbolt <matt at godbolt dot org>
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 20 Mar 2013 06:42:52 -0700
- Subject: Re: Build problem with 4.8.0 RC-20130316 and in-tree binutils
- References: <CAFWXXN1NQVQyfzAN3W85aZz6mwmQtAEL2z2BammvmzMiHQutKw at mail dot gmail dot com> <CAKOQZ8xnUmuveTTXzmnHPd-D0h=o=86X0Buwz46C=T+dX9UCdg at mail dot gmail dot com> <CAFWXXN1hSi+TSHTu2z879nV5jPXyuDv-etbPhu4YTRUtLDbrHw at mail dot gmail dot com>
On Wed, Mar 20, 2013 at 6:36 AM, Matt Godbolt <matt@godbolt.org> wrote:
>
> Thanks for the quick reply. I definitely have --enable-shared set in
> the configuration, and had so with 4.7. However I'm not certain that
> previously a system-installed libbfd.so et al were causing my build to
> succeed (for the wrong reason).
>
> I'll try a build without --enable-shared and see if that works. What
> does this flag do: I couldn't find any reference to it on
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html or in
> ./configure --help - I must have picked it up from the seed set of
> configure options I cribbed from the Ubuntu-built gcc.
The --enable-shared option is the default for GCC.
The libstdc++ manual only lists the configure options that are
specific to libstdc++, as it says in the second paragraph on the web
page you cite. The --enable-shared option for GCC is documented at
http://gcc.gnu.org/install/configure.html .
The --enable-shared option is not the default for the various
binutils. Using --enable-shared when building the binutils causes
them to use a shared libbfd and libopcodes. This is documented in
binutils/README.
When using an in-tree build you get a mix of the GCC and binutils
configure options. This approach must be used with care.
Ian