[Lldb-commits] [PATCH] Fix broken test suite on Windows after r223091

Zachary Turner zturner at google.com
Tue Dec 2 15:50:17 PST 2014

I actually get errors when doing this.

'g++' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the file specified.
The system cannot find the file specified.
d:\src\llvm\build\ninja\bin\clang.exe -g -O0 -m32  -fPIC
-Id:/src/llvm/tools/lldb/test/make/../../include   -c -o main.o main.c
d:\src\llvm\build\ninja\bin\clang.exe -g -O0 -m32  -fPIC
-Id:/src/llvm/tools/lldb/test/make/../../include   -c -o foo.o foo.c
d:\src\llvm\build\ninja\bin\clang.exe -g -O0 -m32  -fPIC
-Id:/src/llvm/tools/lldb/test/make/../../include  -fuse-ld=lld foo.o
-shared -o "libfoo.so"
clang.exe: warning: argument unused during compilation: '-shared'
Cannot infer subsystem; assuming /subsystem:console
Undefined symbol: C:\Program Files (x86)\Microsoft Visual Studio
symbol(s) not found
clang.exe: error: linker command failed with exit code 1 (use -v to see
make: *** [libfoo.so] Error 1

This probably hints a deeper issue or just something else I haven't gotten
around to fixing yet (like maybe it's broken for all C files, and only
works for C++).

Just so I understand, is this a location where it's supposed to find system
libraries, like libc or similar?  Or is this for something else?  Clang is
pretty good about automatically finding all required libraries on Windows,
so if it's just for that it might not be needed, but if it's a place we're
putting our own shared libraries, then maybe we do.



More information about the lldb-commits mailing list