Return to README-ENCAP CVS log

Up to [Early binutils] / binutils

Annotation of binutils/README-ENCAP, revision 1.1.1.1

1.1       root        1: 1/3/89 Pace Willisson
                      2: 
                      3: Here is what to do to bring up gcc & tools on an 80386 running system 5.3
                      4: (if you are adventurous and want to use the latest and greatest tools.
                      5: If you want it to be easy, check back in a couple of months.)
                      6: 
                      7: (There is no debugger support yet...)
                      8: 
                      9: All of these instructions assume you are using the usg compiler.  After
                     10: you get to the end, you could start over using the gnu compiler, but 
                     11: that may not work yet ...
                     12: 
                     13: First make gcc, cpp, and gnulib:
                     14: 
                     15:        cd .../gcc
                     16:        config.gcc i386gnu
                     17:        make install
                     18: 
                     19: (The i386gnu type was added a little after gcc-1.32)
                     20: (the install part doesn't really work - you will have to look at
                     21: what it tries to do, and do it by hand.)
                     22: 
                     23: Now, make the gnu assembler:
                     24: 
                     25:        cd .../gas
                     26:        make a386
                     27:        cp a386 /usr/local/lib/gcc-as
                     28: 
                     29: Now, make the other utilities:
                     30: 
                     31:        cd .../binutils
                     32: 
                     33: edit Makefile to turn on the CFLAGS for USG using COFF_ENCAPSULATE
                     34: 
                     35:        make
                     36:        cp ld /usr/local/lib/gcc-ld
                     37: 
                     38: Put the other programs (size nm strip ar objdump and ranlib) somewhere
                     39: handy, but don't clobber your usg programs.  I put them all in
                     40: /usr/gnu/gnucomp, and I have this shell script in my path under the name "gnu":
                     41: 
                     42:        exec /usr/gnu/gnucomp/$*
                     43: 
                     44: That way, I can say "gnu nm a.out", etc.
                     45: 
                     46: Convert the libraries to the encapsulated format:
                     47: 
                     48:        make libc.a
                     49:        cp libc.a /usr/local/lib/gnu/libc.a
                     50: 
                     51:        cp .../gcc/gnulib usg-gnulib
                     52:        make gnulib
                     53:        cp gnulib /usr/local/lib/gcc-gnulib
                     54: 
                     55:        robotussin /lib/crt0.o /usr/local/lib/gcc-crt0.o
                     56: 
                     57: Now, you should be able to use 'gcc' to compile programs.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.