On Fri, 20 Dec 2019, Mike Stump wrote: > >> This patch series addresses a problem with the testsuite compiler being > >> set up across libatomic, libffi, libgo, libgomp with no correlation > >> whatsoever to the target compiler being used in GCC compilation. > >> Consequently there in no arrangement made to set up the compilation > >> sysroot according to the build sysroot specified for GCC compilation, > >> causing a catastrophic failure across the testsuites affected from the > >> inability to link executables. > > > > Ping for: > > > > <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00767.html> > > <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00768.html> > > <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00770.html> > > Hum... I'm wondering who should review this... Feels like I should, > the problem is it intertwines with the build system as well. So, let me > approve the testsuite parts so that can clear the way for someone else > to approve the remaining bits (if not obvious).
Thanks for your review; I have applied 4/4 as it doesn't contain any non-testsuite parts and will continue pinging 1/4 and 2/4 for the build system bits then (3/4 has been already committed by the Go maintainer). > Please do watch out for breakages as it goes in. Thanks. Sure! Maciej
