| Summary: | gnome-extra/gnome-system-monitor-3.30.0 - ld: /usr/lib64/libgtkmm-3.0.so: undefined reference to `Gtk::Plug_Class::wrap_new(_GObject*)' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dmitriy Baranov <reagentoo> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info |
||
Created attachment 572688 [details]
emerge --info
You need to re-emerge dev-cpp/gtkmm after you upgrade x11-libs/gtk+. (In reply to Jeroen Roovers from comment #2) > You need to re-emerge dev-cpp/gtkmm after you upgrade x11-libs/gtk+. Does not help. This bug now is also actual for gnome-system-monitor-3.32.1. So as per IRC chats and tests, this seems to be gnome-system-monitor not only depending on X stuff for the wnck stuff, but also unconditionally having some Gtk::Socket and Gtk::Plug_Class stuff, which are X11isms, so it needs gtkmm[X] unconditionally right now, with more details to be looked into. |
Created attachment 572686 [details] build.log /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgtkmm-3.0.so: undefined reference to `Gtk::Plug_Class::wrap_new(_GObject*)' /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgtkmm-3.0.so: undefined reference to `Gtk::Socket::get_type()' /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgtkmm-3.0.so: undefined reference to `Gtk::Plug::get_type()' /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libgtkmm-3.0.so: undefined reference to `Gtk::Socket_Class::wrap_new(_GObject*)' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed.