cross compiling shared libraries leaves host RPATH's in them?

[Leon Woestenberg]

Hello,

when building shared libraries in a cross-compile environment, I notice
that my libraries pick up some host RPATH.

This causes overhead (I see an strace of 15 bogus lookups) and a
security hole if the path includes /tmp/.

What's the proper way to build shared libraries so that their RPATH
matches the installation destination?

Regards,

Leon Woestenberg.

--
For unsubscribe information see http://sourceware.org/lists.html#faq