On Wed, Nov 20, 2019 at 3:16 PM Bernd Schmidt <bernds_...@t-online.de> wrote: > > On 11/20/19 2:50 PM, Mikael Pettersson wrote: > > On Mon, Nov 18, 2019 at 9:57 PM Mikael Pettersson <mikpeli...@gmail.com> > > wrote: > >> > >> On Mon, Nov 18, 2019 at 8:31 PM Bernd Schmidt <bernds_...@t-online.de> > >> wrote: > >>> > >>> Hi Mikael, > >>> > >>>> This fixed the problem, thanks. > >>> > >>> Could you also run the testsuite to see if you can reproduce the > >>> g++.old-deja failures Andreas reported? > >> > >> Yes, but it will probably take another week before the native > >> bootstrap (on aranym) and test suite run is finished. It's currently > >> in stage 2. > > Ugh, that suggests the stage2 compiler was miscompiled. That would be > nasty to track down. > > Probably best to just run tests on stage1 and hope something shows up.
Ok, how do I did that? I've always just done 'make -k check' after full bootstraps. I assume the stage 1 artifacts are the ones in the prev-* directories. > What distro are you using for native builds? The m68k debian I'm using > does not have an installable gcc package. I run a bespoke distro on m68k and sparc64, derived from Fedora but massively cut down in size, with target patches done by myself or ported from Debian and Gentoo as necessary. Debian/m68k not having a gcc package? That sounds odd; I see e.g. a gcc-9 in http://ftp.ports.debian.org/debian-ports/pool-m68k/main/g/
