[LLVMdev] Is the option --enable-shared discontinued in 2.7?
Yuri
yuri at tsoft.com
Tue Apr 27 23:25:24 PDT 2010
Jeffrey Yasskin wrote:
> --enable-shared was _created_ in 2.7. If you were passing it in 2.6 or
> earlier, it wasn't doing what you expected.
>
It's description in online documentation appeared long before 2.7 was
released, which caused me to believe it that this feature was present in
2.6. But I never tied to use the shared library anyway.
> I just tried it again on trunk (not 2.7) on OSX 10.5, and it works.
> What platform are you on? Does it work with another version of gcc?
>
I am on FreeBSD-8.0 i386. I tried it with gcc-4.3.1 and it also breaks
the build:
<...skipped...>
llvm[2]: Linking Release executable llvm-as (without symbols)
/tmp/llvm-build/2.7/llvm-objects/tools/llvm-ranlib/Release/llvm-ranlib.o(.text+0x1fc):
In function `__static_initialization_and_destruction_0(int, int)':
: undefined reference to `vtable for
llvm::cl::opt<std::basic_string<char, std::char_traits<char>,
std::allocator<char> >, false, llvm::cl::parser<std::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >'
/tmp/llvm-build/2.7/llvm-objects/tools/llvm-ranlib/Release/llvm-ranlib.o(.text+0x20b):
In function `__static_initialization_and_destruction_0(int, int)':
: undefined reference to `vtable for
llvm::cl::parser<std::basic_string<char, std::char_traits<char>,
std::allocator<char> > >'
<...skipped...>
Yuri
More information about the llvm-dev
mailing list