X-Git-Url: http://git.sourceforge.jp/view?p=pf3gnuchains%2Fgcc-fork.git;a=blobdiff_plain;f=gcc%2Fdoc%2Finstall.texi;h=47a7462116e5d05153a21a430160d61667fbb12e;hp=fcae3d0e064fb8f022ab5bb557b4cbbf1874a07a;hb=81c8673cd5415fa78cb368369ea3a76e967e2472;hpb=805d655461fb1755b1edcae07dce1b688696bf64 diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index fcae3d0e064..47a7462116e 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -43,7 +43,7 @@ @end ifset @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. +@c 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com @c Include everything if we're not making html @@ -64,7 +64,7 @@ @c Part 2 Summary Description and Copyright @copying Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. +1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. @sp 1 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or @@ -261,7 +261,7 @@ environment to your ``good'' shell prior to running @command{configure}/@command{make}. @command{zsh} is not a fully compliant POSIX shell and will not -work when configuring GCC. +work when configuring GCC@. @item GNU binutils @@ -277,7 +277,7 @@ obtained via FTP mirror sites. @item GNU make version 3.79.1 (or later) -You must have GNU make installed to build GCC. +You must have GNU make installed to build GCC@. @item GNU tar version 1.12 (or later) @@ -287,7 +287,7 @@ systems' @command{tar} programs will also work, only try GNU @item GNU Multiple Precision Library (GMP) version 4.0 (or later) -Necessary to build the Fortran frontend. If you don't have it +Necessary to build the Fortran frontend. If you don't have it installed in your library search path, you will have to configure with the @option{--with-gmp} or @option{--with-gmp-dir} configure option. @@ -313,7 +313,7 @@ to regenerate @file{configure} and @file{config.in} files. Most directories require autoconf 2.59 (exactly), but the toplevel still requires autoconf 2.13 (exactly). -@item automake versions 1.8.5 and 1.9.1 +@item automake versions 1.9.3 Necessary when modifying a @file{Makefile.am} file to regenerate its associated @file{Makefile.in}. @@ -323,10 +323,10 @@ file. Specifically this applies to the @file{gcc}, @file{intl}, @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well as any of their subdirectories. -The Java directory @file{libjava} and the @file{libstdc++-v3} directory -require automake 1.9.1. Every other directory should work with either -automake 1.8.5 and automake 1.9.1, but most of them have been tested only -with automake 1.8.5 so far. +For directories that use automake, GCC requires the latest release in +the 1.9.x series, which is currently 1.9.3. When regenerating a directory +to a newer version, please update all the directories using an older 1.9.x +to the latest released version. @item gettext version 0.12 (or later) @@ -391,7 +391,7 @@ Necessary for running @command{texi2dvi}, used when running @itemx ssh (any version) Necessary to access the CVS repository. Public releases and weekly -snapshots of the development sources are also available via FTP. +snapshots of the development sources are also available via FTP@. @item perl version 5.6.1 (or later) @@ -635,22 +635,22 @@ the installation directory for G++ header files. The default is @item --program-prefix=@var{prefix} GCC supports some transformations of the names of its programs when -installing them. This option prepends @var{prefix} to the names of -programs to install in @var{bindir} (see above). For example, specifying +installing them. This option prepends @var{prefix} to the names of +programs to install in @var{bindir} (see above). For example, specifying @option{--program-prefix=foo-} would result in @samp{gcc} being installed as @file{/usr/local/bin/foo-gcc}. @item --program-suffix=@var{suffix} Appends @var{suffix} to the names of programs to install in @var{bindir} -(see above). For example, specifying @option{--program-suffix=-3.1} +(see above). For example, specifying @option{--program-suffix=-3.1} would result in @samp{gcc} being installed as @file{/usr/local/bin/gcc-3.1}. @item --program-transform-name=@var{pattern} Applies the @samp{sed} script @var{pattern} to be applied to the names -of programs to install in @var{bindir} (see above). @var{pattern} has to +of programs to install in @var{bindir} (see above). @var{pattern} has to consist of one or more basic @samp{sed} editing commands, separated by -semicolons. For example, if you want the @samp{gcc} program name to be +semicolons. For example, if you want the @samp{gcc} program name to be transformed to the installed program @file{/usr/local/bin/myowngcc} and the @samp{g++} program name to be transformed to @file{/usr/local/bin/gspecial++} without changing other program names, @@ -659,7 +659,7 @@ you could use the pattern to achieve this effect. All three options can be combined and used together, resulting in more -complex conversion patterns. As a basic rule, @var{prefix} (and +complex conversion patterns. As a basic rule, @var{prefix} (and @var{suffix}) are prepended (appended) before further transformations can happen with a special transformation script @var{pattern}. @@ -669,8 +669,8 @@ transformation is explicitly asked for by one of these options. For native builds, some of the installed programs are also installed with the target alias in front of their name, as in -@samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen -before the target alias is prepended to the name - so, specifying +@samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen +before the target alias is prepended to the name---so, specifying @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the resulting binary would be installed as @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}. @@ -702,7 +702,7 @@ programs---perhaps many others. (GCC installs its own header files in another directory which is based on the @option{--prefix} value.) Both the local-prefix include directory and the GCC-prefix include -directory are part of GCC's "system include" directories. Although these +directory are part of GCC's ``system include'' directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The local-prefix include directory is searched before the GCC-prefix @@ -809,7 +809,7 @@ directory, where @var{libexec} defaults to @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to @var{prefix} which defaults to @file{/usr/local} unless overridden by the @option{--prefix=@var{pathname}} switch described -above. @var{target} is the target system triple, such as +above. @var{target} is the target system triple, such as @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC version, such as 3.0. @item @@ -915,7 +915,7 @@ AIX thread support. DCE thread support. @item gnat Ada tasking support. For non-Ada programs, this setting is equivalent -to @samp{single}. When used in conjunction with the Ada run time, it +to @samp{single}. When used in conjunction with the Ada run time, it causes GCC to use the same thread primitives as Ada uses. This option is necessary when using both Ada and the back end exception handling, which is the default for most Ada targets. @@ -926,7 +926,9 @@ missing and thus this setting will cause a known bootstrap failure.) @item no This is an alias for @samp{single}. @item posix -Generic POSIX thread support. +Generic POSIX/Unix98 thread support. +@item posix95 +Generic POSIX/Unix95 thread support. @item rtems RTEMS thread support. @item single @@ -971,18 +973,12 @@ systems that support conditional traps). Division by zero checks use the break instruction. @end table -@item --enable-altivec -Specify that the target supports AltiVec vector enhancements. This -option will adjust the ABI for AltiVec enhancements, as well as generate -AltiVec code when appropriate. This option is only available for -PowerPC systems. - @item --enable-__cxa_atexit Define if you want to use __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of -destructors, but requires __cxa_atexit in libc. This option is currently -only available on systems with GNU libc. When enabled, this will cause +destructors, but requires __cxa_atexit in libc. This option is currently +only available on systems with GNU libc. When enabled, this will cause @option{-fuse-cxa-exit} to be passed by default. @item --enable-target-optspace @@ -1036,7 +1032,7 @@ addition, @samp{libstdc++}'s include files will be installed into @file{@var{libdir}} unless you overruled it by using @option{--with-gxx-include-dir=@var{dirname}}. Using this option is particularly useful if you intend to use several versions of GCC in -parallel. This is currently supported by @samp{libgfortran}, +parallel. This is currently supported by @samp{libgfortran}, @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}. @@ -1078,7 +1074,7 @@ to look up installations paths in the registry using the following key: @end smallexample @var{key} defaults to GCC version number, and can be overridden by the -@option{--enable-win32-registry=@var{key}} option. Vendors and distributors +@option{--enable-win32-registry=@var{key}} option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled @@ -1112,30 +1108,31 @@ with GCC@. This is on by default when building from CVS or snapshots, but off for releases. More control over the checks may be had by specifying @var{list}; the categories of checks available are @samp{release}, @samp{assert}, @samp{misc}, @samp{tree}, @samp{gc}, -@samp{rtl}, @samp{rtlflag}, @samp{fold}, @samp{gcac} and +@samp{rtl}, @samp{rtlflag}, @samp{runtime}, @samp{fold}, @samp{gcac} and @samp{valgrind}. The @samp{release} category enables only those checks -suitable for release builds, currently this is just @samp{assert}. The -check @samp{valgrind} requires the external @command{valgrind} -simulator, available from @uref{http://valgrind.kde.org/}. The checks -@samp{rtl}, @samp{gcac} and @samp{valgrind} are very expensive. The -default when @var{list} is not specified is -@samp{assert,misc,tree,gc,rtlflag}. That is also the default for -development builds, when @samp{--enable-checking} is not specified. For -release builds the default, when @samp{--enable-checking} is not given, -is @samp{release}. To disable all checking, @samp{--disable-checking} -must be explicitly requested. Disabling assertions will make the -compiler slightly faster but increase the risk of undetected internal -errors causing wrong code to be generated. +suitable for release builds, currently this is @samp{assert} and +@samp{runtime}. The check @samp{valgrind} requires the external +@command{valgrind} simulator, available from +@uref{http://valgrind.kde.org/}. The checks @samp{rtl}, @samp{gcac} and +@samp{valgrind} are very expensive. The default when @var{list} is not +specified is @samp{assert,misc,tree,gc,rtlflag,runtime}. That is also +the default for development builds, when @samp{--enable-checking} is not +specified. For release builds the default, when +@samp{--enable-checking} is not given, is @samp{release}. To disable +all checking, @samp{--disable-checking} must be explicitly requested. +Disabling assertions will make the compiler and runtime slightly faster +but increase the risk of undetected internal errors causing wrong code +to be generated. @item --enable-coverage @itemx --enable-coverage=@var{level} With this option, the compiler is built to collect self coverage -information, every time it is run. This is for internal development -purposes, and only works when the compiler is being built with gcc. The +information, every time it is run. This is for internal development +purposes, and only works when the compiler is being built with gcc. The @var{level} argument controls whether the compiler is built optimized or -not, values are @samp{opt} and @samp{noopt}. For coverage analysis you +not, values are @samp{opt} and @samp{noopt}. For coverage analysis you want to disable optimization, for performance analysis you want to -enable optimization. When coverage is enabled, the default level is +enable optimization. When coverage is enabled, the default level is without optimization. @item --enable-gather-detailed-mem-stats @@ -1143,6 +1140,12 @@ When this option is specified more detailed information on memory allocation is gathered. This information is printed when using @option{-fmem-report}. +@item --with-gc +@itemx --with-gc=@var{choice} +With this option you can specify the garbage collector implementation +used during the compilation process. @var{choice} can be one of +@samp{page} and @samp{zone}, where @samp{page} is the default. + @item --enable-nls @itemx --disable-nls The @option{--enable-nls} option enables Native Language Support (NLS), @@ -1202,7 +1205,7 @@ directory. @emph{This option with the @var{dir} argument is required} when building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does pre-exist, the @var{dir} argument may be omitted. @command{fixincludes} -will be run on these files to make them compatible with GCC. +will be run on these files to make them compatible with GCC@. @item --without-headers Tells GCC not use any target headers from a libc when building a cross @@ -1235,7 +1238,7 @@ The following options apply to the build of the Fortran front end. @itemx --with-mpfr=@var{pathname} @itemx --with-gmp-dir=@var{pathname} @itemx --with-mpfr-dir=@var{pathname} -If you don't have GMP (the GNU Multiple Precision library) and the MPFR +If you don't have GMP (the GNU Multiple Precision library) and the MPFR Libraries installed in a standard location and you want to build the Fortran front-end, you can explicitly specify the directory where they are installed (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where @@ -1272,19 +1275,19 @@ The following options apply to building @samp{libgcj}. Don't set system properties from @env{GCJ_PROPERTIES}. @item --enable-hash-synchronization -Use a global hash table for monitor locks. Ordinarily, +Use a global hash table for monitor locks. Ordinarily, @samp{libgcj}'s @samp{configure} script automatically makes -the correct choice for this option for your platform. Only use +the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. @item --enable-interpreter -Enable the Java interpreter. The interpreter is automatically -enabled by default on all platforms that support it. This option +Enable the Java interpreter. The interpreter is automatically +enabled by default on all platforms that support it. This option is really only useful if you want to disable the interpreter (using @option{--disable-interpreter}). @item --disable-java-net -Disable java.net. This disables the native part of java.net only, +Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. @item --disable-jvmpi @@ -1294,7 +1297,7 @@ Disable JVMPI support. Enable runtime eCos target support. @item --without-libffi -Don't use @samp{libffi}. This will disable the interpreter and JNI +Don't use @samp{libffi}. This will disable the interpreter and JNI support as well, as these require @samp{libffi} to work. @item --enable-libgcj-debug @@ -1303,8 +1306,8 @@ Enable runtime debugging code. @item --enable-libgcj-multifile If specified, causes all @file{.java} source files to be compiled into @file{.class} files in one invocation of -@samp{gcj}. This can speed up build time, but is more -resource-intensive. If this option is unspecified or +@samp{gcj}. This can speed up build time, but is more +resource-intensive. If this option is unspecified or disabled, @samp{gcj} is invoked once for each @file{.java} file to compile into a @file{.class} file. @@ -1312,8 +1315,8 @@ file to compile into a @file{.class} file. Search for libiconv in @file{DIR/include} and @file{DIR/lib}. @item --enable-sjlj-exceptions -Force use of @code{builtin_setjmp} for exceptions. @samp{configure} -ordinarily picks the correct value based on the platform. Only use +Force use of @code{builtin_setjmp} for exceptions. @samp{configure} +ordinarily picks the correct value based on the platform. Only use this option if you are sure you need a different setting. @item --with-system-zlib @@ -1321,25 +1324,25 @@ Use installed @samp{zlib} rather than that included with GCC@. @item --with-win32-nlsapi=ansi, unicows or unicode Indicates how MinGW @samp{libgcj} translates between UNICODE -characters and the Win32 API. +characters and the Win32 API@. @table @code @item ansi Use the single-byte @code{char} and the Win32 A functions natively, -translating to and from UNICODE when using these functions. If +translating to and from UNICODE when using these functions. If unspecified, this is the default. @item unicows -Use the @code{WCHAR} and Win32 W functions natively. Adds +Use the @code{WCHAR} and Win32 W functions natively. Adds @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}. @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines -running built executables. @file{libunicows.a}, an open-source +running built executables. @file{libunicows.a}, an open-source import library around Microsoft's @code{unicows.dll}, is obtained from @uref{http://libunicows.sourceforge.net/}, which also gives details on getting @file{unicows.dll} from Microsoft. @item unicode -Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} -add @code{-lunicows} to @file{libgcj.spec}. The built executables will +Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not} +add @code{-lunicows} to @file{libgcj.spec}. The built executables will only run on Microsoft Windows NT and above. @end table @end table @@ -1352,16 +1355,16 @@ Use the X Window System. @item --enable-java-awt=PEER(S) Specifies the AWT peer library or libraries to build alongside -@samp{libgcj}. If this option is unspecified or disabled, AWT -will be non-functional. Current valid values are @option{gtk} and -@option{xlib}. Multiple libraries should be separated by a +@samp{libgcj}. If this option is unspecified or disabled, AWT +will be non-functional. Current valid values are @option{gtk} and +@option{xlib}. Multiple libraries should be separated by a comma (i.e.@: @option{--enable-java-awt=gtk,xlib}). @item --enable-gtk-cairo -Build the cairo Graphics2D implementation on GTK. +Build the cairo Graphics2D implementation on GTK@. @item --enable-java-gc=TYPE -Choose garbage collector. Defaults to @option{boehm} if unspecified. +Choose garbage collector. Defaults to @option{boehm} if unspecified. @item --disable-gtktest Do not try to compile and run a test GTK+ program. @@ -1501,7 +1504,7 @@ bootstrap4} to increase the number of stages of bootstrap. Note that using non-standard @code{CFLAGS} can cause bootstrap to fail in @file{libiberty}, if these trigger a warning with the new compiler. For example using @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will -cause bootstrap failure as @code{-mcpu=} is deprecated in 3.4.0 and above. +cause bootstrap failure as @option{-mcpu=} is deprecated in 3.4.0 and above. If you used the flag @option{--enable-languages=@dots{}} to restrict @@ -1672,7 +1675,7 @@ at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out -problems before you install and start using your new GCC. +problems before you install and start using your new GCC@. First, you must have @uref{download.html,,downloaded the testsuites}. These are part of the full distribution, but if you downloaded the @@ -1948,7 +1951,7 @@ quickly review the build status page for your release, available from If your system is not listed for the version of GCC that you built, send a note to @email{gcc@@gcc.gnu.org} indicating -that you successfully built and installed GCC. +that you successfully built and installed GCC@. Include the following information: @itemize @bullet @@ -2016,6 +2019,10 @@ printing with programs such as @command{dvips}. You can also Free Software Foundation}, though such manuals may not be for the most recent version of GCC@. +If you would like to generate online HTML documentation, do @samp{cd +@var{objdir}; make html} and HTML will be generated for the manuals in +@file{@var{objdir}/HTML}. + @html
@@ -2108,7 +2115,7 @@ IRIX 6.5, Digital UNIX 4.0D and 5.1, GNU/Linux (i386), HP-UX 10.20, 11.00, and 11.11, and -Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9, +Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9. @item @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a @@ -2567,7 +2574,7 @@ and includes all the necessary compilation tools and libraries. @heading @anchor{*-*-freebsd*}*-*-freebsd* The version of binutils installed in @file{/usr/bin} probably works with -this release of GCC. However, on FreeBSD 4, bootstrapping against the +this release of GCC@. However, on FreeBSD 4, bootstrapping against the latest FSF binutils is known to improve overall testsuite results; and, on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava. @@ -2587,7 +2594,7 @@ FreeBSD/alpha since its inception. You may use @option{-gstabs} instead of @option{-g}, if you really want the old debugging format. There are no known issues with mixing object files and libraries with different debugging formats. Otherwise, this release of GCC should now match more -of the configuration used in the stock FreeBSD configuration of GCC. In +of the configuration used in the stock FreeBSD configuration of GCC@. In particular, @option{--enable-threads} is now configured by default. However, as a general user, do not attempt to replace the system compiler with this release. Known to bootstrap and check with good @@ -2633,9 +2640,9 @@ you may encounter a variety of problems when using the HP assembler. Specifically, @option{-g} does not work on HP-UX (since that system uses a peculiar debugging format which GCC does not know about), unless -you use GAS and GDB. It may be helpful to configure GCC with the +you use GAS and GDB@. It may be helpful to configure GCC with the @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and -@option{--with-as=@dots{}} options to ensure that GCC can find GAS. +@option{--with-as=@dots{}} options to ensure that GCC can find GAS@. If you wish to use the pa-risc 2.0 architecture support with a 32-bit runtime, you must use either the HP assembler, or gas/binutils 2.11 @@ -2711,8 +2718,8 @@ GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for information about obtaining -precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained -to build the Ada language as it can't be bootstrapped using C. Ada is +precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained +to build the Ada language as it can't be bootstrapped using C@. Ada is only available for the 32-bit PA-RISC runtime. The libffi and libjava haven't been ported to HP-UX and don't build. @@ -2731,7 +2738,7 @@ unbundled compiler, or a binary distribution of GCC@. There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC distribution can be built. The second approach is to build GCC -first using the HP tools, then build binutils, then rebuild GCC. +first using the HP tools, then build binutils, then rebuild GCC@. There have been problems with various binary distributions, so it is best not to start from a binary distribution. @@ -2751,7 +2758,7 @@ needed whenever @env{CC} is used. Specifically, options that determine the runtime architecture must be in @env{CC} to correctly select the target for the build. It is also -convenient to place many other compiler options in @env{CC}. For example, +convenient to place many other compiler options in @env{CC}. For example, @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"} can be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in @@ -2767,7 +2774,7 @@ search for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a result, it's not possible to switch linkers in the middle of a GCC build. This has been been reported to sometimes occur in unified builds of -binutils and GCC. +binutils and GCC@. GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through GCC 3.5 require binutils 2.14 or later. @@ -2882,7 +2889,7 @@ you install Support Level Supplement OSS646B or later, and Support Level Supplement OSS631C or later. If you are using release 5.0.7 of OpenServer, you must have at least the first maintenance pack installed (this includes the relevant portions of OSS646). OSS646, also known as -the "Execution Environment Update", provides updated link editors and +the ``Execution Environment Update'', provides updated link editors and assemblers, as well as updated standard C and math libraries. The C startup modules are also updated to support the System V gABI draft, and GCC relies on that behavior. OSS631 provides a collection of commonly @@ -2902,8 +2909,8 @@ use a modern version of GNU binutils. Version 2.13.2.1 was used for all testing. In general, only the @option{--with-gnu-as} option is tested. A modern bintuils (as well as a plethora of other development related GNU utilities) can be found in Support Level Supplement OSS658A, the -"GNU Development Tools" package. See the SCO web and ftp sites for details. -That package also contains the currently "officially supported" version of +``GNU Development Tools'' package. See the SCO web and ftp sites for details. +That package also contains the currently ``officially supported'' version of GCC, version 2.95.3. It is useful for bootstrapping this version. @html @@ -2966,13 +2973,13 @@ more major ABI changes are expected.