On 20.11.19 22:38, Richard Earnshaw wrote: > On 20/11/2019 20:48, Bernd Schmidt wrote: >> On 11/20/19 8:27 PM, Mikael Pettersson wrote: >>> On Wed, Nov 20, 2019 at 3:16 PM Bernd Schmidt <bernds_...@t-online.de> >>> wrote: >>>> 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. >> >> There's a --disable-bootstrap configure option. >> >>>> 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/ >> >> Turns out I wasn't sufficiently familiar with how debian works. I was >> missing an "apt update" step. I kind of assumed a package like gcc would >> install out of the box (others did, things like emacs). >> >> >> Bernd >> > > If you're building gcc on debian/ubuntu you probably also want > > apt build-dep gcc > > to install all the packages needed for building the compiler.
that would be apt build-dep gcc-9. The former would only install the build dependencies of the gcc-defaults package.
