Summary: | dev-cpp/libglademm needs updated dependencies. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sw1ft |
Component: | [OLD] Library | Assignee: | GNOME C++ Bindings Maintainers (OBSOLETE) <gnome-mm+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dragonheart, pasky, paulo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 167156 | ||
Attachments: | glademm-2.0.0.1 build |
Description
sw1ft
2006-11-23 22:38:04 UTC
Indeed... Here I attach a log of a failed build of 2.0.0.1. It seems several dependencies are missing. Created attachment 113497 [details]
glademm-2.0.0.1 build
(In reply to comment #0) > When attempting to emerge libglademm, the ebuild thought that glibmm 2.8.4 was > acceptable; however, it produced this error when building: It looks like libglademm depends upon gtkmm which in turn may require updates to cairomm and glibmm. I got libglademm to compile by adding all of dev-cpp/libglademm, dev-cpp/gtkmm, dev-cpp/cairomm and dev-cpp/glibmm to /etc/portage/package.keywords (with no version constraints). The final result is glibmm (2.12.7), gtkmm (2.10.8), cairomm (1.2.4), libglademm (2.6.3). I think the primary problem may be a missing dependency between libglademm and gtkmm. The emerge error I had before I doing this was: xml.cc:145: error: no 'GType Gnome::Glade::Xml_Class::lookup_type_vfunc_callback(GladeXML*, const char*)' member function declared in class 'Gnome::Glade::Xml_Class' It doesn't solve the problem with libgnomeuimm however. (Still happens. Manually updating gtkmm before makes libglademm build fine.) gtkmm-2.12.1 and newer all depend on >=dev-cpp/glibmm-2.14.1 @herd ... I'm not too sure what to do on that one... We'll be pruning those old ebuilds anyway, and IIRC portage's ordering algorithm in newer versions was modified. So this shouldn't be a problem anymore. What say you? I think this could be closed since looks fixed in latest ebuilds (In reply to comment #5) > gtkmm-2.12.1 and newer all depend on >=dev-cpp/glibmm-2.14.1 > > @herd ... I'm not too sure what to do on that one... We'll be pruning those old > ebuilds anyway, and IIRC portage's ordering algorithm in newer versions was > modified. So this shouldn't be a problem anymore. What say you? > And all dev-cpp/gtkmm:2.4 ebuilds look to have it fixed |