Top-posting as inline replies don't fit here. auto* errors can be tricky to solve, in my experience they tend to be once off weird errors when packages can't quite make sense out of what the auto* scripts are telling them.
Let's get some facts on the table so we can proceed: Which packages were failing originally? What versions of the various auto* packages do you have installed? When did you last resync the tree? P.S. You've no doubt seen that forum posts have a high hit-rate of "throw stuff at the wall and see what sticks", the posts you mention show that happening. Randomly masking stuff hoping it will work is not a good fault-finding technique :-) On 02/05/2013 00:01, Rafa Griman wrote: > Hi Alan, > > On Wed, May 1, 2013 at 11:26 PM, Alan McKinnon <alan.mckin...@gmail.com> > wrote: >> On 01/05/2013 23:05, Rafa Griman wrote: >>> Hi all :) >>> >>> Got some problems with aclocal :( When running: >>> >>> emerge -avDuN --with-bdeps=y world >>> >>> I get a whole bunch of packages who won't install nor upgrade with the >>> following error: >>> >>> Failed Running aclocal ! >>> >>> Looking through the Forums I saw I've got to mask autoconf. >> >> You got that from the Forums, huh? > > > Yup. I also saw a post saying he solved his issue by removing all the > versions except the latest one. Tried that too and portage keeps > rebuilding both versions: > > # equery list autoconf > * Searching for autoconf ... > [IP-] [ ] sys-devel/autoconf-2.13:2.1 > [IP-] [ ] sys-devel/autoconf-2.69:2.5 > > > >> Um yeah, well, signal to noise there is out the roof. >> >> I'd be double checking exactly what the Forum user said, as masking >> autoconf seems to me like a guaranteed way to get portage to whinge very >> loud and very long (half the tree DEPENDS on autoconf). > > > That's why I'm writing, sounds a bit weird to me ... > > >> Maybe the poster meant to mask a /specific/ version of autoconf? >> Start by masking the latest version you installed and proceed from there. > > > Tried that too but still get the same error: > > Failed Running aclocal ! > > No matter what version I mask in: > > vim /etc/portage/package.mask/masked > > I get that same error. I have rebuilt automake and automake-wrapper > too just in case. Have also run: > > revdep-rebuild > > emerge --depclean > > perl-cleaner --all > > python-updater > > I have also unmerged the previous versions of automake and left the > latest, but portage rebuilds 2 other versions so I end up with: > > # equery list automake > * Searching for automake ... > [IP-] [ ] sys-devel/automake-1.10.3:1.10 > [IP-] [ ] sys-devel/automake-1.11.6:1.11 > [IP-] [ ] sys-devel/automake-1.13.1:1.13 > > > TIA > > Rafa > -- Alan McKinnon alan.mckin...@gmail.com
