Summary: | libcap-1.10-r5 emerge fails because it tries to compile in src_install | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kenyon Ralph <kenyon> |
Component: | [OLD] Library | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
sys-libs/libcap-1.10-r5 failed emerge log
out put of emerge -1v libcap --debug >& logfile |
Description
Kenyon Ralph
2006-03-14 14:26:41 UTC
Created attachment 82151 [details]
sys-libs/libcap-1.10-r5 failed emerge log
Created attachment 82153 [details]
out put of emerge -1v libcap --debug >& logfile
uhh, your second logfile showed it emerging properly (In reply to comment #3) > uhh, your second logfile showed it emerging properly Hah, well that's strange. Out of the at least 30 times I've tried it now, that was the only time it succeeded. Trying to emerge libcap fails for me with a nearly identical failed message as the attached failed emerge log albeit with different line numbers, but identical missing include error messages. I tried re-emergeing python-2.4.2-r1 with no luck. However, if I remove 1-10-python.patch from the libcap ebuild, libcap finishes the emerge successfully. I also had to remove libcap-1.10-r4-staticfix.diff because it no longer patched cleanly with the removal of 1-10-python.patch. This is on amd64 machine. Additional information upon request. are you using a tmpfs mount with /var/tmp/portage ? (In reply to comment #6) > are you using a tmpfs mount with /var/tmp/portage ? No. Since I reported this bug, I've reinstalled my system and it's all stable now, no more ~x86 in ACCEPT_KEYWORDS. libcap-1.10-r5 emerges fine now, so this bug could be marked invalid for my part, unless Brian Merrill still has the problem as in Comment #5. k |