On 13.04.2015 15:53, Tomáš Chvátal wrote:
2015-04-13 12:52 GMT+02:00 Tomáš Chvátal <tomas.chvatal@gmail.com
<mailto:tomas.chvatal@gmail.com>>:
2015-04-13 12:47 GMT+02:00 Tomáš Chvátal <tomas.chvatal@gmail.com
<mailto:tomas.chvatal@gmail.com>>:
2015-04-13 12:37 GMT+02:00 Tomáš Chvátal
<tomas.chvatal@gmail.com <mailto:tomas.chvatal@gmail.com>>:
Hello people,
Update:
It is even slightly more fun:
Before I run tests just after install:
abuild@bugaboo:~/rpmbuild/BUILD/libreoffice-4.3.6.2/instdir/program/classes>
ls -laF
total 4300
-rw-r--r-- 2 abuild abuild 1713391 Apr 13 08:08 unoil.jar
After them:
abuild@bugaboo:~/rpmbuild/BUILDROOT/libreoffice-4.3.6.2-0.x86_64/usr/lib64/libreoffice/program/classes>
ls -laF
total 2628
-rw-r--r-- 1 abuild abuild 357 Apr 13 10:36 unoil.jar
Or it also might be caused because of wrong permissions it got
created with?:
abuild@bugaboo:~/rpmbuild/BUILD/libreoffice-4.3.6.2/instdir/program/classes>
ls -laF
total 4300
-rw------- 1 abuild abuild 1713391 Apr 13 10:36 unoil.jar
Tom
More digging,only two jars are broken like this unoil and ridl. They
call the macro:
gb_Jar_add_packagedirs
There might be some race around it. As each build to see how it goes
takes me few hours and I need to get lucky to trigger it... It is bit
unlucky to go by :)
these unoil.jar should not be re-built again after "make" is done, try
running "make -d unitcheck" (warning: generates gigabytes of text) to
see which dependency is triggering the re-build of unoil.jar.
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.