Open Quuxplusone opened 10 years ago
Are you sure you are on trunk? That output looks like it came from a version of LLVM pre-r220462.
If you are still having problems, you can try modifying the first line of the test/Bindings/Go/go.test file to look like this:
; RUN: llvm-go test -x llvm.org/llvm/bindings/go/llvm
That should show you the subcommands that the "go" command is running.
(In reply to comment #1)
> Are you sure you are on trunk? That output looks like it came from a version
> of LLVM pre-r220462.
>
> If you are still having problems, you can try modifying the first line of
> the test/Bindings/Go/go.test file to look like this:
>
> ; RUN: llvm-go test -x llvm.org/llvm/bindings/go/llvm
>
> That should show you the subcommands that the "go" command is running.
I was using tags/google/stable/2014-10-28 which corresponds to r220284.
I'll see if it still happens on trunk.
Attached go.test.log
(24199 bytes, text/x-log): Output from llvm-go test -x
Is this:
/work/chromium/src/tools/clang/scripts/../../../third_party/llvm/../llvm-bootstrap-install/bin/clang++
the correct path to the compiler used to build LLVM?
Did you configure cmake to pass any additional flags to the compiler (maybe to link against another standard library?)
(In reply to comment #4)
> Is this:
>
> /work/chromium/src/tools/clang/scripts/../../../third_party/llvm/../llvm-
> bootstrap-install/bin/clang++
>
> the correct path to the compiler used to build LLVM?
Yup.
>
> Did you configure cmake to pass any additional flags to the compiler (maybe
> to link against another standard library?)
Yes, I invoke cmake like this:
cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON -
DLLVM_ENABLE_THREADS=OFF -
DCMAKE_C_COMPILER=/work/chromium/src/tools/clang/scripts/../../../third_party/llvm/../llvm-
bootstrap-install/bin/clang -
DCMAKE_CXX_COMPILER=/work/chromium/src/tools/clang/scripts/../../../third_party/llvm/../llvm-
bootstrap-install/bin/clang++ -DCMAKE_C_FLAGS=--gcc-
toolchain=/work/gcc482prefix -DCMAKE_CXX_FLAGS=--gcc-
toolchain=/work/gcc482prefix -DCMAKE_EXE_LINKER_FLAGS= -
DCMAKE_SHARED_LINKER_FLAGS= -DCMAKE_MODULE_LINKER_FLAGS= -
DCMAKE_INSTALL_PREFIX=/work/chromium/src/tools/clang/scripts/../../../third_party/llvm/../llvm-
build/Release+Asserts -
DCHROMIUM_TOOLS_SRC=/work/chromium/src/tools/clang/scripts/.. '-
DCHROMIUM_TOOLS=plugins;blink_gc_plugin'
/work/chromium/src/tools/clang/scripts/../../../third_party/llvm
The important bit is -DCMAKE_CXX_FLAGS=--gcc-toolchain=/work/gcc482prefix,
which points Clang to a newer GCC than my system one.
This set-up is probably uncommon, so I don't expect anyone to jump through
hoops to accommodate it, I mostly just filed this to keep track of the test
failure.
This should eventually be fixed by passing CMAKE_C*_FLAGS through to where Go
can see them.
In the meantime, you could work around the issue by moving the flag into
$CC/$CXX.
This is now the last test we need to patch around downstream because it doesn't just work.
Attached llvm-gtest.diff
(4397 bytes, text/plain): patch
go.test.log
(24199 bytes, text/x-log)llvm-gtest.diff
(4397 bytes, text/plain)