rpath

Sun Jun 25 13:07:00 GMT 2000

On 2000年6月25日, Jeff Sturm wrote:
> Tom Tromey wrote:
> > I seem to remember that there is a reason we don't want to do this.
> > Can somebody refresh my memory as to what it is? If so I will add a
> > note to the FAQ about it.
>> It's a tradeoff. It is easier to install and use multiple builds of
> gcj/libgcj if I compile with -rpath so I am not overriding
> LD_LIBRARY_PATH each time. But my -rpath directory is probably
> meaningless to anyone else who wants to run one of my gcj-compiled
> binaries.

Where is the tradeoff? If -rpath is set then it will be found by
the runtime linker. If the shared lib is not where the -rpath says
it is, then rld could still search on the LD_LIBRARY_PATH. Why
only support the LD_LIBRARY_PATH option?

> It is also a simple matter to set LD_LIBRARY_PATH at login, or (on
> Linux) edit my /etc/ld.so.conf. It also seems likely that standard
> Linux distributions will eventually install libgcj.so in a system
> directory. We probably should have a FAQ entry for this.

It should be a simple matter to compile something and then run it.
Why should I have to go set env vars just so that I can run
an executable? It does not matter how simple some other step
might be, why should we require that people do it?
Mo DeJong
Red Hat Inc