| Summary: | Gramps won't install in a chroot | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | george <gk> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
george
2003-09-23 03:07:02 UTC
The test in the ebuild fails: python -c "import gtk.glade" When commenting the test out of the ebuild, econf then fails: checking Python bindings for GNOME... configure: error: **** The python bindings for GNOME 2.0 (gnome-python2) could not be found. did you compile pygtk with glade support ? you really do need it. emerge libglade and then remerge pygtk. Yes I did ... I haven't changed any USE flags since bootstrapping this system. chroot# emerge -pv libglade pygtk gramps These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] gnome-base/libglade-2.0.1 -doc -nls [ebuild R ] dev-python/pygtk-2.0.0 +gnome -opengl [ebuild N ] app-misc/gramps-0.9.3 Same for target PC except gramps is R not N. I also tried revdep-rebuild --soname libglade-2.0.so.0 --pretend and this included pygtk-2.0.0 on both chroot and target PC. As far as my understanding goes, this is pretty conclusive that the problem is the testing for glade, not its presence. We're pushing the boundaries of my knowledge here but anything else I can try to help, just ask. ok can you attach the configure.log or similar to see what exactly fails in the detection ? Just tried to create a log for you with 0.9.4 and guess what - the test in the ebuild still fails but the build itself (with the test commented out) works now! If you want more info to track this down then just ask (although I can't do anything now for about 10 days). If you're happy to close this then so am I - I can always re-open it if the problem comes back after further updates ;). I have seen a different problem though. Building the language files in the ..../po directory will fail for me on a random language with MAKEOPTS="-j2". Changing this to "-j1" fixes it. I haven't time to check if this is a known bug now - I'll look properly when I have can. please open a new bug when necessary, we need to get our bugcount down now to get some oversight. |