Created attachment 453964 [details, diff] This is the patch I used to solve the problem dev-util/pkgconfig builds failure with gcc 6.2. It just builds fail at glib/glib/gdate.c, because of Wformat-nonliteral, So I want to gcc to ignore this as a workaround.
https://bugzilla.gnome.org/761550 is the relevant upstream bug for glib, according to which the currently suggested patch would break compilation with older gcc. upstream fixed this with https://git.gnome.org/browse/glib/commit/?id=8cdbc7fb2c8c876902e457abe46ee18a0b134486
(In reply to Felix Janda from comment #1) > https://bugzilla.gnome.org/761550 > > is the relevant upstream bug for glib, according to which the currently > suggested patch would break compilation with older gcc. upstream fixed > this with > > https://git.gnome.org/browse/glib/commit/ > ?id=8cdbc7fb2c8c876902e457abe46ee18a0b134486 Can we have a wrapper of strftime or just patch when build with gcc6.
Patch works for me. It's better 1) to apply patch as soon as possible until next version is released. or 2) tell us that we just wait w/o applying patch 'IF' next version of pkgconfig will be released at soon.
(In reply to Seong-ho Cho from comment #3) > Patch works for me. > > It's better > > 1) to apply patch as soon as possible until next version is released. > > or > > 2) tell us that we just wait w/o applying patch 'IF' next version of > pkgconfig will be released at soon. I'd vote to apply this to our current pkgconfig ebuild. I started MIPS catalyst runs over the weekend, and had to fight around this, since I am basing on gcc-6.3. I checked upstream, and no sign of a new release yet.
For anyone investigating if they can put their own system on gcc-6: This is only a problem when pkgconfig is compiled with USE="internal-glib". That seems to happen only during bootstrap or with uclibc, so if you haven't changed that use flag yourself, this problem may not affect you.
I think this is fixed dev-util/pkgconfig-0.29.2.
(In reply to dolphinling from comment #5) > For anyone investigating if they can put their own system on gcc-6: > > This is only a problem when pkgconfig is compiled with USE="internal-glib". > That seems to happen only during bootstrap or with uclibc, so if you haven't > changed that use flag yourself, this problem may not affect you. OK. Definitely not blocking gcc-6 stabilization.
