| 1 |
Am Sat, 15 Oct 2011 19:50:23 +0100 |
| 2 |
schrieb Mick <michaelkintzios@×××××.com>: |
| 3 |
|
| 4 |
>[snip snip] |
| 5 |
> [snip...] |
| 6 |
> |
| 7 |
> > > Thank you! :-) |
| 8 |
> > |
| 9 |
> > you're welcome ;) |
| 10 |
> > its really easy to help you because you provide the right |
| 11 |
> > information =) |
| 12 |
> |
| 13 |
> To save me asking next time ... how did you know that pax-utils was |
| 14 |
> to blame? |
| 15 |
|
| 16 |
i saw this error: |
| 17 |
|
| 18 |
> /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226: |
| 19 |
> scanelf: command not found |
| 20 |
> * ERROR: sys-libs/pam-1.1.4 failed (install phase): |
| 21 |
|
| 22 |
and with |
| 23 |
|
| 24 |
% equery b scanelf |
| 25 |
* Searching for scanelf ... |
| 26 |
app-misc/pax-utils-0.2.2 (/usr/bin/scanelf) |
| 27 |
|
| 28 |
i knew that it belonged to pax-utils. that only works, if a package |
| 29 |
owning that binary is installed. if there wasn't, i would have used a |
| 30 |
web search engine. the results normally contain man pages saying which |
| 31 |
package the command belongs to. |
| 32 |
|
| 33 |
that means either /usr/bin/scanelf is missing or /usr/bin is not in the |
| 34 |
path (at least not in the environment of portage). i thought the latter |
| 35 |
would be unlikely :) |
Archives