Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi there,

On Fri, 2011-12-09 at 17:10 +0100, Winfried Donkers wrote:
I have just got a new computer, which should make LibO much faster than my old machine does :) .

        Fun :-)

Unfortunately, I get a make error:
.../core/solver/unxlngi6.pro/bin/cppunit/cppunittester:
symbol lookup error: /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so: undefined symbol: 
cairo_surface_create_for_rectangle
...
make[2]: *** [.../core/workdir/unxlngi6.pro/CppunitTest/hwpfilter_test_hwpfilter.test] Error 1

        Looks like a symbol conflict between your internal cairo library and
the system gtk+ library. Curious that it happens with the cppunit test
of course. Essentially I would remove *cairo* from the solver (or run
deliver -delete inside cairo/) and re-configure and build with
--with-system-cairo.

I use openSUSE 12.1, installed all packages with zypper si -d libreoffice plus some 
more based on errors when running autogen.sh --with-max-jobs=6 --with-num-cpus=6
--without-junit (untill autogen.sh gave a successfull result).
Can anyone give me a hint how I can get LibO built?

        I use --with-system-cairo on the same systme with no problems :-) FWIW,
you're by no means the last accidental victim of the idiocy that is
known as interposing in the ELF linker ;-)

        HTH,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.