Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi John,

On Sun, 2010-10-03 at 11:07 -0500, John Wohn wrote:
Based on advice I got on #libreoffice IRC I tried to build
connectivity manually.  I did:
source LinuxX86Env.Set.sh
cd build/libreoffice-3.2.99.1/connectivity
build

        Great - this is the best approach when a problem comes up in a parallel
make.

and I got a segmentation fault:
Making:    libkabdrv1.so
Segmentation fault
dmake:  Error code 1, while making '../../../unxlngi6.pro/lib/libkabdrv1.so'

        Exciting :-) it looks like the linker crashes. So - we should do:
        build verbose=1

        to get the exact command line - hopefully you don't have a custom
python compile - so you can use gdb.

I don't know what my next steps should be to debug the problem.

        So - with the verbose you should get a long command line of what is
executed and crashes.

        repeat that command pre-pending:

        gdb --args <command>
        run

        and when it crashes enter: 'thread apply all backtrace' and paste the
output here.

        What Linux, and toolchain are you using ? in general the linker
shouldn't crash.

        If that doesn't help - perhaps there is just some stale binaray in
there - I would be inclined to remove unxlngi6.pro and re-build that
piece.

        HTH,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.