#38218: default configure.optflags should be -Os rather than -O2 --------------------------+-------------------------------- Reporter: jeremyhu@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by fmw@…): Replying to [comment:2 ryandesign@…]:
There's no practical way to test that this won't break "anything". We can change it in trunk now and see if we notice any problems on our development machines. And we'll probably let the buildbots rebuild all ports after this (since hopefully it'll go into 2.2 for which we already have to rebuild all ports because of the libtool archive changes) but looking through a log of building thousands of ports to analyze the ones that failed is impractical, especially given how many of our ports already don't build for other reasons. We can handle this like we always do: if people find ports that are broken, because of this or any other reason, they can file tickets and we'll fix them on a case-by-case basis.
Sorry in advance for not having much undrestanding of macports.... In the webkit-gtk portfile (which provoked this), I note the line "platform powerpc {". If this is only invoking options based on the compile time CPU, would a line like "target powerpc {" for the runtime CPU, be a base solution by providing a way of implementing patches and flags required when there is sometimes a difference between compile & execute CPUs? Moreover, such a facility might permit easy testing (or back tracking) before (after), a change like -Os goes live? This sort of facility is what I first went looking for when I found https://trac.macports.org/ticket/37839 -- Ticket URL: <https://trac.macports.org/ticket/38218#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS