When building a system in a separate root for another machine, two packages failed to build due to sandbox violations, triggered by "autotools_run_tool --at-m4flags aclocal -I m4 --install" in eautoreconf.
Created attachment 674452 [details] tpm2-tss build.log
Created attachment 674455 [details] powertop build.log
we need one ticket per package. Please create a new ticket for the other package(s)
I tried doing this setting ROOT to an empty root directory but I cannot replicate - it compiles just fine, no sandbox warning. Do you have a copy of var/tmp/portage/app-crypt/tpm2-tss-2.4.3/temp/aclocal.out ?
Created attachment 675793 [details] aclocal.out
Created attachment 675802 [details, diff] Fix possible missing BDEPEND on autotools-archive I still can't replicate it but I have an idea what might be wrong. Try patching the app-crypt/tpm2-tss-2.4.3.ebuild file with the following patch which adds a possible missing build dependency.
I did the edit, nothing changed. Indeed, I already have autotools-archive installed in /. I don't have it installed in $ROOT, but manually installing it there did not solve the bug either.
I can replicate this by having with a cross-compile by having autotools-archive on CBUILD (host) but not in CHOST (target). Both 2.4.6 and 3.1.0 have the same problem. Now that I can replicate it, after looking at the man page for aclocal, I think I know what the problem is. The problem is the way aclocal is invoked: aclocal -I /var/thinkpadT430s/usr/share/aclocal -I m4 --install --install "copies third-party files to the first -I directory". Unfortunately, that's $ROOT/usr/share/aclocal and not m4. The -I arguments need to be reversed.
Fixed by the autotools.eclass changes in linked bug.