gcc.2.7.2.2.N.README April 1996 This archive contains the following pre-built binaries: gcc-2.7.2.2 g77-0.5.20 libg++-2.7.2 built on and for the m68k-next-nextstep3 platform. includes drivers for both m68k-next-nextstep3 and i386-next-nextstep3 (a cross-compiler) targets. NOTES These have been built for and tested on NEXTSTEP 3.3, but may also work on other versions. This build will mostly like NOT work on OpenStep 4.0 and later. The included libraries (libf2c.a and libg++.a) have been stripped to save installation space. This may impeed debugging (using gdb) efforts if you are building programs using those libraries. INSTALLATION unpack into /usr/local, and you're done. Issue the following commands as root: cd /usr/local gnutar xzvf /PathToArchive/gcc.2.7.2.2.N.b.tar.gz NOTE: you STILL need the nexstep developer packages installed in order to use this, as it uses NeXT's supplied C libraries. Also, in order to use the m68k-next-nextstep3 cross-compiler, you need the DeveloperLibs installed for m68k (in addition to i386). Now if someone ported glibc (GNU libc) to NEXTSTEP, that would be something! The CROSS-COMPILER It's a little tricky to use the cross-compiler, as it's usage differs a bit from NeXT's cc compiler. To produce i386k binaries, envoke gcc as: gcc -bi386-next-nextstep3 foo.c FAT binary NOTE: gcc cannot (easily) create FAT binaries, at least not in the same sense of NeXT's cc, ie, cc -arch m68k -arch i386 foo.c With gcc, you need to create to separate binaries, and then use lipo. Also, the cross-compiler doesn't look in /usr/local/lib for linking libraries, by default, like the native compiler does. If you need to link against items in /usr/local/lib, you'll need to pass the option -L/usr/local/lib (ie, by adding to CFLAGS or LDFLAGS) to the linker (ld). CREDITS GNU Software http://www.gnu.ai.mit.edu/ Packager Rex Dieter Computer System Manager Universtity of Nebraska-Lincoln Department of Mathematics and Statistics http://www.math.unl.edu/~rdieter/