[LLVMbugs] [Bug 21172] New: Executables built with `make check` not embedding library paths (-Wl, -R) like the rest of the build

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=21172

            Bug ID: 21172
           Summary: Executables built with `make check` not embedding
                    library paths (-Wl,-R) like the rest of the build
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: phantall+llvm at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

../src/configure --with-gcc-toolchain=/path/to/gcc/install
gmake -j9
gmake -j9 check

The 3rd step fails on any platform where the system install of libstdc++ is not
new enough (eg., RHEL 6.2).

I tried the following workaround, but it seems LDFLAGS isn't being used by
`make check`:

gcc_path=/path/to/gcc/install
../src/configure --with-gcc-toolchain=${gcc_path} LDFLAGS="-L${gcc_path}/lib
-L${gcc_path}/lib64 -Wl,-R${gcc_path}/lib -Wl,-R${gcc_path}/lib64"

My current workaround for this is to set LD_LIBRARY_PATH as follows (but only
for the `make check` step; everything that gets installed seems to be in good
shape):

LD_LIBRARY_PATH=${gcc_path}/lib:${gcc_path}/lib64:${LD_LIBRARY_PATH} gmake -j9
check

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141006/c55c8389/attachment.html>