Hi, this ebuild installs xalan 1.8.0. In addition to a previous ebuild for version 1.7.0 this one contains the following changes: + added API documentation + set LDFLAGS += "-pthread" as it bails out without it - removes unnecessary docs (we don't need README for example) Probably we also should remove the MSVC samples. Reproducible: Always Steps to Reproduce:
Created attachment 38476 [details] Xalan-C 1.8.0 ebuild
Any chance of this getting into Portage masked?
Oh, and can we keep some of the docs, please? Or, better yet, check the "doc" USE flag to optionally include or exclude the docs?
Sorry - just saw that the ebuild does use the doc USE flag. :/
it fails to build with gcc-3.4 (well i guess technically all the xalan-x ones do ;])
Not a problem for me - got gcc 3.3.4 (currently x86).
There is an easy fix for Xalan-C and gcc 3.4.x. I found it at http://www.mail-archive.com/xalan-dev@xml.apache.org/msg21213.html
Another reason to include this: when I tried to rebuild xalan-c-1.7.0 with xerces-2.6 installed it failed. Looking at it again 1.7.0 should have DEPEND="=dev-libs/xerces-c-2.4.0" instead of DEPEND=">=dev-libs/xerces-c-2.4.0" - my mistake (can this be quietly fixed? - although there is an r1 I see, what's the best syntax to allow bug fixes but not new versions?) 1.8.0 builds against xerces-c-2.6.0 fine for me, but whether it is 100%? Should it be DEPEND="=dev-libs/xerces-c-2.5.0" bearing in mind: http://xml.apache.org/xalan-c/readme.html#xml4c
ok, sorry for the delay 1.8.0 + gcc34 patch is now in cvs
Are all the headers supposed to be installed as readable only by root? ls -l /usr/include/xalanc/* shows that most of the headers are readable only by root.
indeed, looks like the whole tarball has those kind of junk permissions fixed in src_unpack, thanks
