On Mon, 7 Jul 2003, Bjoern A. Zeeb wrote:
Hi,
> > > BTW: do you have own icu-2 / xerces-c2 ports or do you use the once I
> > > submitted ?
> >
> > We used our own because we needed a version that didn't link with
> > libc_r.so (i.e., no pthread) because on FreeBSD 4.x, libc and libc_r
> > apparently do not work well with each other -- it would cause random
> > crashes. That problem is supposed to be fixed on 5.x I heard.
> >
> > But for 4.x, perhaps we should create a separate port for thread-based
> > and non-thread-based of ICU, xerces-c2 and xalan-c?
>
> The ports all have a NO_THREADS option you can set when rebuilding.
> There has been one issue with either the xerces or the xalan port
> noted by Berin Lautenbach and is fixed at least in my local versions
> now; got linked against both libc and libc_r.
Ok, I have verified that my Xalan port still builds with either iconv
and icu2 and uploaded a new tarball I am going to submit to FreeBSD
gnats once I have some positive reports.
It should automagically detect if xerces-c2 got linked with iconv or
icu.
Up-to-date port sources (not yet commited to freebsd ports tree) for
the whole chain can be found on
http://sources.zabbadoz.net/freebsd/ports/
(including references to the PRs):
ICU 2.6:
http://sources.zabbadoz.net/freebsd/ports/icu2-2.4_1-2.6-20030615-01.tbz
Xerces-c2 2.3.0:
http://sources.zabbadoz.net/freebsd/ports/xerces-c2-2.2.0-2.3.0-20030709-01.tbz
Xalan-1.5:
http://sources.zabbadoz.net/freebsd/ports/xalan-c-1.5-20030710-01.tbz
The Xalan build framework update[1] is still pending.
I think it might take another few weeks for it to be commited so I
am no longer going to wait with the port but simply include
these changes for now.
[1] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13238
--
Greetings
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
56 69 73 69 74 http://www.zabbadoz.net/
