Summary: | dev-python/pygobject-2.14 fails to emerge : can't find Python headers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Fellows <fellows> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | exien.ow |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
pygobject-2.14.0 config.log
pygobject build log |
Description
David Fellows
2007-11-18 01:56:56 UTC
Attach the config.log here please. Created attachment 136198 [details]
pygobject-2.14.0 config.log
Created attachment 136199 [details]
pygobject build log
is there a particular reason you still have python 2.3 ? python-2.4.4-r6 is supposed to be fixed wrt to python detection so I guess the problem is that symlinks might still point to the old version. If this is the case I suggest you run python-updater and get rid of python-2.3 After sleeping on the problem and checking portage log files I find I had the following sequence of events. emerge python-2.4.4-r6 (regular update) emerge python-2.3.6-r3 (due to it being flagged in a security advisory) So I did emerge python emerge python-updater and emerge pygobject then completed successfully. I guess I should get rid of python-2.3. ok, thanks for checking that. You should indeed get rid of 2.3 if there is no compelling reason to keep it (I suppose you should know that if it's the case). On side note, don't use "emerge python" if you just want to recompile it, it will clutter /var/lib/portage/world, prefer "emerge -1 python" (or --oneshot). The thing is that it will make it difficult for portage to figure out which dependencies to clean (with --depclean or unmerge-orphans) if you remove a program you wanted to test or just don't have a use for anymore. *** Bug 200045 has been marked as a duplicate of this bug. *** |