home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Fresh Fish 7
/
FreshFishVol7.bin
/
bbs
/
gnu
/
gcc-2.3.3-src.lha
/
GNU
/
src
/
amiga
/
gcc-2.3.3
/
gcc.info-5
(
.txt
)
< prev
next >
Wrap
GNU Info File
|
1994-02-06
|
47KB
|
902 lines
This is Info file gcc.info, produced by Makeinfo-1.49 from the input
file gcc.texi.
This file documents the use and the internals of the GNU compiler.
Copyright (C) 1988, 1989, 1992 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided also
that the sections entitled "GNU General Public License" and "Protect
Your Freedom--Fight `Look And Feel'" are included exactly as in the
original, and provided that the entire resulting derived work is
distributed under the terms of a permission notice identical to this
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that the sections entitled "GNU General Public
License" and "Protect Your Freedom--Fight `Look And Feel'", and this
permission notice, may be included in translations approved by the Free
Software Foundation instead of in the original English.
File: gcc.info, Node: Unos Install, Next: VMS Install, Prev: 3b1 Install, Up: Installation
Installing GNU CC on Unos
=========================
Use `configure unos' for building on Unos.
The Unos assembler is named `casm' instead of `as'. For some
strange reason linking `/bin/as' to `/bin/casm' changes the behavior,
and does not work. So, when installing GNU CC, you should install the
following script as `as' in the subdirectory where the passes of GCC
are installed:
#!/bin/sh
casm $*
The default Unos library is named `libunos.a' instead of `libc.a'.
To allow GNU CC to function, either change all references to `-lc' in
`gcc.c' to `-lunos' or link `/lib/libc.a' to `/lib/libunos.a'.
When compiling GNU CC with the standard compiler, to overcome bugs in
the support of `alloca', do not use `-O' when making stage 2. Then use
the stage 2 compiler with `-O' to make the stage 3 compiler. This
compiler will have the same characteristics as the usual stage 2
compiler on other systems. Use it to make a stage 4 compiler and
compare that with stage 3 to verify proper compilation.
(Perhaps simply defining `ALLOCA' in `x-crds' as described in the
comments there will make the above paragraph superfluous. Please
inform us of whether this works.)
Unos uses memory segmentation instead of demand paging, so you will
need a lot of memory. 5 Mb is barely enough if no other tasks are
running. If linking `cc1' fails, try putting the object files into a
library and linking from that library.
File: gcc.info, Node: VMS Install, Next: WE32K Install, Prev: Unos Install, Up: Installation
Installing GNU CC on VMS
========================
The VMS version of GNU CC is distributed in a backup saveset
containing both source code and precompiled binaries.
To install the `gcc' command so you can use the compiler easily, in
the same manner as you use the VMS C compiler, you must install the VMS
CLD file for GNU CC as follows:
1. Define the VMS logical names `GNU_CC' and `GNU_CC_INCLUDE' to
point to the directories where the GNU CC executables
(`gcc-cpp.exe', `gcc-cc1.exe', etc.) and the C include files are
kept respectively. This should be done with the commands:
$ assign /system /translation=concealed -
disk:[gcc.] gnu_cc
$ assign /system /translation=concealed -
disk:[gcc.include.] gnu_cc_include
with the appropriate disk and directory names. These commands can
be placed in your system startup file so they will be executed
whenever the machine is rebooted. You may, if you choose, do this
via the `GCC_INSTALL.COM' script in the `[GCC]' directory.
2. Install the `GCC' command with the command line:
$ set command /table=sys$common:[syslib]dcltables -
/output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc
$ install replace sys$common:[syslib]dcltables
3. To install the help file, do the following:
$ library/help sys$library:helplib.hlb gcc.hlp
Now you can invoke the compiler with a command like `gcc /verbose
file.c', which is equivalent to the command `gcc -v -c file.c' in
Unix.
If you wish to use GNU C++ you must first install GNU CC, and then
perform the following steps:
1. Define the VMS logical name `GNU_GXX_INCLUDE' to point to the
directory where the preprocessor will search for the C++ header
files. This can be done with the command:
$ assign /system /translation=concealed -
disk:[gcc.gxx_include.] gnu_gxx_include
with the appropriate disk and directory name. If you are going to
be using libg++, this is where the libg++ install procedure will
install the libg++ header files.
2. Obtain the file `gcc-cc1plus.exe', and place this in the same
directory that `gcc-cc1.exe' is kept.
The GNU C++ compiler can be invoked with a command like `gcc /plus
/verbose file.cc', which is equivalent to the command `g++ -v -c
file.cc' in Unix.
We try to put corresponding binaries and sources on the VMS
distribution tape. But sometimes the binaries will be from an older
version than the sources, because we don't always have time to update
them. (Use the `/version' option to determine the version number of
the binaries and compare it with the source file `version.c' to tell
whether this is so.) In this case, you should use the binaries you get
to recompile the sources. If you must recompile, here is how:
1. Execute the command procedure `vmsconfig.com' to copy files
`vax-vms.h', `xm-vax-vms.h', `vax.c' and `vax.md' to `tm.h',
`config.h', `aux-output.c', and `md.' respectively, and to create
files `tconfig.h' and `hconfig.h'. This procedure also creates
several linker option files used by `make-cc1.com' and a data file
used by `make-l2.com'.
$ @vmsconfig.com
2. Setup the logical names and command tables as defined above. In
addition, define the VMS logical name `GNU_BISON' to point at the
to the directories where the Bison executable is kept. This
should be done with the command:
$ assign /system /translation=concealed -
disk:[bison.] gnu_bison
You may, if you choose, use the `INSTALL_BISON.COM' script in the
`[BISON]' directory.
3. Install the `BISON' command with the command line:
$ set command /table=sys$common:[syslib]dcltables -
/output=sys$common:[syslib]dcltables -
gnu_bison:[000000]bison
$ install replace sys$common:[syslib]dcltables
4. Type `@make-gcc' to recompile everything (alternatively, you may
submit the file `make-gcc.com' to a batch queue). If you wish to
build the GNU C++ compiler as well as the GNU CC compiler, you must
first edit `make-gcc.com' and follow the instructions that appear
in the comments.
5. In order to use GCC, you need a library of functions which GCC
compiled code will call to perform certain tasks, and these
functions are defined in the file `libgcc2.c'. To compile this
you should use the command procedure `make-l2.com', which will
generate the library `libgcc2.olb'. `libgcc2.olb' should be built
using the compiler built from the same distribution that
`libgcc2.c' came from, and `make-gcc.com' will automatically do
all of this for you.
To install the library, use the following commands:
$ library gnu_cc:[000000]gcclib/delete=(new,eprintf)
$ library libgcc2/extract=*/output=libgcc2.obj
$ library gnu_cc:[000000]gcclib libgcc2.obj
The first command simply removes old modules that will be replaced
with modules from libgcc2. If the VMS librarian complains about
those modules not being present, simply ignore the message and
continue on with the next command.
Whenever you update the compiler on your system, you should also
update the library with the above procedure.