Bug 95326 - pkg-config 0.29 compilation error after gcc update (5.3 -> 6.1)
Summary: pkg-config 0.29 compilation error after gcc update (5.3 -> 6.1)
Status: RESOLVED FIXED
Alias: None
Product: pkg-config
Classification: Unclassified
Component: src (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: pkg-config
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-09 12:40 UTC by Maciej Sobkowski
Modified: 2017-03-20 12:04 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Output from compiler when using gcc 6.1 (37.66 KB, text/plain)
2016-05-09 12:40 UTC, Maciej Sobkowski
Details

Description Maciej Sobkowski 2016-05-09 12:40:10 UTC
Created attachment 123569 [details]
Output from compiler when using gcc 6.1

Hi,

I am compiling pkg-config 0.29 as part of Poky distribution. It fails with following error (attached). When gcc is downgraded to 5.3 it compiles without error. This is building pkg-config for native arch (x86_64).
Comment 1 Dan Nicholson 2016-05-09 16:46:45 UTC
Looks like this is caused by -Werror=format-nonliteral.

../../../git/glib/glib/gdate.c: In function 'g_date_strftime':
../../../git/glib/glib/gdate.c:2497:7: error: format not a string literal, format string not checked [-Werror=format-nonliteral]
       tmplen = strftime (tmpbuf, tmpbufsize, locale_format, &tm);
       ^~~~~~

Looks like this was fixed in upstream glib. You can patch locally with the following 2 commits until the glib snapshot gets updated.

https://git.gnome.org/browse/glib/commit/glib/gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7
https://git.gnome.org/browse/glib/commit/glib/gdate.c?id=8cdbc7fb2c8c876902e457abe46ee18a0b134486
Comment 2 Dan Nicholson 2017-03-20 12:04:47 UTC
I'm pretty sure commit 64cbed9 will fix it by backporting the 2 glib
patches here. Please let me know if this doesn't work.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.