clang -no-canonical-prefixes breaks build

[llvmbot]

Bugzilla Link	9576
Resolution	FIXED
Resolved on	Jun 16, 2017 19:16
Version	trunk
OS	Linux
Reporter	LLVM Bugzilla Contributor
CC	@zmodem,@petrhosek

Extended Description

Tested with clang 2.8 packaged on Ubuntu 10.10.

This works:

$ clang++ test.cpp -c -o test.o
"/usr/bin/clang" -cc1 -triple i386-pc-linux-gnu -S -disable-free -disable-llvm-verifier -main-file-name test.cpp -mrelocation-model static -mdisable-fp-elim -mconstructor-aliases -target-cpu pentium4 -target-linker-version 2.20.51 -v -resource-dir /usr/lib/clang/2.8 -ferror-limit 19 -fmessage-length 80 -fexceptions -fgnu-runtime -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/cc-yDvkea.s -x c++ test.cpp
clang -cc1 version 2.8 based upon llvm 2.8rc hosted on i386-pc-linux-gnu
ignoring nonexistent directory "/usr/include/c++/4.4/x86_64-linux-gnu/32"
[...]

This fails spectacularly:

$ clang++ -v -no-canonical-prefixes test.cpp -c -o test.o
clang version 2.8 (branches/release_28)
Target: i386-pc-linux-gnu
Thread model: posix
"clang++" -cc1 -triple i386-pc-linux-gnu -S -disable-free -disable-llvm-verifier -main-file-name test.cpp -mrelocation-model static -mdisable-fp-elim -mconstructor-aliases -target-cpu pentium4 -target-linker-version 2.20.51 -v -resource-dir /lib/clang/2.8 -ferror-limit 19 -fmessage-length 80 -fexceptions -fgnu-runtime -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/cc-Wq7xzv.s -x c++ test.cpp
clang++: error: clang frontend command failed with exit code 127 (use -v to see invocation)

[llvmbot]

I just built clang/llvm from SVN (r128412), and ran make install - the same problem happens. The -resource-dir parameter is all wrong, but in a slightly different way from 2.8.

$ clang++ -v test.cpp -c -o test.o
clang version 3.0 (trunk)
Target: i386-pc-linux-gnu
Thread model: posix
"/usr/local/bin/clang" -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name test.cpp -mrelocation-model static -mdisable-fp-elim -masm-verbose -mconstructor-aliases -target-cpu pentium4 -target-linker-version 2.20.51 -momit-leaf-frame-pointer -v -resource-dir /usr/local/bin/../lib/clang/3.0 -ferror-limit 19 -fmessage-length 80 -fcxx-exceptions -fexceptions -fgnu-runtime -fdiagnostics-show-option -fcolor-diagnostics -o test.o -x c++ test.cpp
clang -cc1 version 3.0 based upon llvm 3.0svn hosted on i386-pc-linux-gnu
ignoring nonexistent directory "/usr/include/c++/4.4/x86_64-linux-gnu/32"
[...]

$ clang++ -v -no-canonical-prefixes test.cpp -c -o test.o
clang version 3.0 (trunk)
Target: i386-pc-linux-gnu
Thread model: posix
"clang++" -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name test.cpp -mrelocation-model static -mdisable-fp-elim -masm-verbose -mconstructor-aliases -target-cpu pentium4 -target-linker-version 2.20.51 -momit-leaf-frame-pointer -v -resource-dir ../lib/clang/3.0 -ferror-limit 19 -fmessage-length 80 -fcxx-exceptions -fexceptions -fgnu-runtime -fdiagnostics-show-option -fcolor-diagnostics -o test.o -x c++ test.cpp
clang++: error: unable to execute command: No such file or directory
clang++: error: clang frontend command failed due to signal 1 (use -v to see invocation)

[zmodem]

Just ran into this. The error message may have changed slightly over time, but this sounds like the same problem:

$ PATH=/work/llvm/build.release/bin clang -no-canonical-prefixes -v -c /tmp/a.c
clang version 5.0.0 (trunk 304237) (llvm/trunk 304250)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /work/llvm/build.release/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8.4
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.3
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@MX32
Selected multilib: .;@m64
"clang" -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name a.c -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -v -dwarf-column-info -debugger-tuning=gdb -coverage-notes-file /work/llvm/a.gcno -resource-dir lib/clang/5.0.0 -internal-isystem /usr/local/include -internal-isystem lib/clang/5.0.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdebug-compilation-dir /work/llvm -ferror-limit 19 -fmessage-length 80 -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -o a.o -x c /tmp/a.c
clang: error: unable to execute command: Executable "clang" doesn't exist!

Without -no-canonical-prefixes, it works fine.

[zmodem]

Petr fixed this in r305600.

[llvmbot]

mentioned in issue llvm/llvm-bugzilla-archive#9646