home *** CD-ROM | disk | FTP | other *** search
- gcc.2.7.2.3.1.I.README
- Oct 1997
-
- md5sum:
- 74ce335fe3bcac97b6297a3a394f9dfa gcc.2.7.2.3.1.I.b.tar.gz (~ 5MB)
-
- This archive contains the following pre-built
- binaries:
- gcc-2.7.2.3
- g77-0.5.21
- libg++-2.7.2
-
- built on and for the i386-next-nextstep4 platform. includes drivers
- for both
- i386-next-nextstep4
- and
- m68k-next-nexstep4 (a cross-compiler) (not done yet, if time permits)
- targets.
-
-
- NOTES
-
- Regarding the versioning of this package:
- I tacked on a .1 to the version of this port to represent my first attempt
- at porting gcc v2.7.2.3 to OpenStep. I hope this doesn't confuse people.
- (-;
-
- These have been built for and tested on OpenStep for Mach 4.2, but may also
- work on other versions. This build will most likely NOT work on NEXTSTEP
- 3.x and earlier. I used (for the most part) patches to gcc provided from
- ftp://nice.ethz.ch/users/chris/OS4/
- to get the newest gcc working form OpenStep for Mach 4.x.
-
- I was unable to build a dynamic (ala shared) library version of libg++,
- so if you use g++, at link time, you may get a bunch of linker warnings
- complaining about non-moveable code in libg++ and libstdc++. It still
- works. (??)
-
- 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.3.1.I.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-nextstep4 cross-compiler, you need the
- DeveloperLibs installed for m68k (in addition to i386).
-
-
- The CROSS-COMPILER (ignore this section, for now)
-
- It's a little tricky to use the cross-compiler,
- as it's usage differs a bit from NeXT's cc compiler.
- To produce m68k binaries, envoke gcc as:
- gcc -bm68k-next-nextstep4 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 <rdieter@math.unl.edu>
- Computer System Manager
- Universtity of Nebraska-Lincoln
- Department of Mathematics and Statistics
- http://www.math.unl.edu/~rdieter/
-
-