On Jan 11, 2008, at 10:25, nox@macports.org wrote:
Revision: 32697 http://trac.macosforge.org/projects/macports/changeset/32697 Author: nox@macports.org Date: 2008-01-11 08:25:00 -0800 (Fri, 11 Jan 2008)
Log Message: ----------- icu: Updated to 3.8.1.
Modified Paths: -------------- trunk/dports/devel/icu/Portfile
Modified: trunk/dports/devel/icu/Portfile =================================================================== --- trunk/dports/devel/icu/Portfile 2008-01-11 16:15:06 UTC (rev 32696) +++ trunk/dports/devel/icu/Portfile 2008-01-11 16:25:00 UTC (rev 32697) @@ -4,7 +4,8 @@
name icu set my_name icu4c -version 3.8 +version 3.8.1 +set doc_version [join [lrange [split ${version} .] 0 1] _] categories devel platforms darwin freebsd maintainers nox @@ -25,20 +26,36 @@ distfiles [suffix ${distname}-src]
checksums [suffix ${distname}-src] \ - sha1 4370becc68eab7a01292db62e1649239b1732a5b \ - md5 67cc2650fbcae4c8e3ba5ce4dda4b072 \ - rmd160 e9a0105477b54e6d3f222bf7741a61058c70665b \ - ${distname}-docs.zip \ + md5 a827dbc9d909febd4ec39b90386868ba \ + sha1 c2b933aee6741c28956f1b87dc514dee49b949aa \ + rmd160 d297330ff0eb91bff5ac91e59188f1751f899032 \ + ${my_name}-${doc_version}-docs.zip \ + md5 677b218cbca2acc304b9771c63bd69bf \ sha1 94b47b5dd88bce15dab608719efbbd405d15e912 \ - md5 677b218cbca2acc304b9771c63bd69bf \ rmd160 927f4466758722e958b90a2bae873b11da222e88
worksrcdir ${name}/source set docdir ${prefix}/share/doc/${name}-${version}
+post-patch { + reinplace "s;install_name ;install_name ${prefix}/lib/;" $ {worksrcpath}/config/mh-darwin +} + +configure.cmd ./runConfigureICU MacOSX
The portfile claims to work on the freebsd platform in addition to darwin. Is this configure.cmd appropriate on FreeBSD?
configure.args --mandir=${prefix}/share/man \ --disable-samples
+# ICU wants to build with -O3, let's do as it wants. +configure.cflags-delete -O2 + +pre-configure { + # The -delete statement above may lead to configure.cflags variable being unset + if {! [info exists configure.cflags]} { + configure.cflags + } +}
What you're doing here in the pre-configure phase, is this a MacPorts base bug that needs to be fixed?