1 |
Jackie <jiangjun12321@×××××.com> wrote: |
2 |
|
3 |
>在 Thu, 02 May 2013 06:39:02 +0800,Neil Bothwick <neil@××××××××××.uk> |
4 |
>写道: |
5 |
> |
6 |
>> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote: |
7 |
>> |
8 |
>>> Got some problems with aclocal :( When running: |
9 |
>>> |
10 |
>>> emerge -avDuN --with-bdeps=y world |
11 |
>>> |
12 |
>>> I get a whole bunch of packages who won't install nor upgrade with |
13 |
>the |
14 |
>>> following error: |
15 |
>>> |
16 |
>>> Failed Running aclocal ! |
17 |
>>> |
18 |
>>> Looking through the Forums I saw I've got to mask autoconf. So I |
19 |
>added |
20 |
>>> autoconf to: |
21 |
>>> |
22 |
>>> /etc/portage/package.mask |
23 |
>> |
24 |
>> That's what you get with the forums, aclocal isn't even part of |
25 |
>autoconf, |
26 |
>> it is provided by automake-wrapper. |
27 |
>> |
28 |
>>> And now I get a whole bunch of errors saying autoconf is masked and |
29 |
>I |
30 |
>>> have to unmask it ... which takes me back to step 1 ... |
31 |
>> |
32 |
>> There have been issues with automake-1.13. I have seen a similar |
33 |
>error on |
34 |
>> one package and worked around it with |
35 |
>> |
36 |
>> WANT_AUTOMAKE=1.12 emerge -1 cat/package |
37 |
> |
38 |
> |
39 |
>Also get the same problem here two days ago when I was trying to emerge |
40 |
> |
41 |
>bootchart2.After searching through the Internet I also noticed that it |
42 |
>had |
43 |
>sth to do with automake-1.13,I masked it and problem solved. |
44 |
|
45 |
Hit this a few weeks ago. |
46 |
|
47 |
I ended up unmasking new revisions as fixes for the packages having issues were already in the tree. |
48 |
|
49 |
-- |
50 |
Joost |
51 |
-- |
52 |
Sent from my Android phone with K-9 Mail. Please excuse my brevity. |