#13930: Intermittent failures building Python modules: unable to execute -DNDEBUG ----------------------------+----------------------------------------------- Reporter: wiml@hhhh.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------+----------------------------------------------- Comment (by afb@macports.org): It seems that those python ports are expecting $CC to be set in build as well as in configure, and fall back to random values such as "" or "cc" or "/usr/bin/gcc-4.0" when it isn't. This probably also explains why rerunning the build sometimes succeeds, if something else was adding a $CC to the environment that can be picked up as a lucky guess second time. Supposedly base wants to be enhanced to support CC in non-configure builds ? Workaround meanwhile is adding `build.env="CC=gcc"` while building the port. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13930#comment:4> MacPorts </projects/macports> Ports system for Mac OS