https://bugzilla.novell.com/show_bug.cgi?id=296680#c1 Philipp Thomas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pth@novell.com AssignedTo|pth@novell.com |bnc-team-gnome@forge.provo.novell.com --- Comment #1 from Philipp Thomas 2007-08-02 03:17:59 MST --- I'm reassigning to our GNOME maintainers, but I'd guess there's a -std=c99 or -std=gnu99 missing in the compiler flags. Without one of these C99 inline functions are indeed not supported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=296680#c3 --- Comment #3 from Nikolay Derkach 2007-08-02 03:41:10 MST --- Created an attachment (id=155101) --> (https://bugzilla.novell.com/attachment.cgi?id=155101) build log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=296680#c5 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Michael Matz 2007-08-02 04:11:36 MST --- Well, gcc 4.2 simply doesn't support C99 inlines. glib2 seems to want to use them, though I would think that that was unintended (in the past GCC was less picky about the exact syntax to define or declare inline functions). Anyway, the headers request public inlined functions, and the addition of the -std=c99 flag makes this request C99 inlines, whose semantic is different from GNU inlines. GCC 4.2 doesn't support that semantic, hence the warning. Either don't use the -std=c99 flag, or add the flag -fgnu89-inline, which also makes this warning go away by making GCC use the GNU semantic even in C99 mode. For reference here's the full warning message, which also mentions this solution: warning: C99 inline functions are not supported; using GNU89 warning: to disable this warning use -fgnu89-inline or the gnu_inline function attribute C99 semantic will not be ported to gcc 4.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=296680#c7 --- Comment #7 from Michael Matz 2007-08-02 06:06:05 MST --- GCC 4.1.2 simply didn't implement the warning. GCC 4.2 does implement it in anticipation of the upcoming support for C99 inline semantics in 4.3 which are different enough to GNU semantics to warrant a warning about unintentional use of C99 semantics. As you add -std=c99 to the command line GCC will act as if C99 semantics are requested so it gives the warning based on the assumption that the developer probably cares about this upcoming change in semantics. This normally doesn't lead to any failure, as it's only a warning. But you also use -Werror whose intent is to regard all warnings as compile errors. So, that's what you get here. 4.1.2 didn't have this warning, so -Werror was harmless there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=296680#c9 --- Comment #9 from Michael Matz 2007-08-02 07:16:10 MST --- Nope, the warning is there for a reason. I'm sympathetic to you being annoyed by it, but for that you can add the -fgnu89-inline option yourself to the projects which interest you. Other developers are interested in such warnings hence we should not switch the default to not emit it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.