Hello,
as mentioned in this bug report
https://bugs.freedesktop.org/show_bug.cgi?id=56158 build problems
should be
communicated over the mailing list. So do I.
I never tried to build LibreOffice before on my machine, so that the
configure script had many complaints about
missing dependencies I had to install. Done so, make fetched some
additional stuff from the web and
started to compile.
After a long time make complained about an compiler error because
sane/sane.h was not found. After installing
libsane-dev it continues compiling.
I took a look into configure.ac which actually contains an check for
sane/sane.h. But if I see this correct it will
be only executed if --with-system-sane is passed.
(Please excuse the german output. Forgot to change locale settings
before. But it doesn't say more than I did above.)
---%<-----
[build CXX] extensions/source/scanner/sane.cxx
[build CXX] extensions/source/scanner/sanedlg.cxx
In file included from
/mnt/private/development/cpp/LibreOffice/extensions/source/scanner/sane.cxx:24:0:
/mnt/private/development/cpp/LibreOffice/extensions/source/scanner/sane.hxx:26:23:
schwerwiegender Fehler: sane/sane.h: Datei oder Verzeichnis nicht
gefunden
Kompilierung beendet.
make[1]: ***
[/mnt/private/development/cpp/LibreOffice/workdir/unxlngx6.pro/CxxObject/extensions/source/scanner/sane.o]
Fehler 1
---%<-----
best regards
Robert Peters
PS: Tried to build: c318f3b0224a57102614be0efec4b49c80a3aa82
Context
- Missing sane/sane.h check · Robert Peters
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.