[59483] trunk/dports/games/larn/Portfile
Ryan Schmidt
ryandesign at macports.org
Thu Oct 15 09:28:27 PDT 2009
On Oct 15, 2009, at 11:11, aschenke at macports.org wrote:
> Revision: 59483
> http://trac.macports.org/changeset/59483
> Author: aschenke at macports.org
> Date: 2009-10-15 09:11:39 -0700 (Thu, 15 Oct 2009)
> Log Message:
> -----------
> append build environment settings rather than overwrite
>
> Modified Paths:
> --------------
> trunk/dports/games/larn/Portfile
>
> Modified: trunk/dports/games/larn/Portfile
> ===================================================================
> --- trunk/dports/games/larn/Portfile 2009-10-15 16:07:02 UTC (rev
> 59482)
> +++ trunk/dports/games/larn/Portfile 2009-10-15 16:11:39 UTC (rev
> 59483)
> @@ -17,7 +17,7 @@
> checksums md5 cea96f48caa057793f6bcaf3394ca388
> build.type bsd
> build.args CC=${configure.cc}
> -build.env CFLAGS=-I${prefix}/include -I${prefix}/include/ncurses
> +build.env-append CFLAGS=-I${prefix}/include -I${prefix}/include/
> ncurses
Looking in the debug output, I don't believe this is having the
desired effect:
---> Building larn
DEBUG: Executing org.macports.build (larn)
DEBUG: Environment: CFLAGS='-I/opt/local/include'
MACOSX_DEPLOYMENT_TARGET='10.6'
If you want to pass multiple values to CFLAGS, you will want to quote
the value:
build.env-append CFLAGS="-I${prefix}/include -I${prefix}/include/
ncurses"
I am not sure why the port is succeeding in building against the
MacPorts ncurses even though it never saw your -I${prefix}/include/
ncurses before.
More information about the macports-dev
mailing list