On 3/19/10 6:08 AM, Ryan Schmidt wrote:
On Mar 16, 2010, at 09:41, gwri...@macports.org wrote:
Revision: 64850
http://trac.macports.org/changeset/64850
Author: gwri...@macports.org
Date: 2010-03-16 07:41:53 -0700 (Tue, 16 Mar 2010)
Log Message:
-----------
No universal variant; add verbose configuration and set --with-gcc=.
Modified Paths:
--------------
trunk/dports/devel/hs-utf8-string/Portfile
Modified: trunk/dports/devel/hs-utf8-string/Portfile
===================================================================
--- trunk/dports/devel/hs-utf8-string/Portfile 2010-03-16 14:41:52 UTC (rev
64849)
+++ trunk/dports/devel/hs-utf8-string/Portfile 2010-03-16 14:41:53 UTC (rev
64850)
@@ -15,7 +15,10 @@
sha1 65da57b42de89948aab1870426229e7a3cb89675 \
rmd160 723eeb9e1f4de6f986dc1b58e7b83f429faa34f6
-configure.args-append --enable-library-profiling
+universal_variant no
+configure.args-append -v --enable-library-profiling \
+ --with-gcc=${configure.cc}
+
build.args-append -v
I see you adding these things to a lot of haskell ports. Is it perhaps
appropriate to make the haskell portgroup do this automatically?
I have no objection to this. The "-v" is just to generate verbose
output, so there
is something to look at when port is run with "-d" or "-v".
The --with-ghc=${configure.cc} is always needed to prevent the cabal library
(which does the configure, build and install work) from using the first
thing
name "gcc" on the $PATH.
And there won't be universal variants of haskell ports any time soon.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
