Hi Will,
First - awesome to see you here ! :-) welcome back.
On Fri, 2011-06-03 at 14:25 -0400, William Lachance wrote:
I've been attempting to get LibreOffice master built on my Mac running
10.6. Per the instructions on the wiki, I installed XCode with the
10.4 SDK option and the various ports mentioned here
Sadly I don't have a mac to test.
I've been stuck with a problem building the redland module though. It
seems to want to compile something called 'raptor' using a system
version of libxml, and is getting stuck:
You may find it easier to stay on the beaten track wrt. configure
options (which may mean an internal libxml), and or ./autogen.sh
--with-distro=LibreOfficeMacOSX # but again, I'm not a Mac guy, so just
guessing.
ToFile( "LIBXML_CFLAGS", "-I/opt/local/include/libxml2", "e" );
ToFile( "LIBXML_LIBS", "-L/opt/local/lib -lxml2 -lz -lpthread
-liconv -lm", "e" );
Ah - most likely this is not used by the inner configure, but only by
the OO.o code.
Any ideas on what the problem could be here? I did notice that
redland/raptor/makefile.mk defines the configure flags to be:
..
Do we need to somehow change this to include LIBXML_CFLAGS and
LIBXML_LIBS? Just changing CPPFLAGS to "-nostdinc $(INCLUDE)
$(LIBXML_CFLAGS)" unfortunately didn't seem to help. Any advice on how
to tackle this appreciated.
Sounds like it :-) I wonder if we need some CFLAGS with that in, as
well as CPPFLAGS - no doubt the test is in C ?
Anyhow - thanks for getting stuck in,
ATB,
Michael.
--
michael.meeks@novell.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.