> On Oct 13, 2022, at 11:02 AM, emanuel stiebler <e...@e-bbes.com> wrote:
>
> On 9/28/2022 20:18, Paul Koning via cctalk wrote:
>> FWIW, I just tried building GCC 2.95.2 on my Linux system (Fedora Core 32,
>> GCC 10.3.1. It almost built, ran into an argument mismatch error message in
>> something called "chill". So if you want something that old it looks like
>> you'll have to start by building a less ancient version, say 4.8 or so, and
>> then use that to build the dinosaur.
>
> Which switches/options did you use?
> Last weekend I spent some cycles to try ...
I cheated a bit. My test was "can GCC V.old build at all". So I tried a
native build, not a cross-build. Cross-builds have their own set of issues and
it's been long enough that I no longer remember them well. That's what I would
suggest when dealing with old versions: first try a native (or i386 if you have
x86_64) build to see what, if any, issues you need to handle just for the
generic old GCC. Given that you have that working, you can then do the
cross-build. For example, if you need a GCC V.medium to build the GCC
V.ancient, discovering that first makes things easier.
Yes, you'd have to start by finding an old enough binutils that supports the
target platform. With that in place, you can then build gcc for that platform.
paul
> I can build the binutils around 2.32, emitting elf
> No luck at all, getting gcc to compile. Support for the i860 was removed very
> early after 4.0, going back to 3.x versions fails as they can't compile on 64
> bit systems. (and also never used ELF, but COFF?)
>
> So stuck a little at the moment, I guess I have to install some linux 32 bit
> version, and try again ...
>
