similar to: [LLVMdev] native libraries

Hi Ryan, On Sat, 2007-03-31 at 18:33 -0500, Ryan M. Lefever wrote: > In a previous post (included at the end of the message), Reid stated > that in August 2006, llvm-ld did not support native libraries. I have a > few questions about that. Is it still true that llvm does not support > native libraries? Furthermore, what exactly is meant by that? llvm-ld has been worked on (by

Hi, I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC 3.3.6). When issuing the following command (line 14 in a script called manual.sh): llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB -load=${MY_LIB_DIR}/opt1.so -load=${MY_LIB_DIR}/opt2.so -debug-pass=Details -debug -o test ... I get the following

Hi Bram, Comments inline .. On Wed, 2006-08-16 at 18:01 +0200, Bram Adams wrote: > Hi, > > I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC > 3.3.6). When issuing the following command (line 14 in a script called > manual.sh): > > llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L > ${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB

I'm experiencing an issue when compiling R packages containing c++ code inside a sandbox on linux. The problem is caused by the fact that g++ does not seem to inherit the TMPDIR environment variable from the R process. When creating the shared on library, it tries to write a file under /tmp (instead of $TMPDIR). If /tmp is not writable, this causes the package build to fail. I am personally

Hi, Op 16-aug-06, om 18:59 heeft Reid Spencer het volgende geschreven: >> llvm-ld: warning: Supposed library 'SOME_OTHER_LIB' isn't a library. > > The -l option is used to link libraries into the resulting executable. > I'm hoping "SOME_OTHER_LIB" is not the actual name and you're just > paraphrasing the actual command line. Note that native