Hello,
I just did an update, an "autogen.sh && make clean" and when i build sc,
i have this :
=============
Building module sc
=============
Entering /home/maryline/libreoffice-source/libo/sc/inc
mkout -- version: 1.8
touch
/home/maryline/libreoffice-source/libo/solver/330/unxlngi6.pro/inc/minormkchanged.flg
Entering /home/maryline/libreoffice-source/libo/sc/sdi
dmake: Error: --
`/home/maryline/libreoffice-source/libo/solver/330/unxlngi6.pro/inc/sfx2/sfx.sdi'
not found, and can't be made
Forcing regeneration of dependency info
nothing to do here...
Retrying /home/maryline/libreoffice-source/libo/sc/sdi
dmake: Error: --
`/home/maryline/libreoffice-source/libo/solver/330/unxlngi6.pro/inc/sfx2/sfx.sdi'
not found, and can't be made
-----------------------------------------------------------------------
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development
it seems that the error is inside 'sc', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
Julien.
__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail
Context
- [Libreoffice] Compilation sc failed · Julien Nabet
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.