On Thu, 2010-10-14 at 10:19 +0100, Michael Meeks wrote:
On Thu, 2010-10-14 at 08:37 +0200, Thomas Klausner wrote:
Where is the "build" executable I'm supposed to run when a build is
interrupted ?
Ah - good point :-) I'll update the build script to print a more
useful message in a bit, but first:
Hopefully - git master now doesn't tell you to execute a command you
can't run ;-) when we get a build failure it should say something like
this:
[snip]
Compiling: vcl/source/app/brand.cxx
/data/opt/OpenOffice/loffice/vcl/source/app/brand.cxx:80:2: error: #error Error !
dmake: Error code 1, while making '../../unxlngi6.pro/slo/brand.obj'
-----------------------------------------------------------------------
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 'vcl', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
cd /opt/OpenOffice/loffice
source ./LinuxX86Env.Set.sh
cd vcl
build
when you have isolated and fixed the problem re-run 'make' from the top-level
[/snip]
With a suitable variant for multi-threaded building; great bug to get
fixed :-)
Thanks,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
Context
- Re: [Libreoffice] C{,PP}FLAGS ignored in sal (continued)
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.