install.texi

早期freebsd实现

Motorola m88k running DG/UX.  To build native or cross compilers on
DG/UX, you must first change to the 88open BCS software development
environment.  This is done by issuing this command:

@example
eval `sde-target m88kbcs`
@end example

@item mips-mips-bsd
MIPS machines running the MIPS operating system in BSD mode.  It's
possible that some old versions of the system lack the functions
@code{memcpy}, @code{memcmp}, and @code{memset}.  If your system lacks
these, you must remove or undo the definition of
@code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.

@item mips-sony-sysv
Sony MIPS NEWS.  This works in NEWSOS 5.0.1, but not in 5.0.2 (which
uses ELF instead of COFF).  Support for 5.0.2 will probably be provided
soon by volunteers.

@item ns32k-encore
Encore ns32000 system.  Encore systems are supported only under BSD.

@item ns32k-*-genix
National Semiconductor ns32000 system.  Genix has bugs in @code{alloca}
and @code{malloc}; you must get the compiled versions of these from GNU
Emacs.

@item ns32k-sequent
Go to the Berkeley universe before compiling.  In addition, you probably
need to create a file named @file{string.h} containing just one line:
@samp{#include <strings.h>}.

@item ns32k-utek
UTEK ns32000 system (``merlin'').  The C compiler that comes with this
system cannot compile GNU CC; contact @samp{tektronix!reed!mason} to get
binaries of GNU CC for bootstrapping.

@item romp-*-aos
@itemx romp-*-mach
The only operating systems supported for the IBM RT PC are AOS and
MACH.  GNU CC does not support AIX running on the RT.  We recommend you
compile GNU CC with an earlier version of itself; if you compile GNU CC
with @code{hc}, the Metaware compiler, it will work, but you will get
mismatches between the stage 2 and stage 3 compilers in various files.
These errors are minor differences in some floating-point constants and
can be safely ignored; the stage 3 compiler is correct.

@item rs6000-*-aix
@strong{Read the file @file{README.RS6000} for information on how to get
a fix for a problem in the IBM assembler that prevents use of GNU CC.}
You must either obtain the new assembler or avoid using the @samp{-g}
switch.  Note that @file{Makefile.in} uses @samp{-g} by default when
compiling @file{libgcc2.c}.

@item vax-dec-ultrix
Don't try compiling with Vax C (@code{vcc}).  It produces incorrect code
in some cases (for example, when @code{alloca} is used).

Meanwhile, compiling @file{cp-parse.c} with pcc does not work because of
an internal table size limitation in that compiler.  To avoid this
problem, compile just the GNU C compiler first, and use it to recompile 
building all the languages that you want to run.
@end table

Here we spell out what files will be set up by @code{configure}.  Normally
you need not be concerned with these files.

@itemize @bullet
@item
@ifset INTERNALS
A symbolic link named @file{config.h} is made to the top-level config
file for the machine you will run the compiler on (@pxref{Config}).
This file is responsible for defining information about the host
machine.  It includes @file{tm.h}.
@end ifset
@ifclear INTERNALS
A symbolic link named @file{config.h} is made to the top-level config
file for the machine you plan to run the compiler on (@pxref{Config,,The
Configuration File, gcc.info, Using and Porting GCC}).  This file is
responsible for defining information about the host machine.  It
includes @file{tm.h}.
@end ifclear

The top-level config file is located in the subdirectory @file{config}.
Its name is always @file{xm-@var{something}.h}; usually
@file{xm-@var{machine}.h}, but there are some exceptions.

If your system does not support symbolic links, you might want to
set up @file{config.h} to contain a @samp{#include} command which
refers to the appropriate file.

@item
A symbolic link named @file{tconfig.h} is made to the top-level config
file for your target machine.  This is used for compiling certain
programs to run on that machine.

@item
A symbolic link named @file{tm.h} is made to the machine-description
macro file for your target machine.  It should be in the subdirectory
@file{config} and its name is often @file{@var{machine}.h}.

@item
A symbolic link named @file{md} will be made to the machine description
pattern file.  It should be in the @file{config} subdirectory and its
name should be @file{@var{machine}.md}; but @var{machine} is often not
the same as the name used in the @file{tm.h} file because the
@file{md} files are more general.

@item
A symbolic link named @file{aux-output.c} will be made to the output
subroutine file for your machine.  It should be in the @file{config}
subdirectory and its name should be @file{@var{machine}.c}.

@item
The command file @file{configure} also constructs @file{Makefile} by
adding some text to the template file @file{Makefile.in}.  The
additional text comes from files in the @file{config} directory, named
@file{t-@var{target}} and @file{h-@var{host}}.  If these files do not
exist, it means nothing needs to be added for a given target or host.
@end itemize

@cindex Bison parser generator
@cindex parser generator, Bison
@item
Make sure the Bison parser generator is installed.  (This is
unnecessary if the Bison output files @file{c-parse.c} and
@file{cexp.c} are more recent than @file{c-parse.y} and @file{cexp.y}
and you do not plan to change the @samp{.y} files.)

Bison versions older than Sept 8, 1988 will produce incorrect output
for @file{c-parse.c}.

@item
Build the compiler.  Just type @samp{make LANGUAGES=c} in the compiler
directory.

@samp{LANGUAGES=c} specifies that only the C compiler should be
compiled.  The makefile normally builds compilers for all the supported
languages; currently, C, C++ and Objective C.  However, C is the only
language that is sure to work when you build with other non-GNU C
compilers.  In addition, building anything but C at this stage is a
waste of time.

In general, you can specify the languages to build by typing the
argument @samp{LANGUAGES="@var{list}"}, where @var{list} is one or more
words from the list @samp{c}, @samp{c++}, and @samp{objective-c}.

Ignore any warnings you may see about ``statement not reached'' in
@file{insn-emit.c}; they are normal.  Any other compilation errors may
represent bugs in the port to your machine or operating system, and
@ifclear INSTALLONLY
should be investigated and reported (@pxref{Bugs}).
@end ifclear
@ifset INSTALLONLY
should be investigated and reported.
@end ifset

Some commercial compilers fail to compile GNU CC because they have bugs
or limitations.  For example, the Microsoft compiler is said to run out
of macro space.  Some Ultrix compilers run out of expression space; then
you need to break up the statement where the problem happens.

If you are building with a previous GNU C compiler, do not
use @samp{CC=gcc} on the make command or by editing the Makefile.
Instead, use a full pathname to specify the compiler, such as
@samp{CC=/usr/local/bin/gcc}.  This is because make might execute
the @file{gcc} in the current directory before all of the
compiler components have been built.

@item
If you are using COFF-encapsulation, you must convert @file{libgcc.a} to
a GNU-format library at this point.  See the file @file{README.ENCAP}
in the directory containing the GNU binary file utilities, for
directions.

@item
If you are building a cross-compiler, stop here.  @xref{Cross-Compiler}.

@cindex stage1
@item
Move the first-stage object files and executables into a subdirectory
with this command:

@example
make stage1
@end example

The files are moved into a subdirectory named @file{stage1}.
Once installation is complete, you may wish to delete these files
with @code{rm -r stage1}.

@item
Recompile the compiler with itself, with this command:

@example
make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O"
@end example

This is called making the stage 2 compiler.

The command shown above builds compilers for all the supported
languages.  If you don't want them all, you can specify the languages to
build by typing the argument @samp{LANGUAGES="@var{list}"}.  @var{list}
should contain one or more words from the list @samp{c}, @samp{c++},
@samp{objective-c}, and @samp{proto}.  Separate the words with spaces.
@samp{proto} stands for the programs @code{protoize} and
@code{unprotoize}; they are not a separate language, but you use
@code{LANGUAGES} to enable or disable their installation.

If you are going to build the stage 3 compiler, then you might want to
build only the C language in stage 2.

Once you have built the stage 2 compiler, if you are short of disk
space, you can delete the subdirectory @file{stage1}.

On a 68000 or 68020 system lacking floating point hardware,
unless you have selected a @file{tm.h} file that expects by default
that there is no such hardware, do this instead:

@example
make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O -msoft-float"
@end example

@item
If you wish to test the compiler by compiling it with itself one more
time, do this:

@example
make stage2
make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O" 
@end example

@noindent
This is called making the stage 3 compiler.  Aside from the @samp{-B}
option, the compiler options should be the same as when you made the
stage 2 compiler.  But the @code{LANGUAGES} option need not be the
same.  The command shown above builds compilers for all the supported
languages; if you don't want them all, you can specify the languages to
build by typing the argument @samp{LANGUAGES="@var{list}"}, as described
above.

Then compare the latest object files with the stage 2 object
files---they ought to be identical, unless they contain time stamps.
You can compare the files, disregarding the time stamps if any, like
this:

@example
make compare
@end example

This will mention any object files that differ between stage 2 and stage
3.  Any difference, no matter how innocuous, indicates that the stage 2
compiler has compiled GNU CC incorrectly, and is therefore a potentially
@ifclear INSTALLONLY
serious bug which you should investigate and report (@pxref{Bugs}).
@end ifclear
@ifset INSTALLONLY
serious bug which you should investigate and report.
@end ifset

If your system does not put time stamps in the object files, then this
is a faster way to compare them (using the Bourne shell):

@example
for file in *.o; do
cmp $file stage2/$file
done
@end example

If you have built the compiler with the @samp{-mno-mips-tfile} option on
MIPS machines, you will not be able to compare the files.

@item
Install the compiler driver, the compiler's passes and run-time support.
You can use the following command:

@example
make install CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O" LANGUAGES="@var{list}"
@end example

@noindent
(Use the same value for @code{CC}, @code{CFLAGS} and @code{LANGUAGES}
that you used when compiling the files that are being installed.  One
reason this is necessary is that some versions of Make have bugs and
recompile files gratuitously when you do this step.  If you use the same
variable values, those files will be recompiled properly.

This copies the files @file{cc1}, @file{cpp} and @file{libgcc.a} to files
@file{cc1}, @file{cpp} and @file{libgcc.a} in directory
@file{/usr/local/lib/gcc-lib/@var{target}/@var{version}}, which is where the
compiler driver program looks for them.  Here @var{target} is the target
machine type specified when you ran @file{configure}, and @var{version}
is the version number of GNU CC.  This naming scheme permits various
versions and/or cross-compilers to coexist.

It also copies the driver program @file{gcc} into the directory
@file{/usr/local/bin}, so that it appears in typical execution search
paths.@refill

On some systems, this command will cause recompilation of some files.
This is usually due to bugs in @code{make}.  You should either ignore
this problem, or use GNU Make.

@cindex @code{alloca} and SunOs
@strong{Warning: there is a bug in @code{alloca} in the Sun library.  To
avoid this bug, be sure to install the executables of GNU CC that were
compiled by GNU CC.  (That is, the executables from stage 2 or 3, not
stage 1.)  They use @code{alloca} as a built-in function and never the
one in the library.}

(It is usually better to install GNU CC executables from stage 2 or 3,
since they usually run faster than the ones compiled with some other
compiler.)

@item
Install the Objective C library (if you have built the Objective C
compiler).  Here is the command to do this:

@example
make install-libobjc CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O"
@end example

@item
Correct errors in the header files on your machine.

Various system header files often contain constructs which are
erroneous, incompatible with ANSI C or otherwise unsuitable, and they
will not work when you compile programs with GNU CC.

The most common erroneous construct is found in @file{ioctl.h}, where a
macro expects argument values to be substituted for argument names
inside of character constants---something not done in ANSI C.  This
particular problem can be prevented by using @samp{-traditional}.  Other
problems are not so easy to work around.

GNU CC comes with shell scripts to fix known header file problems.  They
install corrected copies of various header files in a special directory
where only GNU CC will normally look for them.  The scripts adapt to
various systems by searching all the system header files for the problem
cases that we know about.

Use the following command to do this: