* Applying squid-3.1.15-gentoo.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/net-proxy/squid-3.1.22/work/squid-3.1.22' ... * Running eautoreconf in '/var/tmp/portage/net-proxy/squid-3.1.22/work/squid-3.1.22/lib/libTrie' ... * Running eautoreconf in '/var/tmp/portage/net-proxy/squid-3.1.22/work/squid-3.1.22/helpers/negotiate_auth/squid_kerb_auth' ... * Running eautoreconf in '/var/tmp/portage/net-proxy/squid-3.1.22/work/squid-3.1.22/libltdl' ... * Running aclocal ... * Running aclocal ... * Running libtoolize --install --copy --force --automake ... [ ok ] * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal ... [ !! ] * Failed Running aclocal ! * * Include in your bugreport the contents of: [ ok ] * * /var/tmp/portage/net-proxy/squid-3.1.22/temp/aclocal-2.out ***** aclocal ***** ***** PWD: /var/tmp/portage/net-proxy/squid-3.1.22/work/squid-3.1.22/libltdl ***** aclocal aclocal-1.11: `configure.ac' or `configure.in' is required
Looks like a race condition. Try a few times to see if it goes through. Also, please see if MAKEOPTS=-j1 helps in make.conf.
this is always reproducible and -j1 fails too
I will have a look. In any case, this is not a regression.
(In reply to comment #3) > I will have a look. In any case, this is not a regression. No, I'm unable to reproduce to actual stable
Well, in that case something is broken on your system. There is no code change in the build system between 3.1.19 and 3.1.22 to explain this behaviour. They are practically the same. Please attach your emerge --info and ask someone else from the arch team to test as well.
Seems not anymore reproducible, also, works in my other chroot.
*** Bug 447798 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 419685 ***
