Re: Build problem with 4.8.0 RC-20130316 and in-tree binutils

[Matt Godbolt <matt at godbolt dot org>]

Hi Ian,

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.

Thanks, Matt

On Wed, Mar 20, 2013 at 8:18 AM, Ian Lance Taylor <iant@google.com> wrote:
> On Wed, Mar 20, 2013 at 5:35 AM, Matt Godbolt <matt@godbolt.org> wrote:
>>
>> I'm having trouble building the RC 4.8.0 with an in-tree binutils on
>> an Ubuntu 12.04 x86_64.  It seems that while building GCC, the runtime
>> library path does not include the objdir/prev-*/.libs directories; so
>> whenever any of the built binutils programs are run they fail as their
>> shared libraries cannot be found. The SOs are built but aren't on the
>> LD_LIBRARY_PATH it seems.
>
> I'm pretty sure that the GCC build never added bfd/.libs or
> opcodes/.libs to LD_LIBRARY_PATH.
>
>> --enable-shared
>
> Are you sure that you used --enable-shared when building GCC 4.7 with
> an in-tree binutils?  That is what is causing your problem; building
> the binutils with --enable-shared is causing them to use a shared
> libbfd and libopcodes, leading to the failure.
>
> Is it possible that the behaviour of --enable-shared has changed for
> the binutils?
>
> Or is it possible that you have an installed libbfd.so and
> libopcodes.so, but not one that is new enough for the in-tree binutils
> you are building?
>
> Ian



-- 
Matt