It took way too long to find a working dlibs. In the same effort, IвЂ™ve had the same luck with sozobon. Building anything native under emulation was an impossibility. Although I donвЂ™t know what the deal is, it seems the larger the GCC based program is the higher chance itвЂ™ll just crash on exit or force the next program to crash. I even got the 1987 Infocom interpreter running. So maybe I can complete the chain for Mint and MachTen. The one good thing that came out of this experience is that since I am building form i386 to 68000 I found that this setup uses the G++ linker which has endian swapping. And sure there is a MS-DOS version that the MS-DOS Player can run, but get ready for 8.3 filename renaming. All these ancient fileformats sure donвЂ™t help anything.

And sure there is but despite being able to build it on multiple platforms it never does anything useful. Not only is it just overall worse than ZIP, but there are 2 incompatible compression methods, like the introduction of LZD, which any of the good versions of UNZOO canвЂ™t deal with. Speaking of files, ZOO has to be the worst compressor ever. Just as I canвЂ™t for the life of me find the old original GNU libc. ItвЂ™s kind of annoying how all these seemingly tiny files get purged to save a few kb. Which has a lot of GCC2 hooks so I cheated on getting the 1.30 hello world by using the 2.5.8 pre-processor. Instead I got lucky with all three for pl98. There survives a pl95 binary and source package, but again no includes. There is a GCC 1.30 file on all the usual GNU mirrors but to save a few kb it has no headers, instead it wants you to reuse the ones from the 1.25 binary distribution. Amazingly the hardest thing to source is the include files. The reason why this was so freaking hard was how so much of key parts of gcc for the ST have been purged and what remains being scattered to the winds. I guess itвЂ™s not surprising that all the attention is to MiNT & MINIX rather than the native platform. I didnвЂ™t have much to go on, as ancient threads like this, or this end up unanswered or without any good conclusion. And not because of gcc or surprisingly ancient binutils. This was a lot harder than it should have been.

Putty or syncterm