Hi,
well "git clone" and a fresh build was my friend :-) I didn't want to spend more time into
solving that build problem.
What I still don't understand is: I ran "make clean", "configure --disable-moz" (or similar, don't
know by heart), "make" and the build still failed even if all linux tinderboxen were green. So
there must be a difference between a fresh clone and a system after "make clean". I think I even
removed ./install - but can't tell that for sure.
At least now I have a buildable system again the the above is just out of curiosity :-)
Christina
-------- Original-Nachricht --------
Datum: Tue, 15 May 2012 10:11:36 +0100
Von: "Caolán McNamara" <caolanm@redhat.com>
An: "Christina Roßmanith" <ChrRossmanith@gmx.de>
CC: libreoffice@lists.freedesktop.org
Betreff: Re: psp::PrinterInfoManager related build problems
On Sat, 2012-05-12 at 22:43 +0200, Christina Roßmanith wrote:
Hi,
I've made clean and still can't build LibO (error messages see below).
Any idea what might be my problem? Tinderboxes are green, so master
should be buildable?!?
printerjob.cxx:(.text+0x1149): undefined reference to
`psp::PrinterInfoManager::get()'
Is this still a problem for you, or is it resolved. If its still a
problem it must be related somehow to the configure --enable-headless
and/or cups detection stuff somehow.
C.
--
Christina Rossmanith
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
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.