opensubscriber
   Find in this group all groups
 
Unknown more information…

x : xerces-p-dev@xml.apache.org 5 February 2005 • 4:52AM -0500

Re: conflict of building XML::Xerces-2.5.0-0 using Xerces-C-2.6.0
by Lincoln A. Baxter

REPLY TO AUTHOR
 
REPLY TO GROUP




Hey Jason,

What is involved in make a new Xerces release for each release of
Xerces-C?  Is it something we would work on scripting, so that we would
not have to redo it with every release?

Lincoln


On Thu, 2005-02-03 at 11:56 +0530, Jason E. Stewart wrote:
> Sai Tong <sai.tong@gmai...> writes:
>
> > You are attempt to build XML::Xerces-2.5.0-0 using Xerces-C-2.6.0,
> > this will most likely fail, so I am aborting.
> >
> > You must use Xerces-C-2.5.0
>
> This is because the Xerces-C API changes with every version. So most
> often you cannot link an older version of XML-Xerces with a newer
> version of Xerces-C - sometimes it will work, but very rarely.
>
> > Is it possible at all to make XML-Xerces-Perl (2.5.0) with
> > Xerces-C-2.6.0 ? I really would like to install  the XML::Xerces
> > Module without having to  find a way to install an older version of
> > the c++ compiler.
>
> Well, you can simply comment out the line in the Makefile.PL that
> checks the versions and try the compile. My guess is that it will fail
> badly, but you can try.
>
> The other option is to either help me find funding so that I can work
> on XML-Xerces more often (and make a real 2.6 release), or to find
> other developers who can assist in the Xerces development.
>
> Cheers,
> jas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml....
> For additional commands, e-mail: xerces-p-dev-help@xml....
>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml....
For additional commands, e-mail: xerces-p-dev-help@xml....

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.