Some libraries are not found without LD_LIBRARY_PATH mangling

[Alexander Neundorf]

On Sunday 28 October 2007, Andras Mantia wrote:
> On Sunday 28 October 2007, Alexander Neundorf wrote:
> > Objections against making this the default behaviour and removing the
> > option ? (otherwise it will always break if a library links to
> > another library which is in a directory which is not in the RPATH of
> > the executable (which doesn't link directly to that library) and
> > which could only be found by the RPATH of the library)
>
> As I wrote in the other mail, here the problem isn't exactly what you
> described. The executable link to a library  - which is in its RPATH -
> which links to another library - which is also in the RPATH of the
> executable -, still this second library is not found by the executable,
> because the first library doesn't have any RPATH entries.
> If -DKDE4_USE_ALWAYS_FULL_RPATH=ON would fix this issue as well

Yes, it should, please verify.

But I don't really understand the behaviour. It worked for the tests I did. I 
noticed it works different under FreeBSD, where the libs must have RPATH, 
there they don't "reuse" the RPATH from the executable.

Can somebody please shed some light on this ?

Alex