xn wrote:
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)
As far as I know, OS X is not yet fully 64-bit, so perhaps the default
for most binaries is to build 32-bit versions.
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.
Yes, I would assume the binary distribution would work.
I think you may be generating 64-bit Xalan-C object files. That would
happen if the default for your version of gcc is 64-bit. You might try
to add a few flags to the runConfigure command for Xalan-C:
-z -m32 -l -m32
that should force 32-bit binaries.
Also, could you supply the actual runConfigure command line you used?
Unfortunately, it looks like using "-b 32" won't force a 32-bit build on
64-bit platforms.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
