Mark Wielaard <m...@klomp.wildebeest.org>: > Apparently less complete, but there is also > https://ftp.gnu.org/old-gnu/gcc/ > Which does have some old diff files to reconstruct some missing versions.
There are quite a few ancient preserved release tarballs out there Here is the list of reconstructable pre-r3 releases as as I now know it: 0.9 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-0.9.tar.bz2 1.21 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.21.tar.bz2 1.22 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.22.tar.bz2 1.23 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.23-1.24.bz2 1.24 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.24-1.25.bz2 1.25 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.25-1.26.bz2 1.26 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.26-1.27.bz2 1.27 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.27.tar.bz2 1.28 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.28-1.29.bz2 1.29 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.29-1.30.bz2 1.30 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.30-1.31.bz2 1.31 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.31.tar.bz2 1.32 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.31-1.32.bz2 1.33 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.32-1.33.bz2 1.34 ftp://gcc.gnu.org/pub/gcc/old-releases/patches/gcc.diff-1.32-1.34.bz2 1.35 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.35.tar.bz2 It looks like the relevant bits of ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-[12] and ftp://sourceware.org/pub/gcc/old-releases/gcc-[12] Incorporating these will be easy. What I would do is write script that does this: (a) checks to see if each tarball is mirrored locally (b) if not, fetches it, applying forward or back diffs from the nearest whole version as required. (c) generates a sequence of reposurgeon incorporate commands to be included un the main lift script sbb says r3 is 1.36. I doubt r1 and r2 are anything other than Subversion directory creations, but people with easier access than me should check. After this life gets a little trickier. We have the following tarballs that might be of interest: 1.36 r3 ftp://gcc.org/pub/gcc/old-releases/gcc-1/gcc-1.36.tar.bz2 1.37 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.37.tar.bz2 1.38 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.38.tar.bz2 1.39 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.39.tar.bz2 1.40 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.40.tar.bz2 1.41 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.41.tar.bz2 1.42 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-1.42.tar.bz2 2.0 r358 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.8.tar.bz2 2.1 r586 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.1.tar.bz2 3.2.2 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.2.2.tar.bz2 2.3.3 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.3.3.tar.bz2 2.4.5 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.4.5.tar.bz2 2.5.8 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.5.8.tar.bz2 2.6.3 ? ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.6.3.tar.bz2 2.7.2 r10608 ftp://gcc.gnu.org/pub/gcc/old-releases/gcc-1/gcc-2.7.2.tar.bz2 Before we can do anything with these, we need to identify which Subversion revsion each one with a ? belongs to. I've added three of ssb's identifications. For completeness I note thse for which we have no tarballs: r1184 = 2.2, r2674 = 2.3.1, r4493 = 2.4.0 "minus two swapped commits", r5867 = 2.5.0, r7771 = 2.6.0, r9996 = 2.7.0. This recomstruction is being tracked here: https://gitlab.com/esr/gcc-conversion/issues/4 -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
