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


Update:


After an O/S upgrade and git pull, master doesn't build any longer.

I get

/usr/bin/cp: cannot stat '/git/lo/workdir/CustomTarget/postprocess/images/images_breeze.zip': Bestand of map bestaat niet make[1]: *** [/git/lo/solenv/gbuild/Package.mk:35: /git/lo/instdir/share/config/images_breeze.zip] Fout 1
make[1]: *** Wachten op onvoltooide taken...
/usr/bin/cp: cannot stat '/git/lo/workdir/CustomTarget/postprocess/images/images_breeze_dark.zip': Bestand of map bestaat niet make[1]: *** [/git/lo/solenv/gbuild/Package.mk:35: /git/lo/instdir/share/config/images_breeze_dark.zip] Fout 1 /usr/bin/cp: cannot stat '/git/lo/workdir/CustomTarget/postprocess/images/images_galaxy.zip': Bestand of map bestaat niet make[1]: *** [/git/lo/solenv/gbuild/Package.mk:35: /git/lo/instdir/share/config/images_galaxy.zip] Fout 1
make: *** [Makefile:258: build] Fout 2

(for 'Bestand of map bestaat niet' read 'File or folder does not exist', for 'Fout' read 'Error'.)

I have files images_*.zip in /usr/lib64/libreoffice/share/
After copying the images_*.zip files from /usr/lib64/libreoffice/share to workdir/CustomTarget/postprocess/images/ and copying images_breeze.zip to 'missing_filename'.zip till I no longer got errors, I managed to build LibreOffice (master) again.
But this can't be the proper way.

How can I get the proper package or set of images files on my computer again?

Winfried

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.