| View previous topic :: View next topic |
| Author |
Message |
ootawata
n00b
Joined: 10 Nov 2007
Posts: 14
|
 Posted: Tue Mar 11, 2008 2:13 am Post subject: Failed to emerge Parley, reason is: "Failed running acl |
 |
|
I've done quite a bit of "revdep-update" on my computer because I kept on trying to get "libext.so.0" to be found by applications that needed to read it. Anyway, after a long day I've finally managed to get my compuer running properly with no broken packages, but emerging parley still comes up with this error:
| Code: | | Failed Running aclocal ! |
which is on the first package it attempts to emerge:
| Code: | | app-crypt/gpgme-1.1.6 |
My best guess is that I'm missing a use flag somewhere, but I've never encountered this problem and search results in the FAQs returned nothing for aclocal.
Here are my current USE flags:
| Code: | [ebuild U ] app-crypt/gpgme-1.1.6 [1.1.2-r1] USE="-pth%"
[ebuild N ] dev-util/boost-build-1.34.1 USE="python"
[ebuild N ] dev-libs/boost-1.34.1-r2 USE="-debug -doc -icu -pyste -tools"
[ebuild N ] kde-base/kdepimlibs-4.0.1 USE="-debug -htmlhandbook -ldap -sasl -test"
[ebuild N ] kde-base/libkdeedu-4.0.1 USE="-debug"
[ebuild N ] kde-base/parley-4.0.1 USE="-debug -htmlhandbook" |
I'm not very good at judging when I want to use a flag, but I do know to not use "debug" and "doc" since I know I'll never use them.
Is there a good website to learn more about USE flags? (I've looked at the gentoo-wiki, didn't seem to help much).
Thanks alot for any help |
|
| Back to top |
|
 |
ootawata
n00b
Joined: 10 Nov 2007
Posts: 14
|
| Posted: Tue Mar 11, 2008 6:01 pm Post subject: |
|
|
| Did I post this in the wrong section? |
|
| Back to top |
|
|
Theimon
Tux's lil' helper
Joined: 16 Mar 2007
Posts: 99
Location: Netherlands
|
| Posted: Wed Mar 12, 2008 4:59 am Post subject: |
|
|
Did you update libtool recently by any chance? I had the same error (on another package) and with me the problem was a new version of libtool which didn't seem to work with other packages. It couldn't be found apparently. Emerging the previous verison of libtool solved it for me.
_________________
It doesn't matter what's right, it's only wrong if you get caught. |
|
| Back to top |
|
|
|
Desktop Environments
