On 02/12/10 11:21, Jonathan Aquilina wrote:
Is this when you run the autogen.sh? if it is, i had an issue with it
bombing on junit. can you try and change in the autogen.sh from
/bin/sh at the top to /bin/bash. that fixed my issue. if thats the
case, not sure where else to turn to isolate this bug..
Yes it is. I'll try changing it to /bin/bash - I'm on gentoo so it
should be bash anyways, but never mind. I did try --without-junit, but
that didn't work either. I don't have junit or junit4, and I think the
new system is meant to autodetect and use what you have available. So it
should detect ant is missing and switch it off, not bomb because it's
not there ...
Cheers,
Wol
On 12/02/2010 12:10 PM, Wols Lists wrote:
On the old build system I always had to do --without-junit, implying
that I had --with-java.
On the new system I need --without-java or it bombs with "can't find
ant"
Sorry - I should have backed up my old devel directory so I could go
back and find out ...
Cheers,
Wol
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.