On Tue, 19 Jul 2005, Richard Atterer wrote:

> On Mon, Jul 18, 2005 at 07:55:59PM -0400, Robert P. J. Day wrote:

> > and after the configure, i seem to have a valid PPC curl executable,
> > with the following shared lib references:
> >
> > $ ppc_8xx-ldd curl
> > libcurl.so.3 => not found
> > libssl.so.4 =>
> > /usr/local/eldk3.1.1/ppc_8xx/usr/lib/libssl.so.4
>
> Note that due to your use of -rpath, these paths to the libraries
> are now _hardwired_ into the executable. This is probably not a good
> idea; it means that on the machine where you actually run the curl
> executable, the libs must be in exactly the same spot, they can't be
> e.g. in /usr/lib.

hmmmm ... i'm not convinced. in a project i'm working on, i created a
PPC executable, vtcp:

  $ ppc-linux-ldd vtcp
  libc.so.6 => /usr/local/eldk3.1.1/ppc_8xx/lib/libc.so.6
  ld.so.1 => /usr/local/eldk3.1.1/ppc_8xx/lib/ld.so.1
  $

note how the library references appear to be hard-coded but those
libraries are certainly not in that location on the target system, and
the executable runs fine. (LD_LIBRARY_PATH is being used to locate
libraries on the target system.)

i might have to ask more questions about the whole issue of library
location when cross-compiling.

rday
Received on 2005-07-19