On 2013-5-28 19:56 , Ryan Schmidt wrote: > > On May 28, 2013, at 00:58, [email protected] wrote: > >> Revision: 106493 >> https://trac.macports.org/changeset/106493 >> Author: [email protected] >> Date: 2013-05-27 22:58:40 -0700 (Mon, 27 May 2013) >> Log Message: >> ----------- >> glib2: configure with --disable-compile-warnings, as it normally enables >> -Werror for some warnings that the code triggers >> >> Modified Paths: >> -------------- >> trunk/dports/devel/glib2/Portfile >> >> Modified: trunk/dports/devel/glib2/Portfile >> =================================================================== >> --- trunk/dports/devel/glib2/Portfile 2013-05-28 05:57:43 UTC (rev >> 106492) >> +++ trunk/dports/devel/glib2/Portfile 2013-05-28 05:58:40 UTC (rev >> 106493) >> @@ -73,7 +73,8 @@ >> >> configure.cflags-append -fstrict-aliasing >> >> -configure.args --enable-static --disable-libelf >> +configure.args --enable-static --disable-libelf \ >> + --disable-compile-warnings > > Could you point me to the ticket or other documentation about the specific > problems that this was causing? The port already has a lot of directives > whose purpose I'm not sure of anymore, and this makes it difficult for me to > know when it's safe to remove directives.
There's no ticket, it just failed to build for me when I was testing the fix for #39246. As mentioned in the commit message, it doesn't just enable warnings normally, but also -Werror for some warning classes. IIRC the (first) one that caused the failure was a non-constant format string. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
