Since latest KDE update (4.8.1) I get this build error in ArchLinux:
R=/build/src && S=$R/libreoffice-core-3.5.1.2 && O=$S/solver/unxlngx6.pro &&
W=$S/workdir/unxlngx6.pro && mkdir -p $W/Headers/Library/ && touch
$W/Headers/Library/simplecanvas.uno.so
In file included from /usr/include/kcompletion.h:24:0,
from /usr/include/kcombobox.h:27,
from /usr/include/kfilefiltercombo.h:27,
from
/build/src/libreoffice-core-3.5.1.2/fpicker/source/unx/kde4/KDE4FilePicker.cxx:67:
R=/build/src && S=$R/libreoffice-core-3.5.1.2 && O=$S/solver/unxlngx6.pro &&
W=$S/workdir/unxlngx6.pro && mkdir -p $W/Headers/Library/ && touch
$W/Headers/Library/nullcanvas.uno.so
/usr/include/kglobalsettings.h:595:46: error: expected identifier before '(' token
/usr/include/kglobalsettings.h:595:46: error: expected '}' before '(' token
/usr/include/kglobalsettings.h:595:46: error: expected ')' before numeric constant
/usr/include/kglobalsettings.h:597:1: error: expected unqualified-id before 'protected'
/usr/include/kglobalsettings.h:679:1: error: expected unqualified-id before 'private'
/usr/include/kglobalsettings.h:682:21: error: expected unqualified-id before ')' token
/usr/include/kglobalsettings.h:685:20: error: uninitialized const 'd' [-fpermissive]
/usr/include/kglobalsettings.h:688:1: error: expected declaration before '}' token
Is this already known? Latest kfpicker commits seem to be only removing other compiler warnings.
-Andy
Context
- [3.5.1] build broken in KDE4FilePicker.cxx · Andreas Radke
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.