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

[Chris Pinnock <chris_pinnock%mac.com@localhost>]

Once you have a toolchain built, those tools (which are GCC & friends usually) build everything else. The -a doesn’t hurt I don’t think - it’s more relevant when there are multiple targets (e.g. evbarm & friends).

I’m doing something very similar - I’ll mail you separately.
C

> On 8 May 2021, at 21:27, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> wrote:
> 
> Hi Chris,
> 
> On Sat, 2021-05-08 21:02:05 +0100, Chris Pinnock <chris_pinnock%mac.com@localhost> wrote:
>> What system are you using to build with? I have successfully built a
>> sun2 release today on Debian 10. You might do better with the
>> standard gcc.
> 
> It's a Debian sid / Debian unstable system, so everything is quite
> new. And for the mentioned build
> (http://toolchain.lug-owl.de:8080/jobs/netbsd-sun2-m68000 /
> http://toolchain.lug-owl.de:8080/log/netbsd-sun2-m68000), the
> "gcc-snapshot" compiler (as per log, it was:
> 
> 	/usr/lib/gcc-snapshot/bin/gcc --version
> 	gcc (Debian 20210320-1) 11.0.1 20210320 (experimental) [master revision 3279a9a5a9a:6526c452d22:5f256a70a05fcfc5a1caf56678ceb12b4f87f781]
> 
>> BTW for sun2, you can just specific -m sun2 (you don’t need the -a).
> 
>  Does that hurt? I hope it doesn't! Because I've setup jobs to just
> work down all the targets listed by "./build-sh list-arch", so both
> machine and arch are supplied all the time.
> 
>  I'll schedule another build for sun2/m68000 using "just" the older
> system compiler. Let's see what's happening with this. (Queued as
> http://toolchain.lug-owl.de:8080/jobs/netbsd-sun2-m68000/11, but as
> I'm still testing, I might kill/restart the jobs, so. This time, we
> have:
> 
> 	gcc --version
> 	gcc (Debian 10.2.1-6) 10.2.1 20210110
> )
> 
> However, as far as I understand, the NetBSD (native) parts should have
> been built with NetBSD's own cross-gcc, no?
> 
> MfG, JBG
> 
> --