Configure flags and universal variants
Hi all, Trunk contains new code for configure flags and default universal variant code. It would be great if this could be tested more and released as soon as possible: - it would allow maintainers to work on universal variants - it would allow us to simplify many portfiles by removing: configure.env CFLAGS=-I${prefix}/include LDFLAGS=-L${prefix}/lib Besides, trunk code produces -O2 binaries for autoconf-based ports, while any such port with the previous line is compiled -O0 with 1.4.0. Paul
On Mar 27, 2007, at 9:35 PM, Paul Guyot wrote:
Besides, trunk code produces -O2 binaries for autoconf-based ports, while any such port with the previous line is compiled -O0 with 1.4.0.
Might -Os be a better choice for the default? -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Mar 28, 2007, at 1:13 PM, Daniel J. Luke wrote:
On Mar 27, 2007, at 9:35 PM, Paul Guyot wrote:
Besides, trunk code produces -O2 binaries for autoconf-based ports, while any such port with the previous line is compiled -O0 with 1.4.0.
Might -Os be a better choice for the default?
-O2 is a conservative choice. This is autoconf default when the compiler is gcc. Now, I agree we might want to make this a configurable option. Paul
On Mar 27, 2007, at 20:35, Paul Guyot wrote:
Trunk contains new code for configure flags and default universal variant code.
It would be great if this could be tested more and released as soon as possible: - it would allow maintainers to work on universal variants - it would allow us to simplify many portfiles by removing: configure.env CFLAGS=-I${prefix}/include LDFLAGS=-L${prefix}/lib
Besides, trunk code produces -O2 binaries for autoconf-based ports, while any such port with the previous line is compiled -O0 with 1.4.0.
Can this also help the CC, CPP, CXX situation? I mean: there are many ports that say things like this: platform darwin 8 { configure.env CC=/usr/bin/gcc-4.0 CPP=/usr/bin/cpp-4.0 CXX=/usr/bin/g ++-4.0 } Why is this necessary? Wouldn't all three of those be the default on darwin 8 anyway? What problem are these directives trying to solve? And could the problem be solved at a global MacPorts level instead? Along with the MACOSX_DEPLOYMENT_TARGET, CFLAGS and LDFLAGS.
On Mar 28, 2007, at 3:35 AM, Paul Guyot wrote:
Hi all,
Trunk contains new code for configure flags and default universal variant code.
It would be great if this could be tested more and released as soon as possible: - it would allow maintainers to work on universal variants - it would allow us to simplify many portfiles by removing: configure.env CFLAGS=-I${prefix}/include LDFLAGS=-L${prefix}/lib
the -I/path/to/include should go probably go into the CPPFLAGS, not the (C|CXX)FLAGS. i've only tried it with nano, but nano i.e. * works with the CPP- & LDFLAGS set * does not work with the C-, CXX-, and LDFLAGS set nonetheless, either the ports' creators don't stick really closely to that rule or it's us. i ran $grep "\-I\${prefix}/include" */*/Portfile > ~/foo; cd $gnused -r -i "s/.+CFLAGS\=\"*-I\\$\{prefix}\/include[^\n]*/foo/g" foo $gnused -r -i "s/.+CPPFLAGS\=\"*-I\\$\{prefix}\/include[^\n]*/bar/ g" foo $gnused -r -i "s/.+CXXFLAGS\=\"*-I\\$\{prefix}\/include[^\n]*/bla/ g" foo (resulting in foo[1]) [1] http://rafb.net/p/nDOv2P12.html Regards, Elias
Besides, trunk code produces -O2 binaries for autoconf-based ports, while any such port with the previous line is compiled -O0 with 1.4.0.
Paul
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
On 2007-03-28 13:05:23 +0200, Elias Pipping wrote:
On Mar 28, 2007, at 3:35 AM, Paul Guyot wrote:
It would be great if this could be tested more and released as soon as possible: - it would allow maintainers to work on universal variants - it would allow us to simplify many portfiles by removing: configure.env CFLAGS=-I${prefix}/include LDFLAGS=-L${prefix}/lib
the -I/path/to/include should go probably go into the CPPFLAGS, not the (C|CXX)FLAGS. i've only tried it with nano, but nano i.e.
I agree. But instead of setting CPPFLAGS and LDFLAGS, a solution could be to set the CPATH and LIBRARY_PATH environment variables. But I don't know what the best solution is in practice. -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
participants (5)
-
Daniel J. Luke
-
Elias Pipping
-
Paul Guyot
-
Ryan Schmidt
-
Vincent Lefevre