> From: "Bjoern A. Zeeb" <bzeeb-
<snip>
> The great questions are:
> a) why does mbstowcs(..) fail on 4-STABLE bu not on 5.1 ?
> b) [more important] how to correctly recover from this error path ?
> I do not ocnsider it a FreeBSD specific problem but simply an
> unhandled error path in xalan.
Ran into a similar problem in NetBSD 1.6, with
mbstowcs not being correctly implemented for
cases where the caller sets the result string to
0 in order to find the length of the result. May
be the same kind of issue here.
You can define XALAN_USE_XERCES_LOCAL_CODEPAGE_TRANSCODERS
to bypass this call to mbstowcs during the build
process.
I will setup your patches on my FreeBSD system
as soon as you post them. Would love to be able
to get it to work properly.
Great stuff!
Cheers,
Berin
This message was sent through MyMail http://www.mymail.com.au
