| 1 |
On 02/05/2013 17:09, Jackie wrote: |
| 2 |
> My problem was similiar to Rafa's,though I was compiling |
| 3 |
> dev-python/pygtk-2.24.0-r3.But I also got same autom4te & aclcal error |
| 4 |
> as Rafa.But I just masked automake-1.13.1 downgraded to automake-1.12.6 |
| 5 |
> and the compilation went through,then I unmasked automake-1.31.1 and |
| 6 |
> upgraded it back again.Maybe you can try it,too.Just to solve the |
| 7 |
> problem for now.(After I upgradeed automake to 1.13.1,I compiled |
| 8 |
> dev-python/pygtk-2.24.0-r3,the same error appeared again,so it seemed |
| 9 |
> that sth might be wrong with automake-1.13.1) |
| 10 |
|
| 11 |
The easiest way to deal with that if it's just a single package failing is |
| 12 |
|
| 13 |
WANT_AUTOMAKE=<version> emerge .... |
| 14 |
|
| 15 |
It tells portage to not try autodetect stuff but rather to use the SLOT |
| 16 |
specified by you. |
| 17 |
In this case though, the breakage seems to be somewhat more than just a |
| 18 |
few packages, which probably requires masking till automake is fixed |
| 19 |
properly. |
| 20 |
|
| 21 |
The whole thing is rather a scathing comment at whoever committed the |
| 22 |
automake change, as quite obviously the correct answer to "How much |
| 23 |
testing did you do?" is "very little if any" |
| 24 |
|
| 25 |
-- |
| 26 |
Alan McKinnon |
| 27 |
alan.mckinnon@×××××.com |
Archives