Andy,
There is a related JIRA issue on this matter (XALANC-643)
If you can update this issue with a patch, your efforts would be well
appreciated.
This issue (XALANC-643) is still an open issue.
As part of the documentation project, I am trying to close out obsolete
issues.
This one, however, looks like one that should remain until fixed.
Thanks again for your work on this issue.
Sincerely,
Steven J. Hathaway
Xalan Documentation Project
On 3/4/2012 8:51 AM, a...@blacklightning.net wrote:
I'm getting errors building Xalan-C from the trunk (revision 1294167 to be
precise) that I cannot figure out for the life of me, and I'm hoping
someone out there can help me. I'm not super familiar with the Linux
toolchain, so it's possible I'm making some kind of newbie mistake. I was
able to get Xalan-C building on Windows with VC10 (I even seem to have
updated the projects/solutions to use ICU as a message loader, though I
haven't actually tested using that build yet).
I'm building on Ubuntu 12.04 (which is currently a beta release, I
realize, but the version of gcc has only changed from 4.6.1 to 4.6.3 since
the last release of Ubuntu, 11.10, which doesn't seem likely to cause this
kind of trouble). I would prefer to just use the libxerces-c-dev package
(which is 3.1.1), but after getting these errors I also tried building
Xerces myself and ended up with the exact same problem.
I used the default configure options for Xalan (-p linux, -c gcc, -x g++)
and for Xerces when I built it myself.
Basically, I get a whole lot of "undefined reference to" various
xerces_3_1::* symbols. See the attached xalan.log for the full make
output. The obvious problem would be that the reference to the xerces-c
lib is missing, however the command line from the make output proves this
not to be the case. It correctly uses -L to reference the Xerces lib
folder, and uses -lxerces-c to reference the lib itself, and would spit
errors if it couldn't find the lib (I tried several bogus lib names to
check this).
Furthermore, using the "nm" utility on libxerces-c.so (and libxerces-c.a,
for whatever it's worth) clearly shows that it contains the symbols that
are apparently undefined. So, at this point, I'm at a loss. Can anyone
suggest something I'm missing?
Here's console output from an attempted build. The referenced xalan.log
is attached. Thanks for any suggestions!
$ pwd
/home/andy/Development/Libraries/Builds/xalan-c-trunk.1294167
$ echo $XERCESCROOT
/home/andy/Development/Libraries/Builds/xerces-c-3.1.1
$ echo $XALANCROOT
/home/andy/Development/Libraries/Builds/xalan-c-trunk.1294167
$ make> xalan.log 2>&1
$ nm $XERCESCROOT/lib/libxerces-c.so --demangle | grep
'xercesc_3_1::XMLString::stringLen'
00126f60 T xercesc_3_1::XMLString::stringLen(char const*)
$ nm $XERCESCROOT/lib/libxerces-c.so --demangle | grep
'xercesc_3_1::XMLString::compareString'
00126ae0 T xercesc_3_1::XMLString::compareString(char const*, char const*)
00127bc0 T xercesc_3_1::XMLString::compareString(unsigned short const*,
unsigned short const*)
$ nm $XERCESCROOT/lib/libxerces-c.so --demangle | grep
'xercesc_3_1::XMLString::release'
00128cf0 T xercesc_3_1::XMLString::release(char**,
xercesc_3_1::MemoryManager*)
00128d20 T xercesc_3_1::XMLString::release(unsigned short**,
xercesc_3_1::MemoryManager*)
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
