On 21:20 Fri 24 Dec, Ted Unangst wrote: > Here's what I have. There appears to be an issue where clang doesn't > quite work, because it thinks the next stage is installed in ".". See > below. Otherwise, at least it builds. :) > > /tmp> clang -v t.c > clang version 2.8 (branches/release_28) > Target: i386-unknown-openbsd4.8 > Thread model: posix > "/tmp/clang" -cc1 -triple i386-unknown-openbsd4.8 -S -disable-free > -disable-llvm-verifier -main-file-name t.c -mrelocation-model static > -mdisable-fp-elim -mconstructor-aliases -target-cpu i486 > -target-linker-version 2.15 -v -resource-dir /lib/clang/2.8 -ferror-limit > 19 -fmessage-length 80 -fgnu-runtime -fdiagnostics-show-option > -fcolor-diagnostics -o /tmp/cc-KoUUKA.s -x c t.c > clang: error: unable to execute command: /tmp/clang is not executable > clang: error: clang frontend command failed due to signal 1 (use -v to see > invocation)
I workaround this with a simple script which uses the full path to clang: #!/bin/sh exec /home/proger/dev/llvm/Debug+Asserts/bin/clang $*
