If you are using 3.1 version of the Xerces-C then you should try to
build from the head of the Xalan-C repository as David suggested
earlier.

Good luck!
        Vitaly

Steele, Raymond wrote:
Is there a conflict between xalan and xerces functions Locator::getLineNumber() 
and Locator::getColumnNumber()?


I am compiling using the following:

CC -o *.o -c -DSOLARIS -g DDEBUG -DDXLOPT -DMISSING_PROTOS -I<includes>  *.cpp

Now, I am receiving the following error when I try to compile a simple 
application with the xalan headers.

"../XalanLocator.hpp", line 65: Error: Virtual function 
xalanc_1_10:XalanLocator::getLineNumber() const returns int, while 
xerces_3_1::Locator::getLineNumber() const returns unsighned long long

Raymond


-----Original Message-----
From: Steele, Raymond
Sent: Wednesday, February 16, 2011 3:51 PM
To: 'xalan-...@xml.apache.org'
Subject: RE: EXTERNAL: Re: Xalan-C Libraries

David,

I was able to build xalan with runConfigure, but now, when I compile my own 
application, I receive the following at compilation:

../PlatformDefinitions.hpp, line 42: Error #error unknown compiler.


Is this because of the compiler switches that you mentioned? If so, how do I 
get around this.

Thanks,

Raymond


-----Original Message-----
From: David Bertoni [mailto:dbert...@apache.org]
Sent: Monday, January 24, 2011 11:24 AM
To: xalan-...@xml.apache.org
Subject: EXTERNAL: Re: Xalan-C Libraries

On 1/20/2011 3:34 PM, Steele, Raymond wrote:
Is there support for Solaris 10 x86? I cannot seem to find Xalan-C libraries 
that are compatible to my machine type.
There are no pre-built binaries for x86. If you build from the head of
the repository, there is a solaris-x86 target. If you want to build from
the 1.10 source package, you'll need to change some of the compiler
switches for the Solaris SPARC target and use that target.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org


Reply via email to