Thanks for your reply, Dave - the output from the otool command you suggested
is:
libxerces-c.dylib:
Mach header
magic cputype cpusubtype caps filetype ncmds sizeofcmds flags
0xfeedface 7 3 0x00 6 13 1856 0x00118085
I don't understand it all, but from the link you suggested, it seems to be
the correct architecture (i386, 32-bit). (BTW, *is* this correct for a
MacBook Pro? I had thought that these were 64-bit, but everything I've
installed and compiled has been 32-bit)
I didn't actually compile Xerces, but installed the binary: the reason I
think it is working is that I tried some of the Samples included in the
installation and they seemed to parse the XML properly - e.g. running:
SAXCount personal.xml
in /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0/samples/data/
gives:
personal.xml: 15 ms (37 elems, 12 attrs, 134 spaces, 134 chars)
which I suppose is the correct breakdown of that XML file.
Thanks for your help,
Christian
David Bertoni wrote:
>
> xn wrote:
>> I'm having problems building Xalan-C for Mac OS X Snow Leopard - I don't
>> think there are binaries available for this platform. I've got
>> Xerces-C-2_8_0 working (I think) and installed in
>> /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0/ but when I download, unzip
>> and
>> untar Xalan-C_1_10-src.tar.gz to /Users/christian/temp/ and try to build
>> it
>> from the resulting ~/temp/xml-xalan/c/ directory, it won't work.
>> I have set $XERCESCROOT to /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0
>> and $XALANCROOT to /Users/christian/temp/xml-xalan/c
>> and added /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0 to $PATH
>> and $DYLD_LIBRARY_PATH is
>> /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0/lib:
>> Then,
>> ./runConfigure -p macosx -c gcc -x g++
>> seems to set up the configuration OK, but when I run 'make' I get
>> problems
>> starting with:
>> ld: warning: in
>> /usr/local/xerces-c_2_8_0-x86-macosx-gcc_4_0/lib/libxerces-c.dylib, file
>> is
>> not of required architecture
> This indicates the Xerces-C binary you built is for a different
> architecture than the Xalan-C binaries you're linking with it. When you
> way you "think" you've got Xerces-C working, can you provide more
> details, like the flags you provided to the Xerces-C runConfigure
> script? Also, it would be helpful if you could provide a dump of the
> header of the Xerces-C shared object, using otool:
>
> otool -h libxerces-c.dylib
>
> You can find more information about deciphering this output here:
>
> http://0xfe.blogspot.com/2006/03/how-os-x-executes-applications.html
>
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
> For additional commands, e-mail: xalan-dev-h...@xml.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Xalan-C-build-on-Mac-OS-X-Snow-Leopard-tp25782174p25800471.html
Sent from the Xalan - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
