Hi Julien,
So - again this might go well in a bug; this is the 2nd time I've seen
this, and I can't recall the resolution previously.
On Sun, 2010-10-10 at 22:31 +0200, julien wrote:
do i need to add the option with-distro or can i keep on to build like
this, without with-distro option in the autogen part ?
(I've got a Debian in testing updated)
I make again with this :
export VERBOSE=TRUE;make
and here is what i get :
Entering
/home/serval/libreoffice-source/build/build/libreoffice-3.2.99.2/vcl/util
Can you patch this file
/home/serval/libreoffice-source/build/build/libreoffice-3.2.99.2/solenv/bin/checkdll.sh
like this:
--- a/solenv/bin/checkdll.sh
+++ b/solenv/bin/checkdll.sh
@@ -63,7 +63,7 @@ if [ -x $checkdll ]; then
export LD_LIBRARY_PATH;;
esac
- $checkdll "$@"
+ gdb $checkdll "$@"
if [ $? -ne 0 ]; then exit 1 ; fi
for parameter in $*; do
Then - can you run these commands:
bash
cd home/serval/libreoffice-source/build/build/libreoffice-3.2.99.2/
source LinuxX86Env.Set.sh
cd vcl
build verbose=1
You should get a gdb prompt for checkdll: just enter 'run'.
Then when it crashes, can you do 'thread apply all backtrace' ? - and
hopefully we will get a good idea of where it is going wrong - if you
could whack that in the bug, and reply with the bug number here - I'm
sure we can get to the bottom of it.
Thanks so much for helping to chase this one down ?
ATB,
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.