GCC is kind of a memory disaster… It is a shame the BSD folk switched from PCC to GCC back in the Tahoe days.. And the joke is nobody can even scare up a picture of a Tahoe! ..

I see ads for 128 & 256MB memory boards for 3000’s and 4000’s .. I wonder how far short does it run out of memory while compiling? Or if anyone has tried building with -O0 or -Os… but yeah both will result in slower exe’s.

I guess we should be grateful anything gets thrown at the m68k plate as everyone has moved on from the platform… Meanwhile the PPC ultimately went nowhere, and the x86 is still slogging away.

Ok, I understand your archeological motives.

I was a bit puzzled, because I’ve been using NetBSD on Amiga since 1.5.2 and I can see see a lot of work then went into it up until now. The newest release still works great on classic Amigas and even supports outrageously modern hardware like PCI network cards behind PCI bridges.

Naturally, there are also problems, newer gcc versions produce slower code and are more memory-hungry. Amiga port can’t compile itself now because of this (gcc runs out of memory).

Because NetBSD 1.0 is a historical release, it is the first version to include binaries for the Amiga.

This is also the same reason why I setup NetBSD 0.9 for the i386 from an archive I found, and how I resurrected NetBSD 0.8 from a partial CVS dump, along with missing files from NetBSD 0.9 & 386BSD 0.1 Pl24…

I guess you could run “modern” NetBSD for the Amiga if you so wished, but without a physical Amiga why would you?

the latest beta, #4 ethernet works now!