> Commenting out the sqrt(-2.01) code from
> DoubleSupport.cpp does help.  There is no crash
> anymore.  Turns out, yesterday, when I was trying it,
> it was still picking up an old xalan lib from another
> path.  After I cleaned it up and tested it, there is
> no crash anymore.  Now that we know that is the
> problem, what is the next step.  Could that variable
> be initialized to something else. Can I use a
> workaround. 

There are workaround, but they are not portable, so it makes the code very 
difficult to maintain.  This used to be a problem on Solaris, when made 
this call to sqrt() during static initialization, so it was changed to 
occur when you call XalanTransformer::initialize().  We have never seen or 
heard of any problems with this before on AIX.

> You also talked about running the xalan executable to
> test it if it runs fine.  Where can I get it.  The
> problem is, after building xalan libraries, while
> building the TestXSLT package, the build fails with
> compiler errors  and bails out(see below), so I am not
> sure if the xalan executable is supposed to be built
> after that. 

The problems with testXSLT have been fixed in the latest CVS code.  You 
can get around this by specifying the -k option with gmake.

Dave

Reply via email to