rpath'd binaries

Hello!

I noticed that the binaries of all llvm tools contain an rpath to
$OBJDIR/Release/bin. I just only learned about rpaths, but the
way I understand them this would only make sense if that path
would contain shared libraries, which it doesn't. Especially it
makes no sense if I install the binaries and delete the build
directory (where it potentially even leaves a security issue
behind). Am I missing something, or can I safely adjust
Makefile.rules to not use any rpath?

Thanks,
jlh

Hi jlh,

Hello!

I noticed that the binaries of all llvm tools contain an rpath to
$OBJDIR/Release/bin. I just only learned about rpaths, but the
way I understand them this would only make sense if that path
would contain shared libraries, which it doesn't.

That's not entirely true. Its possible to build with shared libraries,
its just not the default method.

Especially it
makes no sense if I install the binaries and delete the build
directory (where it potentially even leaves a security issue
behind). Am I missing something, or can I safely adjust
Makefile.rules to not use any rpath?

I agree. I'm currently revising the makefile system to deal with this
issues, and numerous other issues. What we need to do is use libtool
more effectively so that the build binaries have rpath to the build area
but installed binaries have either no rpath (static link) or an rpath to
the installed libraries (shared libs link).

You can probably fix this yourself in Makefile.rules, but we'll be
converting to the revised makefile system in the coming month or two.
You can track the progress of the new system by watching the commits on
the support module in the SVN repository.

Reid.