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


Matúš Kukan píše v St 21. 11. 2012 v 15:06 +0100:
On 21 November 2012 14:04, Lubos Lunak <l.lunak@suse.cz> wrote:
On Wednesday 21 of November 2012, kendy@suse.cz wrote:
Hi folks,

One of you broke the build of LibreOffice with your commit :-(
Please commit and push a fix ASAP!

Full log available at http://tinderbox.libreoffice.org/MASTER/status.html

Tinderbox info:

  Box name: Win-x86@7-MinGW
...
unzip:  cannot find or open
/local/home/tinderbox/master-mingw/src/fc188d2ed5c2cbcf7a021b34b9f88478-icu
dt49l-subset.zip,
/local/home/tinderbox/master-mingw/src/fc188d2ed5c2cbcf7a021b34b9f88478-icu
dt49l-subset.zip.zip or
/local/home/tinderbox/master-mingw/src/fc188d2ed5c2cbcf7a021b34b9f88478-icu
dt49l-subset.zip.ZIP. dmake:  Error code 9, while making
'./unxlngx6.pro/misc/build/so_configured_so_icu' ERROR: error 65280
occurred while making /local/home/tinderbox/master-mingw/icu

 It seems specifying tarballs to download in configure.ac doesn't work well
with cross-compilation.

True, currently it's quite ugly.
http://cgit.freedesktop.org/libreoffice/core/commit/?id=93abcf4e4bb1a460d7695b6374bf4a92c9203512
should fix this.
Maybe selective download was not that good idea.
I'm working on moving ooo.lst into makefile.
That also may be not good idea. Let's see.
It could help this cross-compiling hack.

Ah, this feature has been discussed at
https://bugs.freedesktop.org/show_bug.cgi?id=56131 David suggested to
use one variable for each tarball. Such variable can be reused also in
the makefile that is used during build. IMHO, it is a good idea.


Best Regards,
Petr


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.