Created attachment 314715 [details] Patch that fixes the build I believe the problem here is that new versions of glib (I'm using 2.32.3) don't pull in libgmodule-2.0.so when you link libglib-2.0.so. I've attached a patch that has autoconf test that g_module_symbol gets pulled in by -lglib-2.0 and if not adds -lgmodule-2.0 to the library list. I don't think this bug is prefix-specific, but I don't have a non-prefix ~amd64 testbed to try this with so I've filed the bug against prefix. The patched ebuild works on both by amd64 box and my ~amd64-linux box. I've also filed an upstream bug https://sourceforge.net/tracker/?func=detail&aid=3533549&group_id=239&atid=100239 I'll attach a diff of the ebuild as well.
Created attachment 314717 [details] Adds the described patch to xchat-2.8.8.ebuild
Let's try something a bit less ugly. Add 4th argument to AM_PATH_GLIB_2_0: 'gmodule'.
Created attachment 314723 [details] Patch that fixes the build (In reply to comment #2) > Let's try something a bit less ugly. > Add 4th argument to AM_PATH_GLIB_2_0: 'gmodule'. This new patch works for me, and it's significantly cleaner. The ebuild remains the same.
Although I belive you've found a valid bug I'm unable to reproduce this on any of my ~amd64 testmachines with glib-2.32.3. Therefore I'd like to request the full build.log file of the failed build from you as well as the output of "emerge --info xchat".
Created attachment 315027 [details] xchat build log This the output of MAKEOPTS="-j1" ebuild xchat-2.8.8-r2.ebuild clean install using the xchat ebuild from portage (ie, not with the patch suggested in the build).
Created attachment 315029 [details] emerge --info xchat
This happened to me today, the patch from comment 3 fixed the problem. This was using gcc 4.7.2, 32-bit x86.
Created attachment 344034 [details] emerge --info xchat Switched from gcc-4.6.3 to gcc-4.7.2 on ~amd64 and xchat now breaks.
I switched from gcc-4.6.3 to gcc-4.7.2 on ~amd64 and xchat now breaks. Submitted my own emerge --info xchat in the attachments.
Packages was removed from tree, see bug #460038