[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dlopen on Solaris compared with IRIX/Tru64

From: Tom Kacvinsky
Subject: Re: dlopen on Solaris compared with IRIX/Tru64
Date: Wed, 20 Dec 2000 14:01:17 -0500 (EST)

Huh?  My experience (on Solaris) has been that if has an embedded RPATH
and the application bar uses and also has a RPATH, then the binary's
RPATH is used for shared lib lookups.  If the RPATH of the binary does not
include the paths in the shared lib's RPATH, then the shared lib's dependencies
are not met. :( Or maybe I am consfusing myself.  Perhaps this is Tru64 UNIX's

Anyway, I guess I am talking about run-time linking, and not use of dlopen.
Or is the bahvior the same?


On Wed, 20 Dec 2000, Bjoern Fischer wrote:

> Hello Albert,
> > dependent on nothing:
> >   $ ldd
> > =>     (file not found)
> This is your problem. Your is not self-contained.
> The run-time linker is not able to resolve all dependencies
> of your You may set LD_LIBRARY_PATH, but you
> definetly want to fix your to contain an DT_RPATH
> for
> > This program works just fine on IRIX 6.5 and Compaq Tru64 UNIX 5.0.
> > The failure above is on Solaris 2.5.1-8/SPARC.
> That's irony! The Platforms Tru64 and IRIX are more or less broken
> with respect to run-time linking resp. dlopen():
> The creator of really knows what other libraries png
> depends on and where to find them. This knowledge should be
> incorprated into, so the run-time linker will be able
> to find all libs and resolve all symbols. Solaris' run-time
> linker only uses the RPATH found in to find libs,
> that png depends on. IRIX and True64 use a globalized RPATH
> in the executable binary for all library searches, which is
> wrong.
>   Bjoern

reply via email to

[Prev in Thread] Current Thread [Next in Thread]