Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!mips!ultra!jimh From: jimh@ultra.com (Jim Hurley) Newsgroups: comp.sys.atari.st.tech Subject: Re: g++ Part comment, part question. Message-ID: <1991Feb21.181331.784@ultra.com> Date: 21 Feb 91 18:13:31 GMT References: <10745@jarthur.Claremont.EDU> <1991Feb17.234055.25173@NCoast.ORG> Organization: Ultra Network Technologies Lines: 52 In <1991Feb17.234055.25173@NCoast.ORG> bjsjr@NCoast.ORG (Bill Shroka) writes: >In article gjh@hplb.hpl.hp.com (Graham Higgins) writes: >> >>GCC versions have reached 1.39 on terminator,but only 1.37.1 appears in binary >>form (1.38 and 1.39 are in "diff" form). >> >>What I'm concerned about is that the GCC-using ST community is dependent on >>*someone else* doing the cross-compilation to get these diffs into binary >>format. (Or are they --- has anyone got a GCC v1.39 executable by compiling it >>up on an ST?) >I've compiled GCC 1.39 on my ST. I used the GULMAKE package that was created >by Jim Hurley. It's a series of Gulam scripts that automates the make process. >It takes about 2 or 3 hours to completely compile GCC and I experienced >relatively few problems, though it's something I'd rather not do very often :-) >-- >-------------------------------------------------------------------------- >Bill Shroka >bjsjr@NCoast.ORG >ncoast!bjsjr@usenet.INS.CWRU.Edu As Bill says, this is a tedious process on the ST, but it is doable. The only problems I have ever encountered were occasional 'make' errors, or maybe gulam-make interaction errors. However, re-executing the 'make' picked up right where it left off. So far, I haven't had any problems compiling or porting the GNU software, (with the exception of 'less'), but you will probably need 4Mbytes and a 32Meg HD partition (to store all the source in one directory). Thanks to J. Bammi, et al, and their excellent gnulibs. Another error comes to mind now - the version 1.37 'ar' aborts when it tries to rename the final library archive, but it was built OK and you can manually rename it. This was fixed in a later release of the package. In the 'gulmake' package I listed the complete directory structure I used, to make things as fool-proof as possible. Don't forget to start with the 'zoo' from Bammi's package first! Otherwise you need to be careful to replace filename '_' with '-' unpacked from older 'zoo' programs. A question comes to mind - the GNU 'tar' program seems to have extremely small block sizes built into it, at least this is how I explain the chain-saw-like buzzing off my hard disk while unpacking files. I've never heard that sort of seek noise from any other program. Does anyone know what's happening here? I haven't looked at the source. -- Jim Hurley --> jimh@ultra.com ...!ames!ultra!jimh (408) 922-0100 Ultra Network Technologies / 101 Daggett Drive / San Jose CA 95134