Dunno about g77, but...
I've got the whole log of the compile and can send it privately if anybody wants it.
2) openssl097 is out of date. The current version is 0.9.7c but 10.2-gcc3 has 0.9.7b.
You just need to selfupdate, 0.9.7c is in 10.2-gcc3 now. =)
This lead me to think of a way of leveraging the 10.2 *.info files for the 10.2-gcc3 tree.
Given that there's now an rsync backend to downloading *.info files, we could make use of symlinks to link most of the 10.2 files to the 10.2-gcc3 tree and have files in 10.2-gcc3 for those specific packages that need special treatment for gcc 3.3. This could be scripted to create the symlinks, and look in the *.info files to see if there's any mention of 3.1 or 3.3 to get an idea of what to do.
The info files are still developed using, and stored in, cvs, so we can't really do symlinks. rsync is great for end-users, but for package developers CVS is still king, and would never be replaced, except maybe with another SCM.
-- Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/ gpg: 6401 D02A A35F 55E9 D7DD 71C5 52EF A366 D3F6 65FE Standards are the industry's way of codifying obsolescence.
pgp00000.pgp
Description: PGP signature
