Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Thanks Stephan.
So better to build using '--without-java' or better to install the older
Java 1-6 ?

On Wed, Nov 19, 2014 at 7:12 PM, Stephan Bergmann <sbergman@redhat.com>
wrote:

On 11/19/2014 04:54 PM, Adam Fyne wrote:

I'm trying to build now on a totally fresh clean Macbook,
after I've installed whatever was needed.
(went with the easy approach, but was missing JDK and
ANT so I've installed them separatly).

After cloning, autogen & make - I get these unit-test errors:
http://pastebin.com/raw.php?i=iYF13p1s

All the unit-tests seem to come from 'dbaccess'.
I also see this line in the output:
"No Java runtime present, requesting install."

Wasn't JDK 64-bit enough ?


see <http://lists.freedesktop.org/archives/libreoffice/2014-
October/064096.html> "Java problem when running
CppunitTest_dbaccess_dialog_save on OS X 10.10 with Oracle JDK 1.8" and <
http://lists.freedesktop.org/archives/libreoffice/2014-October/064097.html>
"Re: Java problem when running CppunitTest_dbaccess_dialog_save on OS X
10.10 with Oracle JDK 1.8"
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice




-- 




*Adam Fyne*
Interoperability Team Leader
Twitter <http://www.twitter.com/cloudoninc> | LinkedIn
<http://www.linkedin.com/company/cloudon> | Facebook
<http://www.facebook.com/cloudoninc>

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.