search for: llvm_cv_oppath

...y Linux box it does not set RPATH when building LLVM as static > libraries. I do not have cmake installed - and when packaging for NetBSD (IIRC) you need to explicitly tell it that cmake is used, which I haven't done - so I'd have to answer "no". I do see LIBS="$LIBS -L${llvm_cv_oppath} -Wl,-rpath,${llvm_cv_oppath}" in autoconf/configure.ac, and hardcode_libdir_flag_spec'${wl}-rpath ${wl}$libdir' and hardcode_libdir_flag_spec_ld='-rpath $libdir' in configure, though. Do these need to be there? Tim

"Larson, Timothy E." <TELarson at west.com> writes: > Hello LLVM devs, > > I am trying to package llvm for NetBSD. The package checker scripts > are complaining about bad rpaths in the binaries. I see that they are > relative to the build directory. I have no idea why that would be. > Can you explain? Are you using cmake for building LLVM? If the answer is

Hello LLVM devs, I am trying to package llvm for NetBSD. The package checker scripts are complaining about bad rpaths in the binaries. I see that they are relative to the build directory. I have no idea why that would be. Can you explain? If I build as myself, for testing (e.g.): $ readelf -d ~/downloads/llvm-2.6/Release/bin/llvm-ar Dynamic section at offset 0x15af28 contains 25 entries:

.../libopagent.{a,so}. This isn't on the loader's default search path, even if <prefix>==/usr, so to link with the .so we also need a -rpath flag to the linker. To avoid that, I'm tentatively using the .a. In configure, behind a --with-oprofile argument, I have: LIBS="$LIBS ${llvm_cv_oppath}/libopagent.a -lbfd -liberty -ldl" This causes llvm-config to print: $ ./Debug/bin/llvm-config --libs --ldflags --cxxflags -L/usr/local/google/jyasskin/llvm/oprof/dbg/Debug/lib -lpthread -lffi -ldl -lm /usr/local/lib/oprofile/libopagent.a -lbfd -liberty -ldl -I/usr/local/google/jyasskin/llv...