search for: dlyd_library_path

...ke install PREFIX=...", but that didn't work either. Are there any suggestions on how to get this to work? Also, some questions about llvm-gcc. If we're just installing the binary version, does anything need to be done in order to let llvm find the libraries, such as modifying the DLYD_LIBRARY_PATH, or are all the paths relative? What about for the stuff compiled by llvm-gcc, does that need paths to be set as well? Finally, does llvm require llvm-gcc for it's runtime, as mentioned by GettingStarted.html, or can it be used by itself? If not, does it make sense to package the two in th...

...be (more) gnu-compliant, and make linux packaging much more simple and straightforward. >> Also, some questions about llvm-gcc. If we're just installing the binary >> version, does anything need to be done in order to let llvm find the >> libraries, such as modifying the DLYD_LIBRARY_PATH, or are all the paths >> relative? > > There aren't any shared libraries so the library path doesn't matter. > For llvm-gcc3, the path needs to be able to find gccas and gccld from > the LLVM build. For llvm-gcc4, everything is linked in statically so > after llvm-gcc...

...er override each of these individually on the command line or replace their values in Makefile.config. > Also, some questions about llvm-gcc. If we're just installing the binary > version, does anything need to be done in order to let llvm find the > libraries, such as modifying the DLYD_LIBRARY_PATH, or are all the paths > relative? There aren't any shared libraries so the library path doesn't matter. For llvm-gcc3, the path needs to be able to find gccas and gccld from the LLVM build. For llvm-gcc4, everything is linked in statically so after llvm-gcc4 is built, it doesn't m...

...make linux > packaging much more simple and straightforward. > > > >> Also, some questions about llvm-gcc. If we're just installing the binary > >> version, does anything need to be done in order to let llvm find the > >> libraries, such as modifying the DLYD_LIBRARY_PATH, or are all the paths > >> relative? > > > > There aren't any shared libraries so the library path doesn't matter. > > For llvm-gcc3, the path needs to be able to find gccas and gccld from > > the LLVM build. For llvm-gcc4, everything is linked in statical...