Nope, that does not succeed either. It compiles for like 2 hours then quits with
[...]
libtool: link: ar rc .libs/libitm.a aatree.o alloc.o alloc_c.o alloc_cpp.o barrier.o beginend.o clone.o eh_cpp.o local.o query.o retry.o rwlock.o useraction.o util.o sjlj.o tls.o method-serial.o method-gl.o method-ml.o x86_sse.o x86_avx.o futex.o
libtool: link: ranlib .libs/libitm.a
libtool: link: ( cd ".libs" && rm -f "libitm.la" && ln -s "../libitm.la" "libitm.la" )
make[4]: Leaving directory '/build/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libitm'
make[3]: Leaving directory '/build/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libitm'
make[2]: Leaving directory '/build/gcc9/src/gcc-build/x86_64-pc-linux-gnu/libitm'
make[1]: Leaving directory '/build/gcc9/src/gcc-build'
make: *** [Makefile:997: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Building package [gcc9] failed.
Cleaning up.
I wish the error message would print the location of the Makefile …
There is a Makefile in /var/lib/chrootbuild/build/gcc9/src/gcc-build, I assume that’s the one.
And there is a config.log, too.
Both don’t give me a clue. I can provide them through some cloud-service if anyone would be willing to inspect them.
Ah this is frustrating