[LLVMbugs] [Bug 8509] New: clang should support compiling drizzle

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Fri Oct 29 11:44:47 PDT 2010


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

           Summary: clang should support compiling drizzle
           Product: clang
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: C++
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: mordred at inaugust.com
                CC: llvmbugs at cs.uiuc.edu, dgregor at apple.com


Hi!

I was hoping I could just write a note saying that I'd gotten Drizzle
(http://drizzle.org) compiling with clang... but I'm down to one final issue
that seems to be a clang/boost issue. (This is all on 64-bit Ubuntu 10.10)

I fixed a bunch of tiny little bugs in Drizzle that clang found, but then at
the final link step I get:


drizzled/current_session.o:(.gnu.linkonce.r._ZTVN5boost19thread_specific_ptrIN8drizzled7SessionEE11delete_dataE+0x20):
undefined reference to
`boost::thread_specific_ptr<drizzled::Session>::delete_data::operator()(void*)'
collect2: ld returned 1 exit status
clang: error: linker (via gcc) command failed with exit code 1 (use -v to see
invocation)

(This does not happen with normal gcc boost)

I followed the instructions on the site for building clang from latest trunk
and then building boost from trunk.

BTW - I also had a problem with boost::regex not building under clang because
of wide string crud - so I added:
#define BOOST_NO_WREGEX
to boost/config/compiler/clang.hpp

Then I also built google protocol buffers (since that's another c++  library
dependency) and then followed:

http://wiki.drizzle.org/Compiling

Except I did:

CC=clang CXX=clang++ ./configure

If we can get this working, I'm going to add a clang-based drizzle build to our
hudson setup...

-- 
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