This is the mail archive of the
mailing list for the binutils project.
Re: compile failure due to undefined symbol
- From: "Peter S. Mazinger" <ps dot m at gmx dot net>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: Alan Modra <amodra at bigpond dot net dot au>, <binutils at sourceware dot org>
- Date: Wed, 3 Oct 2007 09:42:21 +0200 (CEST)
- Subject: Re: compile failure due to undefined symbol
On Tue, 2 Oct 2007, Peter S. Mazinger wrote:
> > But I was able to use it as the basis for a patch which did work. Would you
> > like to try it out and see what you think ? (The patch is attached, but I have
> > not included the regenerated files. I assume that you are OK to recreate them
> > yourself). I chose to use -rpath rather than -rpath-link and then to
> > explicitly link into the shared bfd library rather than using the library
> > location mechanism as this appeared to do the right thing.
Works for me too with 2.18 for i686-*-linux-gnu/ and 2.17 for
Is -Wl,-z,defs supported everywhere?
> I assume you checked that using -rpath has really the correct
> RPATH/RUNPATH in opcodes/.libs/libopcodes.so and in the finally installed
> one in --libdir or whatever.
I checked, there is no hardcoded RUNPATH/RPATH in the intermediate/final
shared libraries, so that should be fine
> Wondering if SHARED_DEPENDENCIES should be bfd/libbfd.la, that is for sure
> a target in the Makefiles and implies the creation of the needed
> libbfd.so, meaning also that the bfd directory is "finalized", I am
> sure about bfd/.libs/libbfd.so being a good target.
I have used SHARED_DEPENDENCIES pointing to `pwd`/../bfd/libbfd.la
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2