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
> > appa
On Mon, 7 Jul 2003, David Yan wrote:
Hi,
ok we are getting offtopic again but if it helps ...
> > 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 o
> I do have some changes since the last tarballs[1] but I am also
> successfully running Xalan on 4.{6,7,8}-STABLE and 5.x now with either
> iconv or icu[2] (autodetected depended on what xerces-c2[3] has been
> built with).
>
> [1] still waiting for the build framework commit before upload
On Mon, 7 Jul 2003, David Yan wrote:
Hi,
> We at Yahoo! have Xalan-C 1.5 working on FreeBSD 4.8 with Xerces-C 2.2
> and ICU 2.6. We are preparing a port now. Please let me know if
> you're interested in the details.
So we will have two ports for the same ? :((
I do have some changes since the
Hi all,
We at Yahoo! have Xalan-C 1.5 working on FreeBSD 4.8 with Xerces-C 2.2
and ICU 2.6. We are preparing a port now. Please let me know if
you're interested in the details.
David
Bjoern A. Zeeb writes at 17:36 on 6/24/2003:
> Hi,
>
> on http://sources.zabbadoz.net/freebsd/ports/expe
On Wed, 25 Jun 2003, Berin Lautenbach wrote:
Hi,
> WooHoo! Works like a charm. testXPath now runs on my 4.8-RELEASE box,
> so very happy.
:-))
> What I might do (if you have no objections), is incorporate the minimal
> amount of changes into the current makefiles to get Freebsd to compile
>
Bjoern,
WooHoo! Works like a charm. testXPath now runs on my 4.8-RELEASE box,
so very happy.
What I might do (if you have no objections), is incorporate the minimal
amount of changes into the current makefiles to get Freebsd to compile
and run properly.
I might leave the install piece out fo
On Mon, 23 Jun 2003 [EMAIL PROTECTED] wrote:
Hi,
> > 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
> >
> You can define XALAN_USE_XERCES_LOCAL_CODEPAGE_TRANSCODERS
> to bypass this call to mbstowcs during the build
> process.
I think we may be relying on non-standard behavior here, so it might be
best if we transitioned _all_ our platforms to just use the Xerces
transcoder.
We can further remo
> 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.
It's strange that
> From: "Bjoern A. Zeeb"
> 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 i
On Thu, 19 Jun 2003 [EMAIL PROTECTED] wrote:
Hi,
(hope you do not get it twice - something ate the first mail :(( )
> > There will be at least one problem with
> > xercesc_2_3::XMLTransService::makeNewTranscoderFor
>
> There have been numerous commits since 1.5 was released, and a fix fo
Bjoern,
To follow up.
Bit the bullet today and did the upgrade to 4.8. Still gcc 2.95.4 but
looks to have been recompiled.
Re-compiled all of Xerces - DOMPrint still crashes. So I think we can
safely say that anything < 5.0 (at least) crashes.
Cheers,
Berin
Bjoern A. Zeeb wrote:
On Sa
On Sat, 21 Jun 2003, Berin Lautenbach wrote:
Hi,
> No joy. SIGSEGV on program exit for DOMPrint and SAXPrint.
>
> Have found that if I disable threads in Xerces, the test apps appear to
> work OK. (Or at least DOMPrint does, which is my main test app.)
I have experimented a bit with this yes
Bjoern A. Zeeb wrote:
Can you please try following patch:
--- src/xercesc/runConfigureFri Jun 20 13:11:49 2003
+++ src.test/xercesc/runConfigure Fri Jun 20 13:13:04 2003
No joy. SIGSEGV on program exit for DOMPrint and SAXPrint.
Have found that if I disable threads in Xerces, the test ap
On Fri, 20 Jun 2003 [EMAIL PROTECTED] wrote:
> > From: Alexei Dets <[EMAIL PROTECTED]>
> > > What exactly are your problems with FreeBSD and xerces-c ?
> >
> > All Xerces applications are crashing (at least on FreeBSD-4.7) with
> > segmentation fault immediately after XML convertions - I mean all
On Thu, 19 Jun 2003 [EMAIL PROTECTED] wrote:
> > I just checked xalan-c cvs and couldn't see any commits since 1.5
> > release. Is this really correct ? Do you know if anybody is working
> > on this ?
> > There will be at least one problem with
> > xercesc_2_3::XMLTransService::makeNewTran
> From: Alexei Dets <[EMAIL PROTECTED]>
> > What exactly are your problems with FreeBSD and xerces-c ?
>
> All Xerces applications are crashing (at least on FreeBSD-4.7) with
> segmentation fault immediately after XML convertions - I mean all supplied
> demo applications. My applications are usi
Hi!
On Thursday 19 June 2003 08:19, Bjoern A. Zeeb wrote:
> Had a xalan 1.4 port almost ready last Oct/Nov I think but neither
> xerces-c2 nor icu2 ports got comitted so I didn't finisch and didn't
> contribute to the open PR yet. If you want to give it a try (minor
> corrections needed) please let
> The problem now is from what I can see, that my xerces-c2 2.3 port
> update[2] is pending and Xalan 1.5 will not work with this due to API
> changes.
> I just checked xalan-c cvs and couldn't see any commits since 1.5
> release. Is this really correct ? Do you know if anybody is working
> on
Hi,
Hadn't really followed Xalan-c up to now.
Also had not followed xerces-c-dev for some weeks due to exams.
First:
There is at least one PR pending for a xalan-c[1] port and I am currently
working on it (neither maintainer nor commit privs to freebsd ports
tree).
Had a xalan 1.4 port almost
TED]>
> Subject: Re: Freebsd port
> Date: 18/06/2003 8:10:22
> To: <[EMAIL PROTECTED]>,
>
> Hi!
> On Sunday 15 June 2003 22:39, Gary Hughes wrote:
> > Has anyone ported Xalan to freebsd?
>
> I've made a port and have now Xalan-1.4.0 + Xerces-1.7.0 work
Hi!
On Monday 16 June 2003 14:21, Matthew Hoyt wrote:
> As well, from a web search, there is also appears to be a Xalan-C 1.4
> patch to enable a FreeBSD build:
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=44430). This is not from
> Apache, but may be of some use.
This will NOT work on FreeBSD
Hi!
On Sunday 15 June 2003 22:39, Gary Hughes wrote:
> Has anyone ported Xalan to freebsd?
I've made a port and have now Xalan-1.4.0 + Xerces-1.7.0 working on FreeBSD
4.7. It is a very stable combination - no any crashes etc.
Newer versions were not working - I think because of Xerces - Xerces-2
Hi Gary,
Regarding a FreeBSD port, Xalan-C does not directly support FreeBSD at
this time.
David Bertoni replied to a similar question in November:
"If you mean Xalan-C++, we don't have any hardware available to do that,
and
limited resources, so I doubt this is possible.
Depending on the
25 matches
Mail list logo
