Dave et al.
I have managed to build 1.4 on NetBSD. Took some
time, but I managed to get it to work. (mbstowcs
is broken in NetBSD 1.5 so had to work around).
I had actually planned to try to get FreeBSD to
work for the next version, but no promises until
I've had a bit of a go. Given FreeBSD is
supported in the Xerces build, this seemed to
make more sense than continuing down the NetBSD
path for my stuff.
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: Re: Upcoming Xalan-C++ 1.5 release
> Date: 27/03/2003 9:18:46
> To: [email protected]
>
>
>
>
>
> Hi Alexei,
>
> Please reply to the list, not to my personal address.
>
> > Is it planned to have a _normal_ Unix library naming scheme
> > (like, for example, libxalan-c.so.15 instead of libxalan-c_1_5_0.so)
> > and if not, why?
>
> Not for this release. That will happen for the next one.
>
> > Are there any plans to support FreeBSD? Currently on FreeBSD I'm stuck
> with
> > Xalan version 1.4.0 + Xerces-1.7.0 - this combination works perfectly
> unlike
> > Xalan-1.5.0-interim + Xerces-2.1.0 (this combination is crashing after
> first
> > calls to initialization methods of Xalan & Xerces...). Xalan-1.4.0 +
> > Xerces-2.1.0 doesn't work either :-(
>
> We've never actually built Xalan on FreeBSD, so I don't know what problems
> might exist for that platform. We don't have access to a FreeBSD machine,
> and these sorts of problems tend to be related to the version of GCC being
> used to build the executables, etc.
>
> Dave
>
>
This message was sent through MyMail http://www.mymail.com.au
