| 1 |
Top-posting as inline replies don't fit here. |
| 2 |
|
| 3 |
auto* errors can be tricky to solve, in my experience they tend to be |
| 4 |
once off weird errors when packages can't quite make sense out of what |
| 5 |
the auto* scripts are telling them. |
| 6 |
|
| 7 |
Let's get some facts on the table so we can proceed: |
| 8 |
|
| 9 |
Which packages were failing originally? |
| 10 |
What versions of the various auto* packages do you have installed? |
| 11 |
When did you last resync the tree? |
| 12 |
|
| 13 |
|
| 14 |
P.S. You've no doubt seen that forum posts have a high hit-rate of |
| 15 |
"throw stuff at the wall and see what sticks", the posts you mention |
| 16 |
show that happening. Randomly masking stuff hoping it will work is not a |
| 17 |
good fault-finding technique :-) |
| 18 |
|
| 19 |
|
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
On 02/05/2013 00:01, Rafa Griman wrote: |
| 24 |
> Hi Alan, |
| 25 |
> |
| 26 |
> On Wed, May 1, 2013 at 11:26 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 27 |
>> On 01/05/2013 23:05, Rafa Griman wrote: |
| 28 |
>>> Hi all :) |
| 29 |
>>> |
| 30 |
>>> Got some problems with aclocal :( When running: |
| 31 |
>>> |
| 32 |
>>> emerge -avDuN --with-bdeps=y world |
| 33 |
>>> |
| 34 |
>>> I get a whole bunch of packages who won't install nor upgrade with the |
| 35 |
>>> following error: |
| 36 |
>>> |
| 37 |
>>> Failed Running aclocal ! |
| 38 |
>>> |
| 39 |
>>> Looking through the Forums I saw I've got to mask autoconf. |
| 40 |
>> |
| 41 |
>> You got that from the Forums, huh? |
| 42 |
> |
| 43 |
> |
| 44 |
> Yup. I also saw a post saying he solved his issue by removing all the |
| 45 |
> versions except the latest one. Tried that too and portage keeps |
| 46 |
> rebuilding both versions: |
| 47 |
> |
| 48 |
> # equery list autoconf |
| 49 |
> * Searching for autoconf ... |
| 50 |
> [IP-] [ ] sys-devel/autoconf-2.13:2.1 |
| 51 |
> [IP-] [ ] sys-devel/autoconf-2.69:2.5 |
| 52 |
> |
| 53 |
> |
| 54 |
> |
| 55 |
>> Um yeah, well, signal to noise there is out the roof. |
| 56 |
>> |
| 57 |
>> I'd be double checking exactly what the Forum user said, as masking |
| 58 |
>> autoconf seems to me like a guaranteed way to get portage to whinge very |
| 59 |
>> loud and very long (half the tree DEPENDS on autoconf). |
| 60 |
> |
| 61 |
> |
| 62 |
> That's why I'm writing, sounds a bit weird to me ... |
| 63 |
> |
| 64 |
> |
| 65 |
>> Maybe the poster meant to mask a /specific/ version of autoconf? |
| 66 |
>> Start by masking the latest version you installed and proceed from there. |
| 67 |
> |
| 68 |
> |
| 69 |
> Tried that too but still get the same error: |
| 70 |
> |
| 71 |
> Failed Running aclocal ! |
| 72 |
> |
| 73 |
> No matter what version I mask in: |
| 74 |
> |
| 75 |
> vim /etc/portage/package.mask/masked |
| 76 |
> |
| 77 |
> I get that same error. I have rebuilt automake and automake-wrapper |
| 78 |
> too just in case. Have also run: |
| 79 |
> |
| 80 |
> revdep-rebuild |
| 81 |
> |
| 82 |
> emerge --depclean |
| 83 |
> |
| 84 |
> perl-cleaner --all |
| 85 |
> |
| 86 |
> python-updater |
| 87 |
> |
| 88 |
> I have also unmerged the previous versions of automake and left the |
| 89 |
> latest, but portage rebuilds 2 other versions so I end up with: |
| 90 |
> |
| 91 |
> # equery list automake |
| 92 |
> * Searching for automake ... |
| 93 |
> [IP-] [ ] sys-devel/automake-1.10.3:1.10 |
| 94 |
> [IP-] [ ] sys-devel/automake-1.11.6:1.11 |
| 95 |
> [IP-] [ ] sys-devel/automake-1.13.1:1.13 |
| 96 |
> |
| 97 |
> |
| 98 |
> TIA |
| 99 |
> |
| 100 |
> Rafa |
| 101 |
> |
| 102 |
|
| 103 |
|
| 104 |
-- |
| 105 |
Alan McKinnon |
| 106 |
alan.mckinnon@×××××.com |
Archives