188.8.131.52.alpha1 build error
mstahl at redhat.com
Wed Nov 13 05:44:51 PST 2013
On 13/11/13 10:12, Miklos Vajna wrote:
> On Tue, Nov 12, 2013 at 09:14:30PM +0100, Andreas Radke <a.radke at arcor.de> wrote:
>> Thanks for the hint. Replacing dejavu-fonts with liberation fonts made
>> the build finish.
> Great to hear that. :)
>> Now it fails in a different way:
>> ... installing module gid_Module_Root_SDK ...
>> DestDir: /build/libreoffice/src/fakeinstall
>> Rootpath: /usr/lib/libreoffice
>> ln: failed to create symbolic link '/build/libreoffice/src/fakeinstall/usr/lib/libreoffice/sdk/classes/win/unowinreg.dll': No such file or directory
>> ERROR: Failure in installer.pm
>> ERROR: Failed "ln -sf '/build/libreoffice/src/185d60944ea767075d27247c3162b3bc-unowinreg.dll' '/build/libreoffice/src/fakeinstall/usr/lib/libreoffice/sdk/classes/win/unowinreg.dll'" at /build/libreoffice/src/libreoffice-184.108.40.206.alpha1/solenv/bin/modules/installer/worker.pm line 374.
> Make sure to check the result after make install, if the symlink still
> points to
> you probably want to replace that symlink with a real copy, as users
> won't have access to '/build/libreoffice/src/' when they install your
> package. :)
the unowinreg.dll must not be a symlink since the installer now checks
for filelists if the listed file is a symlink and in that case assumes
that a symlink needs to be created in the installation that points to
the same target, which avoids having to maintain special entries for
symlinks in scp2; no file is actually copied in that case.
if anybody symlinks random files and expects the installer to convert
them to real files like it did in previous versions they may be
More information about the LibreOffice