re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b #) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096: No space left on device

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR port-sun2/56158; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
Cc: gnats-bugs%netbsd.org@localhost, Chris Pinnock <cjep%netbsd.org@localhost>,
    gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
    Chris Pinnock <chris_pinnock%mac.com@localhost>
Subject: re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b #) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096: No space left on device
Date: Mon, 10 May 2021 07:18:02 +1000

 >   Oh and now it's verified: I don't export HAVE_GCC=3D3D10 anywhere.
 > (Though the initial GCC was a "gcc (Debian 10.2.1-6) 10.2.1 20210110",
 > which is now the system GCC and not the more recent one from the
 > "gcc-snapshot" DEB (which'd identify as "gcc (Debian 20210320-1)
 > 11.0.1 20210320 (experimental) [master revision
 > 3279a9a5a9a:6526c452d22:5f256a70a05fcfc5a1caf56678ceb12b4f87f781]").)
 
 as you previously said, the host compiler _should not_ affect
 what is being built for the target sun2.
 
 just to confirm that this isn't happening, running this will
 tell you what target GCC is being used:
 
    /var/lib/laminar/run/netbsd-sun2-m68000/nn/obj/tooldir.Linux-5.9.0-2-am=
 d64-x86_64/bin/m68010--netbsdelf-gcc -v
 
 (at least, i think that is your path.)
 
 
 
 .mrg.