This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PING^7][PATCH 0/4] Fix library testsuite compilation for build sysroot
- From: Jeff Law <law at redhat dot com>
- To: "Maciej W. Rozycki" <macro at wdc dot com>, gcc-patches at gcc dot gnu dot org
- Date: Sun, 26 Jan 2020 10:01:06 -0700
- Subject: Re: [PING^7][PATCH 0/4] Fix library testsuite compilation for build sysroot
- References: <alpine.LFD.2.21.1911081714120.13542@redsun52.ssa.fujisawa.hgst.com> <alpine.LFD.2.21.1912170000240.30965@redsun52.ssa.fujisawa.hgst.com> <6594B30D-743B-4B4C-81CE-11DD3EE87C8C@comcast.net> <alpine.LFD.2.21.2001210218440.15714@redsun52.ssa.fujisawa.hgst.com>
- Reply-to: law at redhat dot com
On Tue, 2020-01-21 at 02:19 +0000, Maciej W. Rozycki wrote:
> 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).
>
> Ping for the build system parts of:
>
> <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00767.html>
> <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00768.html>
OK. Sorry for the terrible slowness on this kit.
jeff