On 2011-01-24, at 8:26 PM, surenspost@gmail.com wrote:
Hi,
I am building LO after some time now. Did the usual ./g pull -r , make
clean and then make. The build was breaking for me at cppu.
'''
build -- version: 275224
=============
Building module cppu
=============
Entering /home/suren/libreoffice/libo/cppu/inc
Entering /home/suren/libreoffice/libo/cppu/source/LogBridge
Entering /home/suren/libreoffice/libo/cppu/source/typelib
Entering /home/suren/libreoffice/libo/cppu/source/cppu
Entering /home/suren/libreoffice/libo/cppu/source/threadpool
Entering /home/suren/libreoffice/libo/cppu/source/UnsafeBridge
Entering /home/suren/libreoffice/libo/cppu/source/uno
Entering /home/suren/libreoffice/libo/cppu/source/helper/purpenv
Entering /home/suren/libreoffice/libo/cppu/source/AffineBridge
Entering /home/suren/libreoffice/libo/cppu/util
dmake -f extra.mk
Entering /home/suren/libreoffice/libo/cppu/qa
----------------------------------------------------------
- start unit test #1 on library ../unxlngx6.pro/lib/qa_any.so
----------------------------------------------------------
: &&
LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/home/suren/libreoffice/libo/clone/ure/cppu/unxlngx6.pro/lib:/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/lib
/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/bin/cppunittester
../unxlngx6.pro/lib/qa_any.so
Forcing regeneration of dependency info
----------------------------------------------------------
- start unit test #1 on library
----------------------------------------------------------
: &&
LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/home/suren/libreoffice/libo/clone/ure/cppu/unxlngx6.pro/lib:/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/lib
/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/bin/cppunittester
Retrying /home/suren/libreoffice/libo/cppu/qa
Making: all_qa.dpslo
----------------------------------------------------------
- start unit test #1 on library ../unxlngx6.pro/lib/qa_any.so
----------------------------------------------------------
: &&
LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/home/suren/libreoffice/libo/clone/ure/cppu/unxlngx6.pro/lib:/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/lib
/home/suren/libreoffice/libo/solver/330/unxlngx6.pro/bin/cppunittester
../unxlngx6.pro/lib/qa_any.so
-----------------------------------------------------------------------
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development
it seems that the error is inside 'cppu', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
rm -Rf /home/suren/libreoffice/libo/cppu/unxlngx6.pro # optional module 'clean'
/bin/bash
cd /home/suren/libreoffice/libo
source ./LinuxX86-64Env.Set.sh
cd cppu
build
when the problem is isolated and fixed exit and re-run 'make' from the top-level
''''
Please do advice what to do here ? Let me know if anything more is
needed from my side.
I am running Ubuntu 10.10, 64 bit.
I suggest you take a look at the advice under The Build Failed... What can I do? here,
http://wiki.documentfoundation.org/Development/Native_Build
Dave
--
regards
Suren
Learning < Doing
Learn By doing.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.