X-Git-Url: http://git.sourceforge.jp/view?p=pf3gnuchains%2Fgcc-fork.git;a=blobdiff_plain;f=gcc%2Fdoc%2Finstall.texi;h=00dd78745dac6b75f4dab05cd087c03e9c9da3ab;hp=4f7e433c614b3f1f5f3b7f360259712e6feee5ed;hb=1b7b9d609040b011f99476ceffa3a7f9f7fcfa28;hpb=7ab76cecd643d0d098fb7293340afa0e2b5f9f37 diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 4f7e433c614..00dd78745da 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -45,7 +45,8 @@ @end ifset @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. +@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, +@c 2010 Free Software Foundation, Inc. @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com @c IMPORTANT: whenever you modify this file, run `install.texi2html' to @@ -302,7 +303,7 @@ Necessary (only on some platforms) to untar the source code. Many systems' @command{tar} programs will also work, only try GNU @command{tar} if you have problems. -@item GNU Multiple Precision Library (GMP) version 4.2 (or later) +@item GNU Multiple Precision Library (GMP) version 4.3.2 (or later) Necessary to build GCC@. If you do not have it installed in your library search path, you will have to configure with the @@ -311,7 +312,7 @@ and @option{--with-gmp-include}. Alternatively, if a GMP source distribution is found in a subdirectory of your GCC sources named @file{gmp}, it will be built together with GCC@. -@item MPFR Library version 2.3.2 (or later) +@item MPFR Library version 2.4.2 (or later) Necessary to build GCC@. It can be downloaded from @uref{http://www.mpfr.org/}. The @option{--with-mpfr} configure @@ -321,6 +322,16 @@ default library search path. See also @option{--with-mpfr-lib} and distribution is found in a subdirectory of your GCC sources named @file{mpfr}, it will be built together with GCC@. +@item MPC Library version 0.8.1 (or later) + +Necessary to build GCC@. It can be downloaded from +@uref{http://www.multiprecision.org/}. The @option{--with-mpc} +configure option should be used if your MPC Library is not installed +in your default library search path. See also @option{--with-mpc-lib} +and @option{--with-mpc-include}. Alternatively, if an MPC source +distribution is found in a subdirectory of your GCC sources named +@file{mpc}, it will be built together with GCC@. + @item Parma Polyhedra Library (PPL) version 0.10 Necessary to build GCC with the Graphite loop optimizations. @@ -344,29 +355,28 @@ not installed in your default library search path. Necessary to build libgcj, the GCJ runtime. -@item MPC Library version 0.6.0 (or later) +@item libelf version 0.8.12 (or later) + +Necessary to build link-time optimization (LTO) support. It can be +downloaded from @uref{http://www.mr511.de/software/libelf-0.8.12.tar.gz}, +though it is commonly available in several systems. The versions in +IRIX 5 and 6 don't work since they lack @file{gelf.h}. The version in +recent releases of Solaris 11 does work, previous ones don't yet. -Optional when building GCC@. Having this library will enable -additional optimizations on complex numbers. It can be downloaded -from @uref{http://www.multiprecision.org/mpc/}. The -@option{--with-mpc} configure option should be used if your MPC -Library is not installed in your default library search path. See -also @option{--with-mpc-lib} and @option{--with-mpc-include}. -Alternatively, if an MPC source distribution is found in a -subdirectory of your GCC sources named @file{mpc}, it will be built -together with GCC@. +The @option{--with-libelf} configure option should be used if libelf is +not installed in your default library search patch. @end table @heading Tools/packages necessary for modifying GCC @table @asis -@item autoconf version 2.59 -@itemx GNU m4 version 1.4 (or later) +@item autoconf version 2.64 +@itemx GNU m4 version 1.4.6 (or later) Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@: to regenerate @file{configure} and @file{config.in} files. -@item automake version 1.9.6 +@item automake version 1.11.1 Necessary when modifying a @file{Makefile.am} file to regenerate its associated @file{Makefile.in}. @@ -377,8 +387,8 @@ file. Specifically this applies to the @file{gcc}, @file{intl}, as any of their subdirectories. For directories that use automake, GCC requires the latest release in -the 1.9.x series, which is currently 1.9.6. When regenerating a directory -to a newer version, please update all the directories using an older 1.9.x +the 1.11 series, which is currently 1.11.1. When regenerating a directory +to a newer version, please update all the directories using an older 1.11 to the latest released version. @item gettext version 0.14.5 (or later) @@ -571,8 +581,8 @@ We use @var{srcdir} to refer to the toplevel source directory for GCC; we use @var{objdir} to refer to the toplevel build/object directory. If you obtained the sources via SVN, @var{srcdir} must refer to the top -@file{gcc} directory, the one where the @file{MAINTAINERS} can be found, -and not its @file{gcc} subdirectory, otherwise the build will fail. +@file{gcc} directory, the one where the @file{MAINTAINERS} file can be +found, and not its @file{gcc} subdirectory, otherwise the build will fail. If either @var{srcdir} or @var{objdir} is located on an automounted NFS file system, the shell's built-in @command{pwd} command will return @@ -583,7 +593,7 @@ variable to an automounter-aware @command{pwd} command, e.g., phases. First, we @strong{highly} recommend that GCC be built into a -separate directory than the sources which does @strong{not} reside +separate directory from the sources which does @strong{not} reside within the source tree. This is how we generally build GCC; building where @var{srcdir} == @var{objdir} should still work, but doesn't get extensive testing; building where @var{objdir} is a subdirectory @@ -652,8 +662,8 @@ The default value refers to the FSF's GCC bug tracker. @itemize @bullet @item GCC has code to correctly determine the correct value for @var{target} -for nearly all native systems. Therefore, we highly recommend you not -provide a configure target when configuring a native compiler. +for nearly all native systems. Therefore, we highly recommend you do +not provide a configure target when configuring a native compiler. @item @var{target} must be specified as @option{--target=@var{target}} @@ -714,18 +724,34 @@ The default is @file{@var{exec-prefix}/libexec}. Specify the installation directory for the shared libgcc library. The default is @file{@var{libdir}}. +@item --datarootdir=@var{dirname} +Specify the root of the directory tree for read-only architecture-independent +data files referenced by GCC@. The default is @file{@var{prefix}/share}. + @item --infodir=@var{dirname} Specify the installation directory for documentation in info format. -The default is @file{@var{prefix}/info}. +The default is @file{@var{datarootdir}/info}. @item --datadir=@var{dirname} Specify the installation directory for some architecture-independent -data files referenced by GCC@. The default is @file{@var{prefix}/share}. +data files referenced by GCC@. The default is @file{@var{datarootdir}}. + +@item --docdir=@var{dirname} +Specify the installation directory for documentation files (other +than Info) for GCC@. The default is @file{@var{datarootdir}/doc}. + +@item --htmldir=@var{dirname} +Specify the installation directory for HTML documentation files. +The default is @file{@var{docdir}}. + +@item --pdfdir=@var{dirname} +Specify the installation directory for PDF documentation files. +The default is @file{@var{docdir}}. @item --mandir=@var{dirname} Specify the installation directory for manual pages. The default is -@file{@var{prefix}/man}. (Note that the manual pages are only extracts from -the full GCC manuals, which are provided in Texinfo format. The manpages +@file{@var{datarootdir}/man}. (Note that the manual pages are only extracts +from the full GCC manuals, which are provided in Texinfo format. The manpages are derived by an automatic conversion process from parts of the full manual.) @@ -1093,7 +1119,8 @@ RTEMS thread support. @item single Disable thread support, should work for all platforms. @item solaris -Sun Solaris 2 thread support. +Sun Solaris 2/Unix International thread support. Only use this if you +really need to use this legacy API instead of the default, @samp{posix}. @item vxworks VxWorks thread support. @item win32 @@ -1145,6 +1172,11 @@ of the arguments depend on the target. Specify if the compiler should default to @option{-marm} or @option{-mthumb}. This option is only supported on ARM targets. +@item --with-fpmath=sse +Specify if the compiler should default to @option{-msse2} and +@option{-mfpmath=sse}. This option is only supported on i386 and +x86-64 targets. + @item --with-divide=@var{type} Specify how the compiler should generate code for checking for division by zero. This option is only supported on the MIPS target. @@ -1170,6 +1202,14 @@ not provide them. On MIPS targets, make @option{-mno-llsc} the default when no @option{-mllsc} option is passed. +@item --with-synci +On MIPS targets, make @option{-msynci} the default when no +@option{-mno-synci} option is passed. + +@item --without-synci +On MIPS targets, make @option{-mno-synci} the default when no +@option{-msynci} option is passed. This is the default. + @item --with-mips-plt On MIPS targets, make use of copy relocations and PLTs. These features are extensions to the traditional @@ -1189,9 +1229,6 @@ Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. -@item --disable-cpp -Specify that a user visible @command{cpp} program should not be installed. - @item --with-cpp-install-dir=@var{dirname} Specify that the user visible @command{cpp} program should be installed in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. @@ -1209,8 +1246,8 @@ Build GCC using a C++ compiler rather than a C compiler. This is an experimental option which may become the default in a later release. @item --enable-maintainer-mode -The build rules that -regenerate the GCC master message catalog @file{gcc.pot} are normally +The build rules that regenerate the Autoconf and Automake output files as +well as the GCC master message catalog @file{gcc.pot} are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with @option{--enable-maintainer-mode} will enable @@ -1226,7 +1263,7 @@ this process, you can configure with @option{--disable-bootstrap}. @item --enable-bootstrap In special cases, you may want to perform a 3-stage build even if the target and host triplets are different. -This could happen when the host can run code compiled for +This is possible when the host can run code compiled for the target (e.g.@: host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do this you have to configure explicitly with @option{--enable-bootstrap}. @@ -1316,8 +1353,10 @@ powerpc-linux for powerpc64-linux, only generates 32-bit code. This option enables the 32-bit target to be a bi-arch compiler, which is useful when you want a bi-arch compiler that defaults to 32-bit, and you are building a bi-arch or multi-arch binutils in a combined tree. -Currently, this option only affects sparc-linux, powerpc-linux and -x86-linux. +On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), +defaulted to o32. +Currently, this option only affects sparc-linux, powerpc-linux, x86-linux +and mips-linux. @item --enable-secureplt This option enables @option{-msecure-plt} by default for powerpc-linux. @@ -1401,7 +1440,7 @@ increase the risk of undetected internal errors causing wrong code to be generated. @item --disable-stage1-checking -@item --enable-stage1-checking +@itemx --enable-stage1-checking @itemx --enable-stage1-checking=@var{list} If no @option{--enable-checking} option is specified the stage1 compiler will be built with @samp{yes} checking enabled, otherwise @@ -1587,17 +1626,50 @@ option), if the linker supports it. If you specify support @option{--build-id} option, a warning is issued and the @option{--enable-linker-build-id} option is ignored. The default is off. +@item --enable-gnu-unique-object +@itemx --disable-gnu-unique-object +Tells GCC to use the gnu_unique_object relocation for C++ template +static data members and inline function local statics. Enabled by +default for a native toolchain with an assembler that accepts it and +GLIBC 2.11 or above, otherwise disabled. + +@item --enable-lto +Enable support for link-time optimization (LTO). This is enabled by +default if a working libelf implementation is found (see +@option{--with-libelf}). + +@item --with-libelf=@var{pathname} +@itemx --with-libelf-include=@var{pathname} +@itemx --with-libelf-lib=@var{pathname} +If you do not have libelf installed in a standard location and you +want to enable support for link-time optimization (LTO), you can +explicitly specify the directory where libelf is installed +(@samp{--with-libelf=@var{libelfinstalldir}}). The +@option{--with-libelf=@var{libelfinstalldir}} option is shorthand for +@option{--with-libelf-include=@var{libelfinstalldir}/include} +@option{--with-libelf-lib=@var{libelfinstalldir}/lib}. + +@item --enable-gold +Enable support for using @command{gold} as the linker. If gold support is +enabled together with @option{--enable-lto}, an additional directory +@file{lto-plugin} will be built. The code in this directory is a +plugin for gold that allows the link-time optimizer to extract object +files with LTO information out of library archives. See +@option{-flto} and @option{-fwhopr} for details. @end table @subheading Cross-Compiler-Specific Options The following options only apply to building cross compilers. + @table @code @item --with-sysroot @itemx --with-sysroot=@var{dir} Tells GCC to consider @var{dir} as the root of a tree that contains a (subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be -searched in there. The specified directory is not copied into the +searched in there. More specifically, this acts as if +@option{--sysroot=@var{dir}} was added to the default options of the built +compiler. The specified directory is not copied into the install tree, unlike the options @option{--with-headers} and @option{--with-libs} that this option obsoletes. The default value, in case @option{--with-sysroot} is not given an argument, is @@ -1605,6 +1677,11 @@ in case @option{--with-sysroot} is not given an argument, is subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to the GCC binaries if the installation tree is moved. +This option affects the system root for the compiler used to build +target libraries (which runs on the build system) and the compiler newly +installed with @code{make install}; it does not affect the compiler which is +used to build GCC itself. + @item --with-build-sysroot @itemx --with-build-sysroot=@var{dir} Tells GCC to consider @var{dir} as the system root (see @@ -1637,7 +1714,7 @@ compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. @item --with-libs -@itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}'' +@itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}" Deprecated in favor of @option{--with-sysroot}. Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the @file{gcc} install @@ -1837,6 +1914,9 @@ not specified, then the Python modules are installed in $(prefix)/share/python. @item --enable-aot-compile-rpm Adds aot-compile-rpm to the list of installed scripts. +@item --enable-browser-plugin +Build the gcjwebplugin web browser plugin. + @table @code @item ansi Use the single-byte @code{char} and the Win32 A functions natively, @@ -2049,11 +2129,13 @@ the one you are building on: for example, you could build a @code{powerpc64-unknown-linux-gnu} host. In this case, pass @option{--enable-bootstrap} to the configure script. -@code{BUILD_CONFIG} can be used to bring in additional customization to -the build. It can be set to a whitespace-separated list of names. For -each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will be -included by the top-level @file{Makefile}, bringing in any settings it -contains. Some examples are: +@code{BUILD_CONFIG} can be used to bring in additional customization +to the build. It can be set to a whitespace-separated list of names. +For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will +be included by the top-level @file{Makefile}, bringing in any settings +it contains. The default @code{BUILD_CONFIG} can be set using the +configure option @option{--with-build-config=@code{NAME}...}. Some +examples of supported build configurations are: @table @asis @item @samp{bootstrap-O1} @@ -2065,8 +2147,56 @@ Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds Analogous to @code{bootstrap-O1}. @item @samp{bootstrap-debug} -Builds stage2 without debug information, and uses -@file{contrib/compare-debug} to compare object files. +Verifies that the compiler generates the same executable code, whether +or not it is asked to emit debug information. To this end, this +option builds stage2 host programs without debug information, and uses +@file{contrib/compare-debug} to compare them with the stripped stage3 +object files. If @code{BOOT_CFLAGS} is overridden so as to not enable +debug information, stage2 will have it, and stage3 won't. This option +is enabled by default when GCC bootstrapping is enabled, if +@code{strip} can turn object files compiled with and without debug +info into identical object files. In addition to better test +coverage, this option makes default bootstraps faster and leaner. + +@item @samp{bootstrap-debug-big} +Rather than comparing stripped object files, as in +@code{bootstrap-debug}, this option saves internal compiler dumps +during stage2 and stage3 and compares them as well, which helps catch +additional potential problems, but at a great cost in terms of disk +space. It can be specified in addition to @samp{bootstrap-debug}. + +@item @samp{bootstrap-debug-lean} +This option saves disk space compared with @code{bootstrap-debug-big}, +but at the expense of some recompilation. Instead of saving the dumps +of stage2 and stage3 until the final compare, it uses +@option{-fcompare-debug} to generate, compare and remove the dumps +during stage3, repeating the compilation that already took place in +stage2, whose dumps were not saved. + +@item @samp{bootstrap-debug-lib} +This option tests executable code invariance over debug information +generation on target libraries, just like @code{bootstrap-debug-lean} +tests it on host programs. It builds stage3 libraries with +@option{-fcompare-debug}, and it can be used along with any of the +@code{bootstrap-debug} options above. + +There aren't @code{-lean} or @code{-big} counterparts to this option +because most libraries are only build in stage3, so bootstrap compares +would not get significant coverage. Moreover, the few libraries built +in stage2 are used in stage3 host programs, so we wouldn't want to +compile stage2 libraries with different options for comparison purposes. + +@item @samp{bootstrap-debug-ckovw} +Arranges for error messages to be issued if the compiler built on any +stage is run without the option @option{-fcompare-debug}. This is +useful to verify the full @option{-fcompare-debug} testing coverage. It +must be used along with @code{bootstrap-debug-lean} and +@code{bootstrap-debug-lib}. + +@item @samp{bootstrap-time} +Arranges for the run time of each program started by the GCC driver, +built in any stage, to be logged to @file{time.log}, in the top level of +the build tree. @end table @@ -2076,7 +2206,7 @@ When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC@. -To build a cross compiler, we first recommend building and installing a +To build a cross compiler, we recommend first building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. @@ -2156,7 +2286,7 @@ compilation options. Check your target's definition of @section Building in parallel -GNU Make 3.79 and above, which is necessary to build GCC, support +GNU Make 3.80 and above, which is necessary to build GCC, support building in parallel. To activate this, you can use @samp{make -j 2} instead of @samp{make}. You can also specify a bigger number, and in most cases using a value greater than the number of processors in @@ -2570,7 +2700,7 @@ incomplete or out of date. Send a note to @email{gcc@@gcc.gnu.org} detailing how the information should be changed. If you find a bug, please report it following the -@uref{../bugs.html,,bug reporting guidelines}. +@uref{../bugs/,,bug reporting guidelines}. If you want to print the GCC manuals, do @samp{cd @var{objdir}; make dvi}. You will need to have @command{texi2dvi} (version at least 4.7) @@ -2580,7 +2710,7 @@ printing with programs such as @command{dvips}. Alternately, by using @samp{make pdf} in place of @samp{make dvi}, you can create documentation in the form of @file{.pdf} files; this requires @command{texi2pdf}, which is included with Texinfo version 4.8 and later. You can also -@uref{http://www.gnu.org/order/order.html,,buy printed manuals from the +@uref{http://shop.fsf.org/,,buy printed manuals from the Free Software Foundation}, though such manuals may not be for the most recent version of GCC@. @@ -2629,7 +2759,7 @@ AIX: @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p}; @item -@uref{http://www.perzl.org/aix,,AIX 5L and 6 Open Source Packages}. +@uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}. @end itemize @item @@ -2691,15 +2821,6 @@ The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has links to GNU Fortran binaries for several platforms. @end itemize -In addition to those specific offerings, you can get a binary -distribution CD-ROM from the -@uref{http://www.gnu.org/order/order.html,,Free Software Foundation}. -It contains binaries for a number of platforms, and -includes not only GCC, but other stuff as well. The current CD does -not contain the latest version of GCC, but it should allow -bootstrapping the compiler. An updated version of that disk is in the -works. - @html
@@ -2773,6 +2894,10 @@ information are. @item @uref{#iq2000-x-elf,,iq2000-*-elf} @item +@uref{#lm32-x-elf,,lm32-*-elf} +@item +@uref{#lm32-x-uclinux,,lm32-*-uclinux} +@item @uref{#m32c-x-elf,,m32c-*-elf} @item @uref{#m32r-x-elf,,m32r-*-elf} @@ -2785,6 +2910,8 @@ information are. @item @uref{#m68k-uclinux,,m68k-uclinux} @item +@uref{#mep-x-elf,,mep-*-elf} +@item @uref{#mips-x-x,,mips-*-*} @item @uref{#mips-sgi-irix5,,mips-sgi-irix5} @@ -2823,6 +2950,8 @@ information are. @item @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7} @item +@uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10} +@item @uref{#sparc-x-linux,,sparc-*-linux*} @item @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*} @@ -2878,61 +3007,38 @@ shared libraries. @end html @heading @anchor{alpha-dec-osf}alpha*-dec-osf* Systems using processors that implement the DEC Alpha architecture and -are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq +are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer supported. (These are the versions which identify themselves as DEC -OSF/1.) +OSF/1.) As of GCC 4.5, support for Tru64 UNIX V4.0 and V5.0 has been +obsoleted, but can still be enabled by configuring with +@option{--enable-obsolete}. Support will be removed in GCC 4.6. -In Digital Unix V4.0, virtual memory exhausted bootstrap failures -may be fixed by configuring with @option{--with-gc=simple}, -reconfiguring Kernel Virtual Memory and Swap parameters +On Tru64 UNIX, virtual memory exhausted bootstrap failures +may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters per the @command{/usr/sbin/sys_check} Tuning Suggestions, or applying the patch in -@uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. - -In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not -currently (2001-06-13) work with @command{mips-tfile}. As a workaround, -we need to use the old assembler, invoked via the barely documented -@option{-oldas} option. To bootstrap GCC, you either need to use the -Compaq C Compiler: - -@smallexample - % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}] -@end smallexample - -or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: - -@smallexample - % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}] -@end smallexample +@uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. Depending on +the OS version used, you need a data segment size between 512 MB and +1 GB, so simply use @command{ulimit -Sd unlimited}. -As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld} +As of GNU binutils 2.20.1, neither GNU @command{as} nor GNU @command{ld} are supported on Tru64 UNIX, so you must not configure GCC with @option{--with-gnu-as} or @option{--with-gnu-ld}. GCC writes a @samp{.verstamp} directive to the assembler output file unless it is built as a cross-compiler. It gets the version to use from the system header file @file{/usr/include/stamp.h}. If you install a -new version of DEC Unix, you should rebuild GCC to pick up the new version +new version of Tru64 UNIX, you should rebuild GCC to pick up the new version stamp. -@samp{make compare} may fail on old versions of DEC Unix unless you add -@option{-save-temps} to @code{BOOT_CFLAGS}. On these systems, the name -of the assembler input file is stored in the object file, and that makes -comparison fail if it differs between the @code{stage1} and -@code{stage2} compilations. The option @option{-save-temps} forces a -fixed name to be used for the assembler input file, instead of a -randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} -unless the comparisons fail without that option. If you add -@option{-save-temps}, you will have to manually delete the @samp{.i} and -@samp{.s} files after each series of compilations. - GCC now supports both the native (ECOFF) debugging format used by DBX and GDB and an encapsulated STABS format for use only with GDB@. See the discussion of the @option{--with-stabs} option of @file{configure} above for more information on these formats and how to select them. +@c FIXME: does this work at all? If so, perhaps make default. There is a bug in DEC's assembler that produces incorrect line numbers for ECOFF format when the @samp{.align} directive is used. To work @@ -2946,6 +3052,8 @@ To avoid this behavior, specify @option{-gstabs+} and use GDB instead of DBX@. DEC is now aware of this problem with the assembler and hopes to provide a fix shortly. +@c FIXME: still applicable? + @html