> Well, for starters, 3.0 does not build on my stock Debian box. > This appears to be due to ICU being installed on my machine > and autoconf picking it up and configuring Xerces-C++ to use > it (which is not a bad idea by itself). But, as further > investigation showed, autoconf support for ICU is not > finished. I tried to change a few things but ran into more > problems after regenerating the configure scripts with newer > version of libtool. See the following thread for more information: > > http://thread.gmane.org/gmane.text.xml.xerces-c.devel/8275 > > If anybody has any idea how to fix this, please let us know.
I'll certainly take a look. I haven't ever used ICU, but I might be able to identify some things. > I agree, if there is no way to test something then there is no way > to support it. However, as I mentioned above, there are problems > on mainstream platforms or across platforms. We need an accurate list of issues, I think. Is this one in Jira? > Remember that there was a build system which, while being ugly and all, > supported quite a few platforms. Now we threw that build system away > and replaced it with another one which does not (yet) work properly > on less mainstream platforms. It seems to me that telling users of > those platform to fix it themselves or shut up is a sure way to > alienate them. Projects also have to be realistic when they have constrained resources. Poor and non-ongoing support *is* worse than none, and if the autoconf support is there, it's much easier to fix the outliers than it was before. Losing platforms in the short run will pay off in the long run. I don't see how the answer can be anything other than fix it yourself if there's nobody available with the platform to do it for them. It's not being difficult, it's just the way it is. Obviously we can get access to Debian, that's an example where we can fix it, but HP-UX or AIX might not be. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
