Summary: | emerge =dev-libs/glib-2.24.1-r1 fails on automake | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lindsay Haisley <fmouse-gentoo> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | fmouse-gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lindsay Haisley
2010-09-08 19:20:07 UTC
there are no problems with glib 2.24.1-r1, you may update your installation? you are missing gtk-doc-am package but the depend has been in tree for weeks. Please check your installation. Because of time constraints, this system gets updated incrementally. Updating gtk-doc-am from 1.11 to 1.15 seems to have solved the problem. No dependency info was emitted in the attempted emerge of glib. Shouldn't a dependency with a version block indication on gtk-doc-am have been displayed here? I'm sorry if this was an invalid bug, but I simply don't have the time to keep up with everything. Even if the depend for a specific pkg version of gtk-doc-am has been in the tree for weeks, shouldn't some indication of this made it through to the information presented by the emerge for a depended package? I rely heavily on errors from emerge to tell me what to fix if things get out of sync. emerge or your favorite package manager should just have pulled the dependency and installed it before trying to build glib. If this is not the case, check your portage tree is up to date (sync) and if it still doesn't pull the dependency, you might want to report a bug to your package manager. My portage tree is reasonably up-to-date, as is portage, and even so, at any particular time the portage tree should be self-consistent so that this sort of thing doesn't occur. I don't have time to file another bug on this. Someone else with more motivation needs to do it :-) |