On 2013-9-4 09:44 , Ryan Schmidt wrote: > > On Sep 3, 2013, at 18:12, jerem...@macports.org wrote: > >> Revision: 110689 >> https://trac.macports.org/changeset/110689 >> Author: jerem...@macports.org >> Date: 2013-09-03 16:12:19 -0700 (Tue, 03 Sep 2013) >> Log Message: >> ----------- >> darwintrace requires gcc-4.2 or later >> >> Modified Paths: >> -------------- >> trunk/base/src/darwintracelib1.0/darwintrace.c >> >> Modified: trunk/base/src/darwintracelib1.0/darwintrace.c >> =================================================================== >> --- trunk/base/src/darwintracelib1.0/darwintrace.c 2013-09-03 22:59:31 UTC >> (rev 110688) >> +++ trunk/base/src/darwintracelib1.0/darwintrace.c 2013-09-03 23:12:19 UTC >> (rev 110689) >> @@ -503,6 +503,10 @@ >> char *path, *replacement, command; >> #endif >> >> +#if __GNUC__ && (__GNUC__ < 4 || (__GNUC__ == 4 && __GNUC_MINOR__ < 2)) >> +#error Please build with gcc-4.2 or later >> +#endif > > Is this a new requirement after MacPorts 2.2 was released? Because currently > on Tiger gcc 4.0 is being used. If we're going to continue building base for > Tiger, we'll have to build with apple-gcc-4.2.
Nobody has reported problem building 2.2 so I assume the problem exists only in trunk. What is the actual problem with gcc-4.0? The biggest issue for Tiger is that this will make selfupdating fail. It also makes bootstrapping MacPorts impossible. - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
