Compiling gnome-extra/gnome-system-monitor-3.6.1 failed on my machine with errors related to not finding certain symbols in the GIO bindings provided by glibmm. I wish I could be more specific about the exact symbols, but I didn't really expect my eventual fix to work and I lost the log output.
I fixed this by updating glibmm to the latest version available to me (2.34.1), and that fixed these errors. The ebuild for gnome-system-monitor-3.6.1 lists ">=dev-cpp/glibmm-2.27:2" as a dependency, so the true dependency must be somewhere between 2.27 and 2.34.1.
Steps to Reproduce:
1. Attempt to emerge gnome-extra/gnome-system-monitor-3.6.1 with glibmm-2.27
Compilation fails (pretty quickly) about unknown symbols in the GIO namespace.
Created attachment 338904 [details]
my emerge --info
Do you have the error? It would let us search for unknown symbol and try to find the version including that
If I ever did, I lost it months ago, and unfortunately I'm not really in a position to either downgrade my installed glibmm (and risk losing my desktop) or install a new gnome system from scratch. I know this is pretty stereotypical bad bug reporter behavior, so I apologize in advance.
For whatever it's worth (probably not much), ubuntu lists glibmm 2.33.13 and glib 2.28.0 as dependencies for this package+version combo.
+ 14 Sep 2013; Gilles Dartiguelongue <firstname.lastname@example.org>
+ gnome-system-monitor-3.6.1.ebuild, gnome-system-monitor-18.104.22.168.ebuild,
+ Raise glibmm dependency per bug #457624.
I couldn't downgrade my system to a configuration that would fail like it did for you and in the absence of a build.log it is hard to figure out what exactly was missing.
Anyway, since glibmm-2.34 appears to have fixed the issue for you and since it keyword level matches gnome-system-monitor just fine, I raised the glibmm dependency to that version.
Thanks for reporting and please provide a build.log next time. :)