You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Axel Weiß <aw...@informatik.hu-berlin.de> on 2006/08/13 14:55:48 UTC
compile issue
Hi,
I'm trying to compile xalan from svn sources and get an error message that I
cannot understand. Can someone clear me up with this? I'm running a 64-bit
linux (SuSE-10.1) and compiled/installed xerces-3.0 (from svn) prior.
I did the following:
1. Edit Makefile.incl.in line 73, in order to link to xerces-3.0:
--- XERCES_LIB = -L$(XERCESCROOT)/lib -lxerces-c
+++ XERCES_LIB = -L$(XERCESCROOT)/lib -lxerces
2. set XALANCROOT to <path-of-xalan-svn>/trunk
3. set XERCESCROOT to to /usr/local
4. cd $XALANCROOT
5. ./runConfigure -p linux -c gcc -x g++ -b 64 -l -L/usr/local/lib -l
-lpthread
6. make
[...]
make[3]: Entering directory
`<path-of-xalan-svn>/trunk/src/xalanc/Utils/MsgCreator'
[...]
g++ -DLINUX -fPIC -L/usr/local/lib -lpthread -DXALAN_INMEM_MSG_LOADER \
-lm -lpthread -L/usr/local/lib
-lxerces ../../../../obj/MsgFileOutputStream.o ../../../../obj/ICUResHandler.o ../../../../obj/InMemHandler.o ../../../../obj/MsgCreator.o ../../../../obj/NLSHandler.o ../../../../obj/SAX2Handler.o
-o ../../../../bin/MsgCreator
make[3]: Leaving directory
`/fast/axel/xalan/svn/trunk/src/xalanc/Utils/MsgCreator'
../../../bin/MsgCreator /fast/axel/xalan/svn/trunk/src/xalanc/NLS/en_US/XalanMsg_en_US.xlf
-TYPE inmem -LOCALE en_US
Fatal Error at
file /fast/axel/xalan/svn/trunk/src/xalanc/NLS/en_US/XalanMsg_en_US.xlf, line
20, char 19
Message: make[2]: *** [../../../nls/include/LocalMsgData.hpp] Error 8
I have no idea what could be wrong here. The file XalanMsg_en_US.xlf seems to
be sane, don't know anything about 'Error 8'. Who can help?
Shall I file a bugreport?
Thanks,
Axel
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: compile issue
Posted by David Bertoni <db...@apache.org>.
Axel Weiß wrote:
> David Bertoni wrote:
>> It looks like the .xlf file might be corrupt and Xerces-C is complaining
>> during the parse. Can you look at XalanMsg_en_US.xlf and see if there's
>> anything on line 20 that looks suspicious?
>>
>> I just built the sources from SVN recently and did not have any problems.
>
> Hi Dave,
>
> sorry for the delay. I did some random tests now (e.g. DOMCount from the
> xerces samples) and found something strange:
>
> XalanMsg_en_US.xlf, line 21: <xliff version="1.1">
> xliff.dtd, line 43: version CDATA #FIXED "1.0"
>
> produces a version mismatch error (at least when parsed with xercesc-2.7,
> which shows a lot of errors following this one). Xerces-3.0 complains only
> 'fatal error in xml file', without a reason.
That seems to me like there's a bug in the 3.0 branch.
>
> From the reading, XalanMsg_en_US.xlf cannot be validated by xliff.dtd -
> otherwise the validator is broken. I have double-checked that I have the
> current svn checkout of xalan (Revision 431957, without changes since some
> days). Dave, can you check whether your (funcional) files show this version
> conflict? I guess, there's only some stupid not-yet-checked-in issue.
It may be that something has changed in Xerces-C in the 3.0 branch that
affects validation. I suspect that we have never enabled validation for
the message file.
You could try either changing the version attribute in the message file, or
ensuring that all validation is turned off in
xml-xalan/c/src/xalanc/Util/MsgCreator/MsgCreator.cpp
This might also be a bug in Xerces-C 3.0. In general, Xalan-C doesn't
start testing with a new version Xerces-C until there's a concrete date for
the release. I don't real feel that the 3.0 branch is stable enough for
that yet.
Note that, as a workaround, you can produce the message library with a
version of the MsgCreator utility that was compiled with Xerces-C 2.7.
Then, you can simply use that library and the resulting intermediate files
to build Xalan-C with Xerces-C 3.0.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: compile issue
Posted by Axel Weiß <aw...@informatik.hu-berlin.de>.
David Bertoni wrote:
> It looks like the .xlf file might be corrupt and Xerces-C is complaining
> during the parse. Can you look at XalanMsg_en_US.xlf and see if there's
> anything on line 20 that looks suspicious?
>
> I just built the sources from SVN recently and did not have any problems.
Hi Dave,
sorry for the delay. I did some random tests now (e.g. DOMCount from the
xerces samples) and found something strange:
XalanMsg_en_US.xlf, line 21: <xliff version="1.1">
xliff.dtd, line 43: version CDATA #FIXED "1.0"
produces a version mismatch error (at least when parsed with xercesc-2.7,
which shows a lot of errors following this one). Xerces-3.0 complains only
'fatal error in xml file', without a reason.
From the reading, XalanMsg_en_US.xlf cannot be validated by xliff.dtd -
otherwise the validator is broken. I have double-checked that I have the
current svn checkout of xalan (Revision 431957, without changes since some
days). Dave, can you check whether your (funcional) files show this version
conflict? I guess, there's only some stupid not-yet-checked-in issue.
Since I have a new hardware setup (now running AMD-64-bit), I cannot guarantee
that xerces-3.0 library works as expected - I need a matching xalan library
to run my own test scenarios. Using all the pre-compiled libraries
(SuSE-10.1) is just working perfectly, but I was able to run my projects
successfully with the bleeding edge of xerces/xalan some months ago, with my
old hardware setup.
Thanks,
Axel
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: compile issue
Posted by Axel Weiß <aw...@informatik.hu-berlin.de>.
David Bertoni wrote:
> It looks like the .xlf file might be corrupt and Xerces-C is complaining
> during the parse. Can you look at XalanMsg_en_US.xlf and see if there's
> anything on line 20 that looks suspicious?
David,
These are lines 19ff of XalanMsg_en_US.xlf:
<!DOCTYPE xliff PUBLIC "-//XLIFF//DTD XLIFF//EN"
"../xliff.dtd" >
<xliff version="1.1">
<file source-language="en_US" target-language="en_US" datatype="cpp"
original="XalanC source files" product-name="XalanC"
product-version="1.10.0">
<header></header>
<body>
Except for some trailing whitespaces, there's nothing suspicious with it. And
xliff.dtd seems to be good as well (althought I'm not familiar with DTDs).
> I just built the sources from SVN recently and did not have any problems.
I will double-check my xerces installation tomorrow.
Thanks,
Axel
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: compile issue
Posted by David Bertoni <db...@apache.org>.
Axel Weiß wrote:
> Hi,
>
> I'm trying to compile xalan from svn sources and get an error message that I
> cannot understand. Can someone clear me up with this? I'm running a 64-bit
> linux (SuSE-10.1) and compiled/installed xerces-3.0 (from svn) prior.
>
> I did the following:
> 1. Edit Makefile.incl.in line 73, in order to link to xerces-3.0:
> --- XERCES_LIB = -L$(XERCESCROOT)/lib -lxerces-c
> +++ XERCES_LIB = -L$(XERCESCROOT)/lib -lxerces
>
> 2. set XALANCROOT to <path-of-xalan-svn>/trunk
> 3. set XERCESCROOT to to /usr/local
> 4. cd $XALANCROOT
> 5. ./runConfigure -p linux -c gcc -x g++ -b 64 -l -L/usr/local/lib -l
> -lpthread
> 6. make
> [...]
> make[3]: Entering directory
> `<path-of-xalan-svn>/trunk/src/xalanc/Utils/MsgCreator'
> [...]
> g++ -DLINUX -fPIC -L/usr/local/lib -lpthread -DXALAN_INMEM_MSG_LOADER \
> -lm -lpthread -L/usr/local/lib
> -lxerces ../../../../obj/MsgFileOutputStream.o ../../../../obj/ICUResHandler.o ../../../../obj/InMemHandler.o ../../../../obj/MsgCreator.o ../../../../obj/NLSHandler.o ../../../../obj/SAX2Handler.o
> -o ../../../../bin/MsgCreator
> make[3]: Leaving directory
> `/fast/axel/xalan/svn/trunk/src/xalanc/Utils/MsgCreator'
> ../../../bin/MsgCreator /fast/axel/xalan/svn/trunk/src/xalanc/NLS/en_US/XalanMsg_en_US.xlf
> -TYPE inmem -LOCALE en_US
>
> Fatal Error at
> file /fast/axel/xalan/svn/trunk/src/xalanc/NLS/en_US/XalanMsg_en_US.xlf, line
> 20, char 19
> Message: make[2]: *** [../../../nls/include/LocalMsgData.hpp] Error 8
>
> I have no idea what could be wrong here. The file XalanMsg_en_US.xlf seems to
> be sane, don't know anything about 'Error 8'. Who can help?
It looks like the .xlf file might be corrupt and Xerces-C is complaining
during the parse. Can you look at XalanMsg_en_US.xlf and see if there's
anything on line 20 that looks suspicious?
I just built the sources from SVN recently and did not have any problems.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org