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