Compile failed because the new glib version.
Steps to Reproduce:
1. emerge net-nntp/pan
i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pthread -I/usr/include/gmime-2.6 -I/usr/include/gpgme -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=prescott -O2 -pipe -fomit-frame-pointer -c -o progress.o progress.cc
In file included from file-util.h:28:0,
/usr/include/glib-2.0/glib/gtypes.h:28:2: #error "Only <glib.h> can be included directly."
glib >2.31.0 breaks a lot of packages Each package needs to be patched to account for the changes with the way includes are handled. The following packages on my system fail with the same error:
There was one other but the individual package got patched in the tree and it compiled fine. I suspect all the packages affected need to be patched and there are bug reports opened for pan and xchat that I see. I had to have 2.32.0 unmasked for gnome 3.2.1
(In reply to comment #1)
> glib >2.31.0 breaks a lot of packages Each package needs to be patched to
> account for the changes with the way includes are handled. The following
> packages on my system fail with the same error:
I have fixed app-accessibility/gnome-speech and x11-libs/gksu in cvs, and filed bug #411195 with a patch for xchat. On my machine, easytag builds fine with glib-2.32, so I suspect you are experiencing a different issue with it, namely bug #409281.
In the future, please file *separate* bugs for each package that fails due to glib-2.32. That way, they will be noticed by the maintainers of the affected packages, many of whom are not be subscribed to a bug about net-nntp/pan.
Thank you for reporting; fixed in cvs without a revision bump. (I used Dominique Leuenberger's patch because the corresponding commit from upstream git also included other changes that appeared to be somewhat invasive.)
> 08 Apr 2012; Alexandre Rostovtsev <email@example.com> pan-0.135.ebuild,
> Fix building with >=glib-2.31 (bug #401437, thanks to Mathias for reporting).