On Wed, 24 Dec 2014 09:55:37 +0000, Vincent Sanders wrote: > as we discovered with beos, gcc 2.95 support is a bit hit and > miss. Though I beleive the main issue there was g++, even so I fear > 2.95 is too primative and is almost 14 years old at this point.
I agree we shouldn't go back to such an old version. > > There are loads of patches here: > > https://github.com/cahirwpz/m68k-amigaos-toolchain > > > > There are an excessive number and I have no idea which are relevant. > > That is terrifying, I really do think that if they want continuing > compiler support they need to look at a modern gcc version or a clang > port. And getting the patches merged back upstream would be a good idea too. It looks like that must never have happened for m68k-amigaos. > Alas wishing does not make it so, being pragmatic, if there is a > "cannonical" cross toolchain for the target I might be persuaded to > put it on the CI as long as we can "package" it under /opt/netsurf > correctly so builds are repeatbale. I dislike this a lot but if it is > the only way... I'd rather get the official 3.4.6 source and import the patches we need from that repo (even if that's all of them under patches/gcc-3.4.6). I did try building it with our current patches but it clearly needs more as I get errors with register defines (REG_A0 etc), unless I'm doing something wrong. Chris
