Re: LD_RUN_PATH not adding paths when building with shared libs

[Bill Moseley]

On Thu, Aug 28, 2003 at 05:36:50PM -0500, Tim Mooney wrote:

> Are you assuming LD_RUN_PATH is something that's honored on IRIX because
> you've seen it honored on other platforms (e.g. Solaris?).  If you've
> seen it documented somewhere that it should work on IRIX, can you provide
> information on where I should look?

Tim,

You are right.

I just got a reply back and they built a hello world program and used 
LD_RUN_PATH and strings(1) didn't show the path.

The original problem was the built binary was not finding libgcc.  The
first solution was to use LD_RUN_PATH and --disable-shared which worked. 
On linux --disable-shared allowed the use of LD_RUN_PATH (because of
lack of --rpath at link time).  So I assume that's what was happening.

But, on IRIX with --disable-shared libgcc does not show up in ldd
output.

Another solution was to use -R /path/to/libgcc in LDFLAGS.  That also
works at building the program but then libgcc is shown in ldd output
(and they commented they might want to use the binary on another IRIX
machine without libgcc installed).


I don't understand why --disable-shared would make that difference.  
This project uses libtool to create a library, and then links it into 
our program.

I thought --disable-shared prevented the creation of the shared library
(that we are building in our project).  On linux when I use
--disable-shared ldd swish-e no longer shows libswish-e, but that's the
only difference.  So now I wonder why their tests on IRIX showed that
--disable-shared also statically linked in libgcc.

Thanks for your help,


-- 
Bill Moseley
address@hidden