On Wed, Nov 3, 2010 at 1:05 PM, Renato Botelho <rbgarga_at_gmail.com> wrote: > On Wed, Nov 3, 2010 at 12:44 PM, Ed Schouten <ed_at_80386.nl> wrote: >> * Renato Botelho <rbgarga_at_gmail.com>, 20101103 15:36: >>> On Wed, Nov 3, 2010 at 11:44 AM, Ed Schouten <ed_at_80386.nl> wrote: >>> > Garga! >>> > >>> > * Renato Botelho <rbgarga_at_gmail.com>, 20101103 13:36: >>> >> For now i solve my problem adding this to /etc/src.conf >>> >> >>> >> .if ${.CURDIR} == "/usr/src/gnu/lib/libgcc" >>> >> CC=cc >>> >> CXX=c++ >>> >> .endif >>> >> >>> >> This way libgcc_s.so is built using gcc instead of clang and the problem >>> >> is gone. I just wonder other problems we can find since simething on >>> >> libgcc_s.so is broken when built with clang. >>> > >>> > Would it be hard to figure out which exact object file causes this? >>> >>> Hi Ed, >>> >>> I've submitted a ktrace result of openoffice execution [1], i just >>> saw it got a SIGBUS at some point, but debug openoffice doesn't >>> seem to be a trivial task. >>> >>> I don't know if we can build OO with debug symbols to make it >>> easier to debug. If you know what i can do to help debugging, >>> just let me know and i can provide any information. >> >> Well, I mean, can you build some of libgcc's object files with Clang and >> others with GCC? Hint: Just build everything with GCC. Afterwards, go >> into the object directory, rm some of the .o files and make CC=clang. >> >> Since OOo is a C++ application, I suspect the unwind-related object >> files to be the culprit. > > Bingo! When I build everything but unwind-dw2.o with clang it works. > This is the object that is causing the problem. FYI, after upgrade it today to r218915, and remove the hack to build libgcc with gcc instead of clang, the problem is gone. Now my world + kernel are both 100% built with clang and i can start openoffice as well. -- Renato BotelhoReceived on Mon Feb 21 2011 - 16:55:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:11 UTC