On Wed, Mar 7, 2012 at 7:17 PM, Mariana Marasoiu
<mariana.marasoiu@gmail.com> wrote:
I did yesterday a ./g pull -r but it didn't fix the build. Afterwards,
I tried a make clean & make, which ended with the same result.
I followed Korrawit's instructions and realised that the branch I was
trying to build wasn't the master, but libreoffice-3-5. So I switched
to master, did ./g pull -r and now it's building once again. Lets hope
this time works :D
Okay, bad news... I still couldn't build LibreOffice :(.
It fails in two modules: officecfg and sal. I tried building them
separately, with a make clean before that, but I still get errors...
This is what I get for officecfg:
cd officecfg && make -j 1 -rs gb_PARTIALBUILD=T
[ build XCS ] officecfg/registry/schema/org/openoffice/Setup.xcs
/home/mariana/Working/git/libo/solver/unxlngi6.pro/xml/processing/schema_val.xsl:1:
parser error : Document is empty
^
/home/mariana/Working/git/libo/solver/unxlngi6.pro/xml/processing/schema_val.xsl:1:
parser error : Start tag expected, '<' not found
^
cannot parse /home/mariana/Working/git/libo/solver/unxlngi6.pro/xml/processing/schema_val.xsl
make[1]: ***
[/home/mariana/Working/git/libo/workdir/unxlngi6.pro/XcsTarget/officecfg/registry/schema/org/openoffice/Setup.xcs]
Error 4
make: *** [officecfg] Error 2
And for sal module, there are lots of C++ errors and warnings and also
"No such file or directory" errors.
If I should post the output, tell me and I'll put it in a pastebin.
Thanks,
Mariana Mărășoiu
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.