Another glibc change that nearly got pushed into F16

Tom Lane tgl at
Wed Oct 26 14:06:31 UTC 2011

"Richard W.M. Jones" <rjones at> writes:
> I forgot to add that it's probably a good idea to recompile any
> package that was compiled against the -13 glibc package.

BTW, if this is the case, why is 2.14.90-13 still in rawhide?
Shouldn't we assume that every build done recently in rawhide is tainted?

I've spent the past couple of days trying to rebuild every libpng-using
Fedora package using mock's fedora-rawhide-x86_64 environment.
A distressingly large fraction of them FTBFS with

/usr/include/glib-2.0/glib/gmacros.h:32:2: error: #error "Only <glib.h> can be included directly."

or close variants of that.  I assume this is another manifestation of
the same bug being discussed here ... or have the glibc guys managed to
break the world in two different ways in the same release?

			regards, tom lane

More information about the devel mailing list