[LLVMdev] llvm with non-standard gcc location

[Rafael Ávila de Espíndola]

On 2010-12-28 18:00, Martin Schubert wrote:
> Hi all,
> I'd like to use LLVM 2.8 on a openSUSE 10.3 box and when I try to
> compile anything I get an error:

Can you try trunk? I think this has been solved (for this config).

> martin at vm:~/project/backend> clang tutorial001.m -v -emit-llvm -o
> tutorial001
> clang version 2.9 (trunk 122601)
> Target: x86_64-unknown-linux-gnu
> Thread model: posix
> "/usr/local/llvm/Debug+Asserts/bin/clang" -cc1 -triple
> x86_64-unknown-linux-gnu -emit-llvm-bc -disable-free -main-file-name
> tutorial001.m -mrelocation-model static -mdisable-fp-elim -masm-verbose
> -mconstructor-aliases -munwind-tables -target-cpu x86-64
> -target-linker-version 2.17.50.20070726 -v -resource-dir
> /usr/local/llvm/Debug+Asserts/bin/../lib/clang/2.9 -ferror-limit 19
> -fmessage-length 178 -fgnu-runtime -fdiagnostics-show-option
> -fcolor-diagnostics -o /tmp/cc-3mbwGS.o -x objective-c tutorial001.m
> clang -cc1 version 2.9 based upon llvm 2.9svn hosted on
> x86_64-unknown-linux-gnu
> #include "..." search starts here:
> #include <...> search starts here:
>   /usr/local/include
>   /usr/local/llvm/Debug+Asserts/bin/../lib/clang/2.9/include
>   /usr/include
> End of search list.
> "/usr/bin/ld" --eh-frame-hdr -m elf_x86_64 -dynamic-linker
> /lib64/ld-linux-x86-64.so.2 -o tutorial001 /usr/lib/../lib64/crt1.o
> /usr/lib/../lib64/crti.o crtbegin.o -L -L/../../../../lib64
> -L/lib/../lib64 -L/usr/lib/../lib64 -L/../../.. /tmp/cc-3mbwGS.o -lgcc
> --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s
> --no-as-needed crtend.o /usr/lib/../lib64/crtn.o
> /usr/bin/ld: crtbegin.o: No such file: No such file or directory
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
>
> I did some research already and if I understand it correctly the problem
> is a non-standard gcc location (/usr/lib64/gcc/x86_64-suse-linux/4.2.1).
> As I did not find any simple solution for this problem I was hoping that
> this mailing list might be the right place to get some suggestions on
> how to fix it.
>
> Thank you!
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev