[LLVMbugs] [Bug 9576] New: clang -no-canonical-prefixes breaks build

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon Mar 28 14:51:29 PDT 2011


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

           Summary: clang -no-canonical-prefixes breaks build
           Product: clang
           Version: unspecified
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: nobled at dreamwidth.org
                CC: llvmbugs at cs.uiuc.edu


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)

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the llvm-bugs mailing list