diff options
30 files changed, 1433 insertions, 608 deletions
diff --git a/gnu/egcs/install/BINARIES b/gnu/egcs/install/BINARIES new file mode 100644 index 00000000000..3c74daffc0a --- /dev/null +++ b/gnu/egcs/install/BINARIES @@ -0,0 +1,46 @@ + + Installing GCC: Binaries + + We are often asked about pre-compiled versions of GCC. While we cannot + provide these for all platforms, below you'll find links to binaries + for various platforms where creating them by yourself is not easy due + to various reasons. + + Please note that we did not create these binaries, nor do we support + them. If you have any problems installing them, please contact their + makers. + * [1]AIX + * DOS: [2]DJGPP + * [3]HP-UX Porting Center + * [4]SCO OpenServer/Unixware + * Solaris (SPARC, Intel): [5]Sunfreeware + * SGI: [6]SGI Freeware + * Windows 95, 98, and NT: [7]Cygwin for Windows 95, 98, and NT | + [8]GNU Win32 related projects by Mumit Khan + * [9]The Written Word offers binaries for Solaris 2.5.1, 2.6, + 2.7/SPARC, 2.7/Intel, IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX + 10.20, and HP-UX 11.00. + + In addition to those specific offerings, you can get a binary + distribution CD-ROM from the [10]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. + _________________________________________________________________ + + [11]Return to the GCC Installation page + +References + + 1. http://www-frec.bull.com/docs/download.htm + 2. http://www.delorie.com/djgpp/ + 3. http://hpux.cae.wisc.edu/ + 4. http://www.sco.com/skunkware/devtools/index.html#gcc + 5. http://www.sunfreeware.com/ + 6. http://freeware.sgi.com/ + 7. http://sources.redhat.com/cygwin/ + 8. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ + 9. ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/ + 10. http://www.fsf.org/order/order.html + 11. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/BUILD b/gnu/egcs/install/BUILD index 70eff6b3d31..a14c39adc0d 100644 --- a/gnu/egcs/install/BUILD +++ b/gnu/egcs/install/BUILD @@ -1,15 +1,15 @@ Installing GCC: Building - + Now that GCC is configured, you are ready to build the compiler and runtime libraries. - + We _highly_ recommend that GCC be built using GNU make; other versions may work, then again they might not. - + (For example, many broken versions of make will fail if you use the recommended setup where _objdir_ is different from _srcdir_.) - + Building a native compiler For a native build issue the command `make bootstrap'. This will build @@ -24,12 +24,12 @@ Building a native compiler * Perform a comparison test of the stage2 and stage3 compilers. * Build runtime libraries using the stage3 compiler from the previous step. - + If you are short on disk space you might consider `make bootstrap-lean' instead. This is identical to `make bootstrap' except that object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. - + If you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information with "make CFLAGS='-O' LIBCFLAGS='-g @@ -37,28 +37,28 @@ Building a native compiler will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) - + If you used the flag --enable-languages=... to restrict the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, that re-defining LANGUAGES when calling `make bootstrap' _*does not*_ work anymore! - + Building a cross compiler We recommend reading the [1]crossgcc FAQ for information about building cross compilers. - + 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 native compiler. You can then use the native GCC compiler to build the cross compiler. - + Assuming you have already installed a native copy of GCC and - configured your corss compiler, issue the command "make", which + configured your cross compiler, issue the command "make", which performs the following steps: * Build host tools necessary to build the compiler such as texinfo, bison, gperf. @@ -68,20 +68,22 @@ Building a cross compiler GCC source tree before configuring. * Build the compiler (single stage only). * Build runtime libraries using the compiler from the previous step. - + Note that if an error occurs in any step the make process will exit. - + Building in parallel - If you have a multiprocessor you can use `make bootstrap MAKE="make -j - 2" -j 2' instead of just `make bootstrap' when building GCC. You can + If you have a multiprocessor system you can use `make bootstrap + MAKE="make -j 2" -j 2' or just `make -j 2 bootstrap' for GNU Make 3.79 + and above instead of just `make bootstrap' when building GCC. You can use a bigger number instead of two if you like. In most cases, it won't help to use a number bigger than the number of processors in your machine. _________________________________________________________________ - - _Last modified on August 27, 1999._ + + [2]Return to the GCC Installation page References 1. http://www.objsw.com/CrossGCC/ + 2. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/CONFIGURE b/gnu/egcs/install/CONFIGURE index 9f88368b332..a881b59c76d 100644 --- a/gnu/egcs/install/CONFIGURE +++ b/gnu/egcs/install/CONFIGURE @@ -1,39 +1,41 @@ Installing GCC: Configuration - + Like most GNU software, GCC must be configured before it can be built. This document describes the recommended configuration procedure for both native and cross targets. - + We use _srcdir_ to refer to the toplevel source directory for GCC; we use _objdir_ to refer to the toplevel build/object directory. - + First, we _highly_ recommend that GCC be built into a separate directory than the sources which does _not_ reside within the source tree. This is how we generally build GCC; building where _srcdir_ == _objdir_ should still work, but doesn't get extensive testing; building where _objdir_ is a subdirectory of _srcdir_ is unsupported. - + Second, when configuring a native system, either "cc" or "gcc" must be in your path or you must set CC in your environment before running configure. Otherwise the configuration scripts may fail. - + To configure GCC: - + % mkdir _objdir_ % cd _objdir_ % _srcdir_/configure _[target]_ _[options]_ - + _target specification_ * GCC has code to correctly determine the correct value for _target_ for nearly all native systems. Therefore, we highly recommend you not provide a configure target when configuring a native compiler. - * _target_ must be specified when configuring a cross compiler; - examples of valid targets would be i960-rtems, m68k-coff, sh-elf, - etc. - + * _target_ must be specified as --target=_target_ when configuring a + cross compiler; examples of valid targets would be i960-rtems, + m68k-coff, sh-elf, etc. + * Specifying just _target_ instead of --target=_target_ implies that + the host defaults to _target_. + _options specification_ - + Use _options_ to override several configure time options for GCC. A partial list of supported options: * --prefix=_dirname_ -- Specify the toplevel installation directory. @@ -70,10 +72,12 @@ be built to support different target variants, calling conventions, etc. This is the default. * --enable-threads -- Specify that the target supports threads. This - affects only the Objective-C compiler and runtime library. + affects the Objective-C compiler and runtime library, and + exception handling for other languages like C++ and Java. * --enable-threads=_lib_ -- Specify that _lib_ is the thread support - library. This affects only the Objective-C compiler and runtime - library. + library. This affects the Objective-C compiler and runtime + library, and exception handling for other languages like C++ and + Java. * --with-cpu=_cpu_ -- Specify which cpu variant the compiler should generate code for by default. This is currently only supported on the some ports, specifically arm, powerpc, and SPARC. If configure @@ -81,14 +85,15 @@ ultrasparc) you provide, please check the configure script for a complete list of supported models. * --enable-target-optspace -- Specify that target libraries should - be optimzied for code space instead of code speed. This is the + be optimized for code space instead of code speed. This is the default for the m32r platform. * --enable-cpp -- Specify that a shell script which emulates traditional cpp functionality should be installed. * --enable-cpplib -- Specify that the functionality of CPP should be - integrated into the compiler itself. This is still under - development, but may be useful in limited situations. This option - is never enabled by default. + integrated into the compiler itself. This option is not supported + by snapshots since November 2000. In snapshots where it is + supported, it is not enabled by default, except for snapshots very + close to November 2000. * --without-fast-fixincludes -- Specify that the old, slower method of fixing the system header files should be used. EGCS 1.1.x and older releases default to the slow version. GCC 2.95 and newer @@ -99,9 +104,8 @@ addition, libstdc++'s include files will be installed in ${libsubdir}/include/g++ unless you overruled it by using --with-gxx-include-dir=_dirname_. Using this option is - particularly useful if you intend to use several versions of - egcs/gcc in parallel. This is currently supported by libf2c and - libstdc++. + particularly useful if you intend to use several versions of GCC + in parallel. This is currently supported by libf2c and libstdc++. * --enable-languages=_lang1_,_lang2_,... -- Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for _lang_x you can issue the @@ -109,29 +113,35 @@ grep language= */config-lang.in Currently, you can use any of the following: CHILL, c++, f77, java and objc. Please note, that this switch does not work with EGCS - 1.1.2 or older versions of egcs. It will be supported in GCC 2.95 - and newer version. + 1.1.2 or older versions of egcs. It is supported in GCC 2.95 and + newer versions. If you do not pass this flag, all languages available in the gcc sub-tree will be configured. Re-defining LANGUAGES when calling make bootstrap _*does not*_ work anymore, as those language sub-directories might not have been configured! * --with-dwarf2 -- Specify that the compiler should use DWARF2 debugging information as the default. - + Some options which only apply to building cross compilers: * --with-headers=_dir_ -- Specifies a directory which has target - include files. These include files will be copied into the gcc - install directory. Fixincludes will be run on these files to make - them compatible with gcc. + include files. _This options is required_ when building a cross + compiler, if ${prefix}/${target}/sys-include doesn't pre-exist. + These include files will be copied into the gcc install directory. + Fixincludes will be run on these files to make them compatible + with gcc. * --with-libs=_"dir1 dir2 ... dirN"_ -- Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the gcc install directory. * --with-newlib -- Specifies that "newlib" is being used as the target C library. This causes __eprintf to be omitted from libgcc.a on the assumption that it will be provided by newlib. - + Note that each --enable option has a corresponding --disable option and that each --with option has a corresponding --without option. _________________________________________________________________ - - _Last modified on July 16, 1999._ + + [1]Return to the GCC Installation page + +References + + 1. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/DOWNLOAD b/gnu/egcs/install/DOWNLOAD index 785ca3242e8..fc72c41fa78 100644 --- a/gnu/egcs/install/DOWNLOAD +++ b/gnu/egcs/install/DOWNLOAD @@ -1,39 +1,40 @@ Downloading GCC - - GCC is distributed via FTP tarballs compressed with gzip or bzip2. It - is possible to download a full distribution or specific components. - + + GCC is distributed via CVS and FTP tarballs compressed with gzip or + bzip2. It is possible to download a full distribution or specific + components. + + Please refer to our [1]releases web page for information on how to + obtain GCC. + The full distribution includes the C, C++, Objective-C, Fortran, Java, and Chill compilers. The full distribution also includes runtime libraries for C++, Objective-C and Fortran. In the future the GNU compiler testsuites will be included in the full distribution. - + If you choose to download specific components, you must download the core gcc distribution plus any language specific distributions you wish to use. The core distribution includes the C language front-end - as well as the shared componenets. Each language has a tarball which + as well as the shared components. Each language has a tarball which includes the language front-end as well as the language runtime (when appropriate). - + Unpack the core distribution as well as any language specific distributions in the same directory. - - XXX FSF mirror sites - - [1]FTP download from egcs.cygnus.com (USA California) - - [2]FTP download from go.cygnus.com (USA California -- High speed link - provided by Stanford) - - GCC releases are available on many [3]FTP mirror sites. If possible, - please use one of these. + + If you also intend to build binutils (either to upgrade an existing + installation or for use in place of the corresponding tools of your + OS), unpack the binutils distribution either in the same directory or + a separate one. In the latter case, add symbolic links to any + components of the binutils you intend to build alongside the compiler + (bfd, binutils, gas, gprof, ld, opcodes,...) to the directory + containing the GCC sources. _________________________________________________________________ - - _Last modified on July 16, 1999._ + + [2]Return to the GCC Installation page References - 1. ftp://egcs.cygnus.com/pub/egcs/releases/index.html - 2. ftp://go.cygnus.com/pub/sourceware.cygnus.com/pub/egcs/releases/index.html - 3. http://gcc.gnu.org/mirrors.html + 1. http://gcc.gnu.org/releases.html + 2. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/FINALINSTALL b/gnu/egcs/install/FINALINSTALL index 918d649157e..5403c41a7ef 100644 --- a/gnu/egcs/install/FINALINSTALL +++ b/gnu/egcs/install/FINALINSTALL @@ -1,29 +1,31 @@ Installing GCC: Final installation - + Now that GCC has been built and tested, you can install it with `cd _objdir_; make install' for a native compiler or `cd _objdir_; make install LANGUAGES="c c++"' for a cross compiler (note installing cross compilers will be easier in the next release!). - + That step completes the installation of GCC; user level binaries can be found in _prefix_/bin where _prefix_ is the value you specified with the --prefix to configure (or /usr/local by default). - + If you don't mind, please quickly review the [1]build status page. If your system is not listed, send a note to [2]gcc@gcc.gnu.org - indicating that you successfully built and installed GCC. Include the - output from running _srcdir_/config.guess. (Do not send us the - config.guess file itself, just the output from running it!) - + indicating that you successfully built and installed GCC. + + Include the output from running _srcdir_/config.guess. (Do not send us + the config.guess file itself, just the output from running it!) + If you find a bug, please report it following our [3]bug reporting - guidlines. + guidelines. _________________________________________________________________ - - _Last modified on July 16, 1999._ + + [4]Return to the GCC Installation page References - 1. http://egcs.cygnus.com/gcc-2.95/buildstat.html + 1. http://gcc.gnu.org/gcc-2.95/buildstat.html 2. mailto:gcc@gcc.gnu.org - 3. http://gcc.gnu.org/faq.html#bugreport + 3. http://gcc.gnu.org/bugs.html + 4. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/INDEX b/gnu/egcs/install/INDEX index cc7e59a51ae..e84f82642ca 100644 --- a/gnu/egcs/install/INDEX +++ b/gnu/egcs/install/INDEX @@ -1,51 +1,45 @@ Installing GCC - + The latest version of this document is always available at - [1]http://egcs.cygnus.com/install/. - + [1]http://gcc.gnu.org/install/. + This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. - + GCC includes several components that previously were separate distributions with their own installation instructions. This document - supercedes all package specific installation instructions. We provide + supersedes all package specific installation instructions. We provide the component specific installation information in the source distribution for historical reference purposes only. - - We recommend you read the entire generic installation instructions as - well as any target specific installation instructions before you - proceed to configure, build, test and install GCC. - - If something goes wrong in the configure, build, test or install - procedures, first double check that you followed the generic and - target specific installation instructions carefully. Then check the - [2]FAQ to see if your problem is covered before you file a bug report. - - _Before_ starting the build/install procedure _please_ browse the - [3]host/target specific installation notes. - - The installation procedure is broken into five steps. - * [4]downloading the source - * [5]configure - * [6]build - * [7]test (optional) - * [8]install - _________________________________________________________________ - - [9]Return to the GCC home page + + _Before_ starting the build/install procedure please check the + [2]host/target specific installation notes. We recommend you browse + the entire generic installation instructions before you proceed. + + The installation procedure itself is broken into five steps. + 1. [3]Downloading the source + 2. [4]Configuration + 3. [5]Building + 4. [6]Testing (optional) + 5. [7]Final install + + Please note that GCC does not support `make uninstall` and probably + won't do so in the near future as this would open a can of worms. + Instead, we suggest that you install GCC into a directory of its own + and simply remove that directory when you do not need that specific + version of GCC any longer. _________________________________________________________________ - - _Last modified on July 15, 1999._ + + [8]Return to the GCC Installation page References - 1. http://egcs.cygnus.com/install/ - 2. http://gcc.gnu.org/faq.html - 3. http://gcc.gnu.org/install/specific.html - 4. http://gcc.gnu.org/install/download.html - 5. http://gcc.gnu.org/install/configure.html - 6. http://gcc.gnu.org/install/build.html - 7. http://gcc.gnu.org/install/test.html - 8. http://gcc.gnu.org/install/finalinstall.html - 9. http://gcc.gnu.org/index.html + 1. http://gcc.gnu.org/install/ + 2. http://gcc.gnu.org/install/specific.html + 3. http://gcc.gnu.org/install/download.html + 4. http://gcc.gnu.org/install/configure.html + 5. http://gcc.gnu.org/install/build.html + 6. http://gcc.gnu.org/install/test.html + 7. http://gcc.gnu.org/install/finalinstall.html + 8. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/SPECIFIC b/gnu/egcs/install/SPECIFIC index 54c9a8f6c55..9cadc511a7f 100644 --- a/gnu/egcs/install/SPECIFIC +++ b/gnu/egcs/install/SPECIFIC @@ -1,83 +1,60 @@ Host/Target specific installation notes for GCC - + Please read this document carefully _before_ installing the GNU Compiler Collection on your machine. * [1]alpha*-dec-linux* * [2]alpha*-dec-osf* - * [3]GCC with DOS + * [3]DOS * [4]hppa*-hp-hpux* * [5]hppa*-hp-hpux9 * [6]hppa*-hp-hpux10 - * [7]i?86-*-linux* - * [8]i?86-*-sco3.2v5* - * [9]i?86-*-udk - * [10]*-ibm-aix* - * [11]m68k-*-nextstep* - * [12]m68k-sun-sunos4.1.1 - * [13]mips*-sgi-irix[45] - * [14]mips*-sgi-irix6 - * [15]powerpc-*-linux-gnu* - * [16]*-*-solaris* - * [17]sparc-sun-solaris* - * [18]sparc-sun-solaris2.7 - * [19]Sun V5.0 Compiler Bugs - * [20]sparc-sun-sunos* - * [21]sparc-unknown-linux-gnulibc1 - * [22]sparc64-*-* - * [23]GCC with Windows or OS/2 - - * [24]all ELF targets (SVR4, Solaris, etc.) + * [7]hppa*-hp-hpux11 + * [8]*-*-linux-gnu + * [9]i?86-*-linux* + * [10]i?86-*-sco3.2v5* + * [11]i?86-*-solaris* + * [12]i?86-*-udk + * [13]*-ibm-aix* + * [14]m68k-*-nextstep* + * [15]m68k-sun-sunos4.1.1 + * [16]mips*-sgi-irix[45] + * [17]mips*-sgi-irix6 + * [18]powerpc-*-linux-gnu* + * [19]*-*-solaris* + * [20]sparc-sun-solaris* + * [21]sparc-sun-solaris2.7 + * [22]Sun V5.0 Compiler Bugs + * [23]sparc-sun-sunos* + * [24]sparc-unknown-linux-gnulibc1 + * [25]sparc64-*-* + * [26]Microsoft Windows + * [27]OS/2 + + * [28]all ELF targets (SVR4, Solaris, etc.) _________________________________________________________________ - + alpha*-dec-linux* - - GNU/Linux Alpha EV56 or PCA56 hosts running Red Hat 4.2 or 5.0 may see - errors of this sort: - Error: Unknown pseudo-op: `.arch' - - This is a signal that a new assembler is needed if you want to - generate BWX insns for your machine. - - The version of GCC shipped with Red Hat 4.2 (2.7.0.2) has a fault - wherein it will silently generate incorrect code. The version shipped - with Red Hat 5.0 (2.8.0.1) is not broken, but required an extra - -m21164a argument on the command-line. In order to visibly trap - 2.7.0.2, I now issue DEC's .arch pseudo into the assembly. Relieving - the problem of mucking with command-line arguments for 2.8.0.1 is a - pleasant side effect. - - If you've got Red Hat 5.0 installed, you may grab binutils 2.9.1 and - be happy. If you've got Red Hat 4.2, bugs make it much harder to - upgrade pieces on your own, and you are better off upgrading the - entire system. - - In either case, your problem may be bypassed by not emitting BWX code - by default. Do this by using - configure alphaev5-unknown-linux-gnulibc1 - - if you have RH 4.2, or - configure alphaev5-unknown-linux-gnu - - if you have RH 5.0. - + + We strongly recommend to upgrade to binutils 2.10 (or newer). + The following error: Error: macro requires $at register while noat in effect - also indicates that you should upgrade to a newer version of the - assembler, 2.9 or later. If you can not upgrade the assembler, the - compiler option "-Wa,-m21164a" may work around this problem. + indicates that you should upgrade to a newer version of the assembler, + 2.9 or later. If you can not upgrade the assembler, the compiler + option "-Wa,-m21164a" may work around this problem. _________________________________________________________________ - + alpha*-dec-osf* - + If you install a shared libstdc++ and, when you link a non-trivial C++ program (for example, gcc/testsuite/g++.other/delete3.C), the linker reports a couple of errors about multiply-defined symbols (for example, nothrow, __throw and terminate(void)), you've probably got a linker bug, for which there's no known fix. The officially recommended work-around is to remove the shared libstdc++. - + An alternative solution is to arrange that all symbols from libgcc get copied to the shared libstdc++; see detailed solution below. (Surprising as it may seem, this does indeed fix the problem!) _Beware_ @@ -86,59 +63,66 @@ if programs start to depend on libstdc++ to provide symbols that used to be only in libgcc, you must arrange that libstdc++ keeps providing them, otherwise the programs will have to be relinked. - + The magic spell is to add -Wl,-all,-lgcc,-none to the definition of macro SHDEPS in libstdc++/config/dec-osf.ml _before_ - alpha*-dec-osf*/libstdc++/Makefile is created (a [25]patch that does + alpha*-dec-osf*/libstdc++/Makefile is created (a [29]patch that does just that is available). If the Makefile already exists, run ./config.status within directory alpha*-dec-osf*/libstdc++ (and alpha*-dec-osf*/ieee/libstdc++, if it also exists). Remove any existing libstdc++.so* from such directories, and run make all-target-libstdc++ in the top-level directory, then make install-target-libstdc++. - + If you have already removed the build tree, you may just remove libstdc++.so.2.10.0 from the install tree and re-create it with the command gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm. If the ieee sub-directory exists, repeat this command in it, with the additional flag -mieee. _________________________________________________________________ - - GCC with DOS - - A binary distribution is available at [26]Simtel.Net and its mirrors. - ________________________________________________________________________ - + + DOS + + Please have a look at our [30]binaries page. + _________________________________________________________________ + hppa*-hp-hpux* - - We _highly_ recommend using gas/binutils-2.8 or newer on all hppa platforms; - you may encounter a variety of problems when using the HP assembler. - - If you wish to use pa-risc 2.0 architecture support, you must use either the - HP assembler or a recent [27]snapshot of gas. - - More specific information to hppa*-hp-hpux* targets follows. - ________________________________________________________________________ - + + We _highly_ recommend using gas/binutils-2.8 or newer on all hppa + platforms; you may encounter a variety of problems when using the HP + assembler. + + Specifically, -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 and configure GCC with the --with-gnu-as option. + + If you wish to use pa-risc 2.0 architecture support, you must use + either the HP assembler or a recent [31]snapshot of gas. + + More specific information to hppa*-hp-hpux* targets follows. + _________________________________________________________________ + hppa*-hp-hpux9 - - The HP assembler has major problems on this platform. We've tried to work - around the worst of the problems. However, those workarounds may be causing - linker crashes in some circumstances; the workarounds also probably prevent - shared libraries from working. Use the GNU assembler to avoid these problems. - - The configuration scripts for GCC will also trigger a bug in the hpux9 shell. - To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to /bin/ksh in - your environment. - ________________________________________________________________________ - + + The HP assembler has major problems on this platform. We've tried to + work around the worst of the problems. However, those workarounds may + be causing linker crashes in some circumstances; the workarounds also + probably prevent shared libraries from working. Use the GNU assembler + to avoid these problems. + + The configuration scripts for GCC will also trigger a bug in the hpux9 + shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to + /bin/ksh in your environment. + _________________________________________________________________ + hppa*-hp-hpux10 - - For hpux10.20, we _highly_ recommend you pick up the latest sed patch - PHCO_15468 from HP. HP has two sites which provide patches free of charge: - * [28]US, Canada, Asia-Pacific, and Latin-America - * [29]Europe - + + For hpux10.20, we _highly_ recommend you pick up the latest sed patch + PHCO_19798 from HP. HP has two sites which provide patches free of + charge: + * [32]US, Canada, Asia-Pacific, and Latin-America + * [33]Europe + The HP assembler on these systems is much better than the hpux9 assembler, but still has some problems. Most notably the assembler inserts timestamps into each object file it creates, causing the @@ -146,25 +130,40 @@ be able to continue by saying `make all' after getting the failure from `make bootstrap'. _________________________________________________________________ - + + hppa*-hp-hpux11 + + GCC 2.95.2 does not support HP-UX 11, and it cannot generate 64-bit + object files. Current (as of late 2000) snapshots and GCC 3.0 do + support HP-UX 11. + _________________________________________________________________ + + *-*-linux-gnu + + If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install + out-of-the-box. You'll get compile errors while building libstdc++. + The patch [34]glibc-2.2.patch, that is to be applied in the GCC source + tree, fixes the compatibility problems. + _________________________________________________________________ + i?86-*-linux* - + You will need binutils-2.9.1.0.15 or newer for exception handling to work. - + If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can - be found on [30]www.bitwizard.nl. + be found on [35]www.bitwizard.nl. _________________________________________________________________ - + i?86-*-sco3.2v5* - + If you are building languages other than C, you must follow the instructions about invoking `make bootstrap' because the native OpenServer compiler will build a cc1plus that will not correctly parse many valid C++ programs including those in libgcc.a. _You must do a `make bootstrap' if you are building with the native compiler._ - + Use of the `-march-pentiumpro' flag can result in unrecognized opcodes when using the native assembler. While it's rather rare to see these emitted by GCC yet, errors of the basic form: @@ -174,56 +173,65 @@ are symptoms of this problem. You may work around this by not building affected files with that flag or by using the GNU assembler. Users of GNU assembler should see the note below for hazards on doing so. - + If you choose to configure with --enable-shared you should also - specificy --with-gnu-as --disable-multilib even if you are not using - the GNU assembler. In doing so you will give up the ability to - generate COFF executables as described below. This combination of - flags is necessary to suppress negative interactions with multilibing. - + specify --with-gnu-as --disable-multilib even if you are not using the + GNU assembler. In doing so you will give up the ability to generate + COFF executables as described below. This combination of flags is + necessary to suppress negative interactions with multilibing. + The native SCO assembler that is provided with the OS at no charge is normally required. If, however, you must be able to use the GNU - assembler you may configure this package using the flags - --with-gnu-as. You must use a recent version of GNU binutils; version - 2.9.1 seems to work well. If you select this option, you will be - unable to reliably build COFF images. In general, the --with-gnu-as - option isn't as well tested as the native assembler. - + assembler (perhaps you're compiling code with asms that require GAS + syntax) you may configure this package using the flags --with-gnu-as. + You must use a recent version of GNU binutils; versions past 2.9.1 + seems to work well. If you select this option, you will be unable to + reliably build COFF images. In general, the --with-gnu-as option isn't + as well tested as the native assembler. + Unlike various prereleases of GCC that used -belf and defaulted to COFF, you must now use the -melf and -mcoff flags to toggle between the two object file formats. ELF is now the default. - + Look in gcc/config/i386/sco5.h (search for "messy") for additional OpenServer-specific flags. - + Systems based on OpenServer before 5.0.4 (`uname -X' will tell you what you're running) require TLS597 from ftp.sco.com/TLS for C++ constructors and destructors to work right. - + The system linker in (at least) 5.0.4 and 5.0.5 will sometimes do the wrong thing for a construct that GCC will emit for PIC code. This can be seen as execution testsuite failures when using -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c. For 5.0.5, an updated linker that will cure this problem is available. You must - install both [31]ftp://ftp.sco.com/Supplements/rs505a/ and - [32]OSS499A. - + install both [36]ftp://ftp.sco.com/Supplements/rs505a/ and + [37]OSS499A. + The dynamic linker in OpenServer 5.0.5 (earlier versions may show the same problem) aborts on certain g77-compiled programs. It's - particluarly likely to be triggered by building Fortran code with the + particularly likely to be triggered by building Fortran code with the -fPIC flag. Although it's conceivable that the error could be triggered by other code, only G77-compiled code has been observed to cause this abort. If you are getting core dumps immediately upon execution of your g77 program - and especially if it's compiled with - -fPIC - try applying [33]`sco_osr5_g77.patch' to your libf2c and + -fPIC - try applying [38]`sco_osr5_g77.patch' to your libf2c and rebuilding GCC. Affected faults, when analyzed in a debugger, will show a stack backtrace with a fault occurring in rtld() and the program running as /usr/lib/ld.so.1. This problem has been reported to SCO engineering and will hopefully be addressed in later releases. _________________________________________________________________ - + + i?86-*-solaris* + + GCC 2.95.2, when configured to use the GNU assembler, would invoke it + with the -s switch, that GNU as up to 2.9.5.0.12 does not support. If + you'd rather not use a newer GNU as nor the native assembler, you'll + need the patch [39]`x86-sol2-gas.patch'. + _________________________________________________________________ + i?86-*-udk - + This target emulates the SCO Universal Development Kit and requires that package be installed. (If it is installed, you will have a /udk/usr/ccs/bin/cc file present.) It's very much like the @@ -232,35 +240,35 @@ Unixware 2. This target will generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, with the same warnings and caveats as the SCO UDK. - + You can stage1 with either your native compiler or with UDK. If you don't do a full bootstrap when initially building with your native compiler you will have an utterly unusable pile of bits as your reward. - + This target is a little tricky to build because we have to distinguish it from the native tools (so it gets headers, startups, and libraries from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this: CC=/udk/usr/ccs/bin/cc _/your/path/to/_gcc/configure --host=i686-pc-udk --tar -get=i686-pc-udk --exec-prefix=udk- +get=i686-pc-udk --program-prefix=udk- _You should substitute 'i686' in the above command with the appropriate processor for your host._ - + You should follow this with a `make bootstrap' then `make install'. You can then access the UDK-targeted GCC tools by adding udk- before the commonly known name. For example, to invoke the C compiler, you would use `udk-gcc'. They will coexist peacefully with any native-target GCC tools you may have installed. _________________________________________________________________ - + *-ibm-aix* - + AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or newer is recommended to build on this platform. - + Errors involving "alloca" when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the @@ -270,19 +278,19 @@ get=i686-pc-udk --exec-prefix=udk- environment variable does not provide a definition that will confuse configure. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). - + Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its - [34]service.boulder.ibm.com website as PTF U455193. - + [40]service.boulder.ibm.com website as PTF U455193. + Binutils does not support AIX 4.3 (at least through release 2.9). GNU as and GNU ld will not work properly and one should not configure GCC to use those GNU utilities. Use the native AIX tools which do interoperate with GCC. - + AIX 4.3 utilizes a new "large format" archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 to parse archive libraries did not handle the new format @@ -292,22 +300,24 @@ get=i686-pc-udk --exec-prefix=udk- option of the archive command may be used to create archives of 32-bit objects using the original "small format". A correct version of the routines is shipped with AIX 4.3.2. - + The initial assembler shipped with AIX 4.3.0 generates incorrect - object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUPUT FROM + object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer - Support and from its [35]service.boulder.ibm.com website as PTF + Support and from its [41]service.boulder.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. - + The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A - fix for APAR IX87327 will be available from IBM Customer Support. + fix for APAR IX87327 is available from IBM Customer Support and from + its [42]service.boulder.ibm.com website as PTF U461879. This fix is + incorporated in AIX 4.3.3 and above. _________________________________________________________________ - + m68k-*-nextstep* - + You absolutely _must_ use GNU sed and GNU make on this platform. - + On NEXTSTEP 3.x where x < 3 the build of GCC will abort during stage1 with an error message like this: _eh @@ -318,17 +328,17 @@ get=i686-pc-udk --exec-prefix=udk- The reason for this is the fact that NeXT's assembler for these versions of the operating system does not support the .section pseudo op that's needed for full C++ exception functionality. - + As NeXT's assembler is a derived work from GNU as, a free replacement that does can be obtained at - [36]ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s + [43]ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s .tar.gz. - + If you try to build the integrated C++ & C++ runtime libraries on this system you will run into trouble with include files. The way to get around this is to use the following sequence. Note you must have write - permission to the directory _prefix_ you secified in the configuration - preocess of GCC for this sequence to work. + permission to the directory _prefix_ you specified in the + configuration process of GCC for this sequence to work. cd bld-gcc make all-texinfo all-bison all-byacc all-binutils all-gas all-ld cd gcc @@ -337,14 +347,14 @@ get=i686-pc-udk --exec-prefix=udk- cd .. make bootstrap3 _________________________________________________________________ - + m68k-sun-sunos4.1.1 - + It is reported that you may need the GNU assembler on this platform. _________________________________________________________________ - + mips*-sgi-irix[45] - + You must use GAS on these platforms, as the native assembler can not handle the code for exception handling support. Either of these messages indicates that you are using the MIPS assembler when instead @@ -360,7 +370,7 @@ get=i686-pc-udk --exec-prefix=udk- These systems don't have ranlib, which various components in GCC need; you should be able to avoid this problem by installing GNU binutils, which includes a functional ranlib for this system. - + You may get the following warning on irix4 platforms, it can be safely ignored. warning: foo.o does not have gp tables for all its sections. @@ -372,26 +382,40 @@ get=i686-pc-udk --exec-prefix=udk- IRIX 5.2. We recommend you use GNU make instead of the vendor supplied make program; however, you may have success with "smake" on IRIX 5.2 if you do not have GNU make available. - - See [37]http://reality.sgi.com/ariel/freeware for more information + + See [44]http://reality.sgi.com/ariel/freeware for more information about using GCC on IRIX platforms. _________________________________________________________________ - + mips*-sgi-irix6 - + You must _not_ use GAS on irix6 platforms; doing so will only cause problems. - + These systems don't have ranlib, which various components in GCC need; you should be able to avoid this problem by making a dummy script called ranlib which just exits with zero status and placing it in your path. - + + If you are using Irix cc as your bootstrap compiler, you must ensure + that the N32 ABI is in use. To test this, compile a simple C file with + cc and then run file on the resulting object file. The output should + look like: + + test.o: ELF N32 MSB ... + + If you see: + + test.o: ELF 32-bit MSB + + then your version of cc uses the O32 ABI default. You should set the + environment variable CC to 'cc -n32' before configuring GCC. + GCC does not currently support generating O32 ABI binaries in the mips-sgi-irix6 configurations. It used to be possible to create a GCC with O32 ABI only support by configuring it for the mips-sgi-irix5 target. See the link below for details. - + GCC does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but IRIX @@ -400,62 +424,68 @@ get=i686-pc-udk --exec-prefix=udk- padded at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes of the register when it should be loaded into the upper 4 bytes of the register. - + GCC is consistent with itself, but not consistent with the SGI C - compiler [and the SGI supplied runtime libraries], so the only + compiler (and the SGI supplied runtime libraries), so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. I can only recall seeing two of them: inet_ntoa, and semctl. - - See [38]http://reality.sgi.com/ariel/freeware for more information + + See [45]http://reality.sgi.com/ariel/freeware for more information about using GCC on IRIX platforms. _________________________________________________________________ - + powerpc-*-linux-gnu* - - You will need [39]binutils-2.9.4.0.8 or newer for a working GCC. It is + + You will need [46]binutils-2.9.4.0.8 or newer for a working GCC. It is strongly recommended to recompile binutils if you initially built it with gcc-2.7.2.x. _________________________________________________________________ - + *-*-solaris* - + Starting with Solaris, Sun does not ship a C compiler any more. To bootstrap and install GCC you first have to install a pre-built - compiler, for example from [40]http://www.sunfreeware.com. - + compiler, see our [47]binaries page for details. + Sun as 4.X is broken in that it cannot cope with long symbol names. A - typical error message might look similiar to the following: - + typical error message might look similar to the following: + /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: can't compute value of an expression involving an external symbol. - - See the [41]How to work around too long C++ symbol names? FAQ entry + + See the [48]How to work around too long C++ symbol names? FAQ entry for further information. - + Sun make in all known Solaris 1 (SunOS 4) and Solaris 2 releases has a broken _VPATH_ mechanism, which means you must either: * Use GNU make (recommended), _or:_ * Always build in the source directory, _or:_ * _(For GCC 2.95.1 only)_ apply the patches mentioned at - [42]http://www.gnu.org/software/gcc/egcstensions.html#sun-make. + [49]http://www.gnu.org/software/gcc/extensions.html#sun-make. _________________________________________________________________ - + sparc-sun-solaris* - + binutils 2.9.1 has known bugs on this platform. We recommend to use the vendor tools (Sun as, Sun ld) until these have been fixed. + Unfortunately, C++ shared libraries, including libstdc++, won't work + properly if assembled with Sun as: the linker will complain about + relocations in read-only sections, in the definition of virtual + tables. Some possible work-arounds: use some development release of + binutils, wait for the next stable binutils release or refrain from + creating C++ shared libraries. _________________________________________________________________ - + sparc-sun-solaris2.7 - + Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 and later, including all EGCS releases. Sun formerly recommended 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to recommend it only for people who use Sun's compilers. - + Here are some workarounds to this problem: * Do not install Sun patch 107058-01 until after Sun releases a complete patch for bug 4210064. This is the simplest course to @@ -477,62 +507,66 @@ get=i686-pc-udk --exec-prefix=udk- -08 or later should fix the bug, but (as of 1999-10-06) it is still being tested. _________________________________________________________________ - + Sun V5.0 Compiler Bugs - - The Sun V5.0 compilers are known to mis-compile GCC, which in turn - causes GCC to fail its bootstrap comparison test. We expect to have a - workaround ready in time for GCC 2.95.2. + + The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC + 2.95.1, which in turn causes GCC to fail its bootstrap comparison + test. GCC 2.95.2 has a workaround. _________________________________________________________________ - + sparc-sun-sunos* - + A bug in the SunOS4 linker will cause it to crash when linking -fPIC compiled objects (and will therefore not allow you to build shared libraries). - + To fix this problem you can either use the most recent version of binutils or get the latest SunOS4 linker patch (patch ID 100170-10) from Sun's patch site. _________________________________________________________________ - + sparc-unknown-linux-gnulibc1 - - It has been reported that you might need [43]binutils-2.8.1.0.23 for + + It has been reported that you might need [50]binutils-2.8.1.0.23 for this platform, too. _________________________________________________________________ - + sparc64-*-* - + GCC version 2.95 is not able to compile code correctly for sparc64 targets. Users of the Linux kernel, at least, can use the sparc32 program to start up a new shell invocation with an environment that causes configure to recognize (via uname -a) the system as sparc-*-* instead. _________________________________________________________________ - - GCC with Windows or OS/2 - - GCC does not currently support Windows, either natively or with the - cygwin32 dll. However Mumit Khan has been working on supporting - Windows with GCC. You should check out his site if you're interested - in Windows support. [44]GNU Win32 related projects - + + Microsoft Windows (32 bit) + + GCC currently builds under the [51]Cygwin environment. However you + need to delete (or rename) the texinfo directory included with the GCC + sources. You will also need to configure with the option + --with-included-gettext. + _________________________________________________________________ + + OS/2 + GCC does not currently support OS/2. However, Andrew Zabolotny has - been working on a generic os/2 port with pgcc. The current code code - can be found at [45]http://www.goof.com/pcg/os2/. + been working on a generic OS/2 port with pgcc. The current code code + can be found at [52]http://www.goof.com/pcg/os2/. + + An older copy of GCC 2.8.1 is included with the EMX tools available at + [53]ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/. _________________________________________________________________ - + all ELF targets (SVR4, Solaris, etc.) - + C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. _________________________________________________________________ - - [46]Return to the GCC Installation page - - _Last modified on October 17, 1999._ + + [54]Return to the GCC Installation page References @@ -542,43 +576,51 @@ References 4. http://gcc.gnu.org/install/specific.html#hppa*-hp-hpux* 5. http://gcc.gnu.org/install/specific.html#hppa*-hp-hpux9 6. http://gcc.gnu.org/install/specific.html#hppa*-hp-hpux10 - 7. http://gcc.gnu.org/install/specific.html#ix86-*-linux* - 8. http://gcc.gnu.org/install/specific.html#ix86-*-sco3.2v5* - 9. http://gcc.gnu.org/install/specific.html#ix86-*-udk - 10. http://gcc.gnu.org/install/specific.html#*-ibm-aix* - 11. http://gcc.gnu.org/install/specific.html#m68k-*-nextstep* - 12. http://gcc.gnu.org/install/specific.html#m68k-sun-sunos4.1.1 - 13. http://gcc.gnu.org/install/specific.html#mips*-sgi-irix[45] - 14. http://gcc.gnu.org/install/specific.html#mips*-sgi-irix6 - 15. http://gcc.gnu.org/install/specific.html#powerpc-*-linux-gnu* - 16. http://gcc.gnu.org/install/specific.html#*-*-solaris* - 17. http://gcc.gnu.org/install/specific.html#sparc-sun-solaris* - 18. http://gcc.gnu.org/install/specific.html#sparc-sun-solaris2.7 - 19. http://gcc.gnu.org/install/specific.html#sunv5 - 20. http://gcc.gnu.org/install/specific.html#sparc-sun-sunos* - 21. http://gcc.gnu.org/install/specific.html#sparc-unknown-linux-gnulibc1 - 22. http://gcc.gnu.org/install/specific.html#sparc64-*-* - 23. http://gcc.gnu.org/install/specific.html#win+os2 - 24. http://gcc.gnu.org/install/specific.html#elf_targets - 25. http://gcc.gnu.org/install/dec-osf-shlibstdc++.patch - 26. ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/ - 27. ftp://sourceware.cygnus.com/pub/binutils/snapshots - 28. http://us-support.external.hp.com/ - 29. http://europe-support.external.hp.com/ - 30. http://www.bitwizard.nl/sig11/ - 31. ftp://ftp.sco.com/Supplements/rs505a/ - 32. ftp://ftp.sco.com/SLS/ - 33. http://gcc.gnu.org/install/sco_osr5_g77.patch - 34. http://service.boulder.ibm.com/ - 35. http://service.boulder.ibm.com/ - 36. ftp://ftp.next.peak.org/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz - 37. http://reality.sgi.com/ariel/freeware/ - 38. http://reality.sgi.com/ariel/freeware/ - 39. ftp://ftp.varesearch.com/pub/support/hjl/binutils - 40. http://www.sunfreeware.com/ - 41. http://gcc.gnu.org/faq.html#squangle - 42. http://www.gnu.org/software/gcc/egcstensions.html#sun-make - 43. ftp://ftp.yggdrasil.com/private/hjl - 44. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ - 45. http://www.goof.com/pcg/os2/ - 46. http://gcc.gnu.org/install/index.html + 7. http://gcc.gnu.org/install/specific.html#hppa*-hp-hpux11 + 8. http://gcc.gnu.org/install/specific.html#*-*-linux-gnu + 9. http://gcc.gnu.org/install/specific.html#ix86-*-linux* + 10. http://gcc.gnu.org/install/specific.html#ix86-*-sco3.2v5* + 11. http://gcc.gnu.org/install/specific.html#ix86-*-solaris* + 12. http://gcc.gnu.org/install/specific.html#ix86-*-udk + 13. http://gcc.gnu.org/install/specific.html#*-ibm-aix* + 14. http://gcc.gnu.org/install/specific.html#m68k-*-nextstep* + 15. http://gcc.gnu.org/install/specific.html#m68k-sun-sunos4.1.1 + 16. http://gcc.gnu.org/install/specific.html#mips*-sgi-irix[45] + 17. http://gcc.gnu.org/install/specific.html#mips*-sgi-irix6 + 18. http://gcc.gnu.org/install/specific.html#powerpc-*-linux-gnu* + 19. http://gcc.gnu.org/install/specific.html#*-*-solaris* + 20. http://gcc.gnu.org/install/specific.html#sparc-sun-solaris* + 21. http://gcc.gnu.org/install/specific.html#sparc-sun-solaris2.7 + 22. http://gcc.gnu.org/install/specific.html#sunv5 + 23. http://gcc.gnu.org/install/specific.html#sparc-sun-sunos* + 24. http://gcc.gnu.org/install/specific.html#sparc-unknown-linux-gnulibc1 + 25. http://gcc.gnu.org/install/specific.html#sparc64-*-* + 26. http://gcc.gnu.org/install/specific.html#windows + 27. http://gcc.gnu.org/install/specific.html#os2 + 28. http://gcc.gnu.org/install/specific.html#elf_targets + 29. http://gcc.gnu.org/install/dec-osf-shlibstdc++.patch + 30. http://gcc.gnu.org/install/binaries.html + 31. ftp://sources.redhat.com/pub/binutils/snapshots + 32. http://us-support.external.hp.com/ + 33. http://europe-support.external.hp.com/ + 34. http://gcc.gnu.org/install/glibc-2.2.patch + 35. http://www.bitwizard.nl/sig11/ + 36. ftp://ftp.sco.com/Supplements/rs505a/ + 37. ftp://ftp.sco.com/SLS/ + 38. http://gcc.gnu.org/install/sco_osr5_g77.patch + 39. http://gcc.gnu.org/install/x86-sol2-gas.patch + 40. http://service.boulder.ibm.com/ + 41. http://service.boulder.ibm.com/ + 42. http://service.boulder.ibm.com/ + 43. ftp://ftp.next.peak.org/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz + 44. http://reality.sgi.com/ariel/freeware/ + 45. http://reality.sgi.com/ariel/freeware/ + 46. ftp://ftp.varesearch.com/pub/support/hjl/binutils + 47. http://gcc.gnu.org/install/binaries.html + 48. http://gcc.gnu.org/faq.html#squangle + 49. http://www.gnu.org/software/gcc/extensions.html#sun-make + 50. ftp://ftp.yggdrasil.com/private/hjl + 51. http://www.cygwin.com/ + 52. http://www.goof.com/pcg/os2/ + 53. ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/ + 54. http://gcc.gnu.org/install/index.html diff --git a/gnu/egcs/install/TEST b/gnu/egcs/install/TEST index be13f665991..2f3c38efd78 100644 --- a/gnu/egcs/install/TEST +++ b/gnu/egcs/install/TEST @@ -1,13 +1,106 @@ - Installation Instructions: Testing GCC - - The testsuite has been temporarily removed from the gcc distributions - until the copyright status of some tests can be determined. It is - hoped that the testsuite will be included in the gcc releases again - soon. - - Until the testsuite is included it is impossible to run the testsuite. - Sorry. - _________________________________________________________________ - - _Last modified on July 15, 1999._ + Installing GCC: Testing + + _Please note that this is only applicable to current development + versions of GCC and GCC 3.0 or later. GCC 2.95.x does not come with a + testsuite._ + + Before you install GCC, you might wish to run the testsuite. This step + is optional and may require you to download additional software. + + First, you must have [1]downloaded the testsuites. The full + distribution contains testsuites; only if you downloaded the "core" + compiler plus any front ends, you do not have the testsuites. + + Second, you must have a new version of dejagnu on your system; dejagnu + 1.3 will not work. We have made dejagnu snapshots available at + [2]ftp://gcc.gnu.org/pub/gcc/infrastructure until a new version of + dejagnu has been released. + + A few targets require specific preparations: + * In order to run the libio tests on targets which do not fully + support Unix/POSIX commands (e.g. Cgwin), the references to the + dbz directory may be deleted from libio/configure.in. + * When there is difficulty resolving paths to the files init.tcl and + runtest.exp, the following environment variables should be set + appropriately, for example: + + TCL_LIBRARY = /usr/share/tcl8.0 + DEJAGNULIBS = /usr/share/dejagnu + On systems such as Cygwin, these paths are required to be actual + paths, not mounts or links; presumably this is due to some lack of + portability in the dejagnu code. + + Finally, you can run the testsuite (which may take a long time): + + cd _objdir_; make -k check + + The testing process will try to test as many components in the GCC + distribution as possible, including the C, C++ and Fortran compilers + as well as the C++ runtime libraries. + +How can I run the test suite on selected tests? + + As a first possibility to cut down the number of tests that are run it + is possible to use `make check-gcc` or `make check-g++` in the gcc + subdirectory of the object directory. To further cut down the tests + the following is possible: + + make check-gcc RUNTESTFLAGS="execute.exp <other options>" + + This will run all gcc execute tests in the testsuite. + + make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>" + + This will run the g++ "old-deja" tests in the testsuite where the + filename matches 9805*. + + The *.exp files are located in the testsuite directories of the GCC + source, the most important ones being compile.exp, execute.exp, dg.exp + and old-deja.exp. To get a list of the possible *.exp files, pipe the + output of `make check` into a file and look at the "Running ... .exp" + lines. + +How to interpret test results + + After the testsuite has run you'll find various *.sum and *.log files + in the testsuite subdirectories. The *.log files contain a detailed + log of the compiler invocations and the corresponding results, the + *.sum files summarize the results. These summaries list all the tests + that have been run with a corresponding status code: + * PASS: the test passed as expected + * FAIL: the test unexpectedly failed + * XFAIL: the test failed as expected + * UNSUPPORTED: the test is not supported on this platform + * ERROR: the testsuite detected an error + * WARNING: the testsuite detected a possible problem + + It is normal for some tests to report unexpected failures. At the + current time our testing harness does not allow fine grained control + over whether or not a test is expected to fail. We expect to fix this + problem in future releases. + +Submitting test results + + If you want to report the results to the GCC project, use the + contrib/test_summary shell script. Start it in the objdir with + + _srcdir_/contrib/test_summary -p your_commentary.txt -m + gcc-testresults@gcc.gnu.org |sh + + This script uses the Mail program to send the results, so make sure it + is in your PATH. The file your_commentary.txt is prepended to the + testsuite summary and should contain any special remarks you have on + your results or your build environment. Please do not edit the + testsuite result block or the subject line, as these messages are + automatically parsed and presented at the [3]GCC testresults web page. + Here you can also gather information on how specific tests behave on + different platforms and compare them with your results. A few failing + testcases are possible even on released versions and you should look + here first if you think your results are unreasonable. + +References + + 1. http://gcc.gnu.org/install/download.html + 2. ftp://gcc.gnu.org/pub/gcc/infrastructure + 3. http://gcc.gnu.org/testresults/ diff --git a/gnu/egcs/install/binaries.html b/gnu/egcs/install/binaries.html new file mode 100644 index 00000000000..b9b584ce3eb --- /dev/null +++ b/gnu/egcs/install/binaries.html @@ -0,0 +1,58 @@ +<html> +<head> +<title>Installing GCC: Binaries</title> +</head> + +<body> +<h1 align="center">Installing GCC: Binaries</h1> + +<p>We are often asked about pre-compiled versions of GCC. While we cannot +provide these for all platforms, below you'll find links to binaries for +various platforms where creating them by yourself is not easy due to various +reasons.</p> + +<p>Please note that we did not create these binaries, nor do we +support them. If you have any problems installing them, please +contact their makers.</p> + +<ul> +<li><a href="http://www-frec.bull.com/docs/download.htm">AIX</a> + +<li>DOS: <a href="http://www.delorie.com/djgpp/">DJGPP</a> + +<li><a href="http://hpux.cae.wisc.edu/">HP-UX Porting Center</a> + +<li><a href="http://www.sco.com/skunkware/devtools/index.html#gcc">SCO + OpenServer/Unixware</a> + +<li>Solaris (SPARC, Intel): <a + href="http://www.sunfreeware.com/">Sunfreeware</a> + +<li>SGI: <a href="http://freeware.sgi.com/">SGI Freeware</a> + +<li>Windows 95, 98, and NT: + <a href="http://sources.redhat.com/cygwin/">Cygwin for Windows 95, + 98, and NT</a> | + <a href="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/">GNU + Win32 related projects</a> by Mumit Khan + +<li><a href="ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/">The +Written Word</a> offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel, +IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00. + +</ul> + +<p>In addition to those specific offerings, you can get a binary +distribution CD-ROM from the <a +href="http://www.fsf.org/order/order.html">Free Software +Foundation</a>. 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.</p> + +<hr> +<p><a href="./index.html">Return to the GCC Installation page</a></p> + +</body> +</html> diff --git a/gnu/egcs/install/build.html b/gnu/egcs/install/build.html index 12da67fc7e0..c6ad5012613 100644 --- a/gnu/egcs/install/build.html +++ b/gnu/egcs/install/build.html @@ -74,7 +74,7 @@ native compiler. You can then use the native GCC compiler to build the cross compiler. <p>Assuming you have already installed a native copy of GCC and configured -your corss compiler, issue the command "make", which performs the +your cross compiler, issue the command "make", which performs the following steps: <ul> <li>Build host tools necessary to build the compiler such as texinfo, bison, @@ -95,15 +95,15 @@ following steps: <h2>Building in parallel</h2> -<p> If you have a multiprocessor you can use `<code>make bootstrap -MAKE="make -j 2" -j 2</code>' instead of just `<code>make bootstrap</code>' +<p> If you have a multiprocessor system you can use `<code>make bootstrap +MAKE="make -j 2" -j 2</code>' or just `<code>make -j 2 bootstrap</code>' +for GNU Make 3.79 and above instead of just `<code>make bootstrap</code>' when building GCC. You can use a bigger number instead of two if you like. In most cases, it won't help to use a number bigger than the number of processors in your machine. -<p> <hr> -<i>Last modified on August 27, 1999.</i> +<p><a href="./index.html">Return to the GCC Installation page</a></p> </body> </html> diff --git a/gnu/egcs/install/configure.html b/gnu/egcs/install/configure.html index f27ab3a6d67..5e133e9a52c 100644 --- a/gnu/egcs/install/configure.html +++ b/gnu/egcs/install/configure.html @@ -42,8 +42,12 @@ Otherwise the configuration scripts may fail. recommend you not provide a configure target when configuring a native compiler. - <li> <b>target</b> must be specified when configuring a cross compiler; + <li> <b>target</b> must be specified as <tt>--target=</tt><i>target</i> + when configuring a cross compiler; examples of valid targets would be i960-rtems, m68k-coff, sh-elf, etc. + + <li>Specifying just <i>target</i> instead of <tt>--target=</tt><i>target</i> + implies that the host defaults to <i>target</i>. </ul> @@ -97,11 +101,13 @@ GCC. A partial list of supported <tt>options</tt>: etc. This is the default. <li> <tt>--enable-threads</tt> -- Specify that the target supports threads. - This affects only the Objective-C compiler and runtime library. + This affects the Objective-C compiler and runtime library, and exception + handling for other languages like C++ and Java. <li> <tt>--enable-threads=</tt><i>lib</i> -- Specify that <i>lib</i> is the - thread support library. This affects only the Objective-C compiler and - runtime library. + thread support library. This affects the Objective-C compiler and + runtime library, and exception handling for other languages like C++ and + Java. <li> <tt>--with-cpu=</tt><i>cpu</i> -- Specify which cpu variant the compiler should generate code for by default. This is currently @@ -110,15 +116,18 @@ GCC. A partial list of supported <tt>options</tt>: 603e, or ultrasparc) you provide, please check the configure script for a complete list of supported models. - <li> <tt>--enable-target-optspace</tt> -- Specify that target libraries should be optimzied for code space instead of code speed. This is the default for - the m32r platform. + <li> <tt>--enable-target-optspace</tt> -- Specify that target libraries + should be optimized for code space instead of code speed. This is the + default for the m32r platform. <li> <tt>--enable-cpp</tt> -- Specify that a shell script which emulates traditional cpp functionality should be installed. - <li> <tt>--enable-cpplib</tt> -- Specify that the functionality of CPP should - be integrated into the compiler itself. This is still under development, but - may be useful in limited situations. This option is never enabled by default. + <li> <tt>--enable-cpplib</tt> -- Specify that the functionality of + CPP should be integrated into the compiler itself. This option is + not supported by snapshots since November 2000. In snapshots where + it is supported, it is not enabled by default, except for snapshots + very close to November 2000. <li> <tt>--without-fast-fixincludes</tt> -- Specify that the old, slower method of fixing the system header files should be used. @@ -132,7 +141,7 @@ GCC. A partial list of supported <tt>options</tt>: <tt>${libsubdir}/include/g++</tt> unless you overruled it by using <tt>--with-gxx-include-dir=</tt><i>dirname</i>. Using this option is particularly useful if you intend to use several - versions of egcs/gcc in parallel. This is currently supported by <tt>libf2c</tt> + versions of GCC in parallel. This is currently supported by <tt>libf2c</tt> and <tt>libstdc++</tt>. <li> <tt>--enable-languages=</tt><i>lang1</i><tt>,</tt><i>lang2</i><tt>,...</tt> @@ -144,8 +153,8 @@ GCC. A partial list of supported <tt>options</tt>: </tt><br> Currently, you can use any of the following: <tt>CHILL</tt>, <tt>c++</tt>, <tt>f77</tt>, <tt>java</tt> and <tt>objc</tt>. Please note, that this switch - does not work with EGCS 1.1.2 or older versions of egcs. It will be supported - in GCC 2.95 and newer version.<br> + does not work with EGCS 1.1.2 or older versions of egcs. It is supported + in GCC 2.95 and newer versions.<br> If you do not pass this flag, all languages available in the <tt>gcc</tt> sub-tree will be configured. Re-defining LANGUAGES when calling <tt>make bootstrap</tt> <b>*does not*</b> work anymore, as those language sub-directories might not have been @@ -158,9 +167,11 @@ GCC. A partial list of supported <tt>options</tt>: <p>Some options which only apply to building cross compilers: <ul> <li> <tt>--with-headers=</tt><i>dir</i> -- Specifies a directory which has - target include files. These include files will be copied into the gcc - install directory. Fixincludes will be run on these files to make them - compatible with gcc. + target include files. + <em>This options is required</em> when building a cross + compiler, if <tt>${prefix}/${target}/sys-include</tt> doesn't pre-exist. + These include files will be copied into the gcc install directory. + Fixincludes will be run on these files to make them compatible with gcc. <li> <tt>--with-libs=</tt><i>"dir1 dir2 ... dirN"</i> -- Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the gcc install directory. @@ -172,10 +183,8 @@ GCC. A partial list of supported <tt>options</tt>: <p>Note that each <tt>--enable</tt> option has a corresponding <tt>--disable</tt> option and that each <tt>--with</tt> option has a corresponding <tt>--without</tt> option. - -<p> <hr> -<i>Last modified on July 16, 1999.</i> +<p><a href="./index.html">Return to the GCC Installation page</a></p> </body> </html> diff --git a/gnu/egcs/install/download.html b/gnu/egcs/install/download.html index a3ed652bb5f..ff96cf06007 100644 --- a/gnu/egcs/install/download.html +++ b/gnu/egcs/install/download.html @@ -2,37 +2,41 @@ <head> <title>Downloading GCC</title> </head> + <body> <h1 align="center">Downloading GCC</h1> -<p>GCC is distributed via FTP tarballs compressed with gzip or bzip2. It is -possible to download a full distribution or specific components. +<p>GCC is distributed via CVS and FTP tarballs compressed with gzip or +bzip2. It is possible to download a full distribution or specific +components.</p> + +<p>Please refer to our <a href="http://gcc.gnu.org/releases.html">releases +web page</a> for information on how to obtain GCC.</p> <p>The full distribution includes the C, C++, Objective-C, Fortran, Java, and Chill compilers. The full distribution also includes runtime libraries for C++, Objective-C and Fortran. In the future the GNU compiler testsuites -will be included in the full distribution. +will be included in the full distribution.</p> <p>If you choose to download specific components, you must download the core gcc distribution plus any language specific distributions you wish to use. The core distribution includes the C language front-end as well as the -shared componenets. Each language has a tarball which includes the language -front-end as well as the language runtime (when appropriate). +shared components. Each language has a tarball which includes the language +front-end as well as the language runtime (when appropriate).</p> -<p>Unpack the core distribution as well as any language specific distributions -in the same directory. +<p>Unpack the core distribution as well as any language specific +distributions in the same directory.</p> -<p>XXX FSF mirror sites -<p><a href="ftp://egcs.cygnus.com/pub/egcs/releases/index.html"> -FTP download from egcs.cygnus.com (USA California)</a> -<p><a href="ftp://go.cygnus.com/pub/sourceware.cygnus.com/pub/egcs/releases/index.html"> -FTP download from go.cygnus.com (USA California -- High speed link -provided by Stanford)</a> -<p>GCC releases are available on many <a href="../mirrors.html">FTP mirror sites</a>. If possible, please use one of these. +<P>If you also intend to build binutils (either to upgrade an existing +installation or for use in place of the corresponding tools of your +OS), unpack the binutils distribution either in the same directory or +a separate one. In the latter case, add symbolic links to any +components of the binutils you intend to build alongside the compiler +(bfd, binutils, gas, gprof, ld, opcodes,...) to the directory containing +the GCC sources.</p> -<p> <hr> -<i>Last modified on July 16, 1999.</i> +<p><a href="./index.html">Return to the GCC Installation page</a></p> </body> </html> diff --git a/gnu/egcs/install/finalinstall.html b/gnu/egcs/install/finalinstall.html index 5c11a503213..6b30b430e3f 100644 --- a/gnu/egcs/install/finalinstall.html +++ b/gnu/egcs/install/finalinstall.html @@ -9,29 +9,27 @@ `<code>cd <i>objdir</i>; make install</code>' for a native compiler or `<code>cd <i>objdir</i>; make install LANGUAGES="c c++"</code>' for a cross compiler (note installing cross compilers will be easier in the -next release!). - +next release!).</p> <p>That step completes the installation of GCC; user level binaries can be found in <i>prefix</i>/bin where <i>prefix</i> is the value you specified -with the --prefix to configure (or /usr/local by default). +with the --prefix to configure (or /usr/local by default).</p> <p>If you don't mind, please quickly review the <a -href="http://egcs.cygnus.com/gcc-2.95/buildstat.html">build status page</a>. +href="http://gcc.gnu.org/gcc-2.95/buildstat.html">build status page</a>. If your system is not listed, send a note to <a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating -that you successfully built and installed GCC. +that you successfully built and installed GCC.</p> -Include the output from running <i>srcdir</i>/config.guess. (Do not +<p>Include the output from running <i>srcdir</i>/config.guess. (Do not send us the config.guess file itself, just the output from running -it!) +it!)</p> <p>If you find a bug, please report it following our <a -href="../faq.html#bugreport">bug reporting guidlines</a>. +href="../bugs.html">bug reporting guidelines</a>.</p> -<p> <hr> -<i>Last modified on July 16, 1999.</i> +<p><a href="./index.html">Return to the GCC Installation page</a></p> </body> </html> diff --git a/gnu/egcs/install/glibc-2.2.patch b/gnu/egcs/install/glibc-2.2.patch new file mode 100644 index 00000000000..e63af193783 --- /dev/null +++ b/gnu/egcs/install/glibc-2.2.patch @@ -0,0 +1,282 @@ +2000-10-11 Jakub Jelinek <jakub@redhat.com> + + * iostream.cc (ostream::operator<<(double n)) [__GLIBC_MINOR__ >= 2]: + Initialize new fields wide and i18n of struct printf_info. + (ostream::operator<<(long double n)) [__GLIBC_MINOR__ >= 2]: + Likewise. + +2000-09-23 Franz Sirl <Franz.Sirl-kernel@lauterbach.com> + + * stdstreams.cc: Include <libio.h>, not "libio.h". + * iolibio.h: Likewise. + (_IO_pos_BAD): Use _IO_off_t instead of _IO_fpos_t. + * libio.h (_IO_USER_LOCK): Define. + +1999-12-13 Jakub Jelinek <jakub@redhat.com> + + * libio.h (_IO_cookie_io_functions_t): Use _IO_off_t instead of + _IO_fpos_t. + (_IO_seekoff, _IO_seekpos): Likewise. Use _IO_off64_t instead of + _IO_fpos64_t. + * libioP.h (_IO_seekoff_t, _IO_seekpos_t, _IO_seek_t): Likewise. + (_IO_seekoff, _IO_seekpos): Likewise. + (_IO_default_seekoff, _IO_default_seekpos): Likewise. + (_IO_default_seek): Likewise. + (_IO_file_seekoff, _IO_file_seek, _IO_str_seekoff): Likewise. + * streambuf.h (streampos): Typedef to _IO_off_t resp. _IO_off64_t. + * parsestream.h (class parsebuf::pos_at_line_start): Change type + to _IO_off_t. + +--- gcc-2.95.2/libio/libio.h.jj Mon Jun 29 20:06:26 1998 ++++ gcc-2.95.2/libio/libio.h Thu Nov 2 17:33:00 2000 +@@ -136,6 +136,7 @@ + #define _IO_IS_APPENDING 0x1000 + #define _IO_IS_FILEBUF 0x2000 + #define _IO_BAD_SEEN 0x4000 ++#define _IO_USER_LOCK 0x8000 + + /* These are "formatting flags" matching the iostream fmtflags enum values. */ + #define _IO_SKIPWS 01 +@@ -277,7 +278,7 @@ typedef struct + { + _IO_ssize_t (*read) __PMT ((struct _IO_FILE *, void *, _IO_ssize_t)); + _IO_ssize_t (*write) __PMT ((struct _IO_FILE *, const void *, _IO_ssize_t)); +- _IO_fpos_t (*seek) __PMT ((struct _IO_FILE *, _IO_off_t, int)); ++ _IO_off_t (*seek) __PMT ((struct _IO_FILE *, _IO_off_t, int)); + int (*close) __PMT ((struct _IO_FILE *)); + } _IO_cookie_io_functions_t; + +@@ -348,11 +349,11 @@ extern _IO_ssize_t _IO_padn __P ((_IO_FI + extern _IO_size_t _IO_sgetn __P ((_IO_FILE *, void *, _IO_size_t)); + + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +-extern _IO_fpos64_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos64_t, int)); ++extern _IO_off64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); ++extern _IO_off64_t _IO_seekpos __P ((_IO_FILE *, _IO_off64_t, int)); + #else +-extern _IO_fpos_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +-extern _IO_fpos_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); ++extern _IO_off_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); ++extern _IO_off_t _IO_seekpos __P ((_IO_FILE *, _IO_off_t, int)); + #endif + + extern void _IO_free_backup_area __P ((_IO_FILE *)); +--- gcc-2.95.2/libio/libioP.h.jj Tue May 18 00:58:56 1999 ++++ gcc-2.95.2/libio/libioP.h Tue Oct 10 11:40:57 2000 +@@ -146,10 +146,10 @@ typedef _IO_size_t (*_IO_xsgetn_t) __PMT + It matches the streambuf::seekoff virtual function. + It is also used for the ANSI fseek function. */ + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-typedef _IO_fpos64_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off64_t OFF, ++typedef _IO_off64_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off64_t OFF, + int DIR, int MODE)); + #else +-typedef _IO_fpos_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off_t OFF, ++typedef _IO_off_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off_t OFF, + int DIR, int MODE)); + #endif + #define _IO_SEEKOFF(FP, OFF, DIR, MODE) JUMP3 (__seekoff, FP, OFF, DIR, MODE) +@@ -160,9 +160,9 @@ typedef _IO_fpos_t (*_IO_seekoff_t) __PM + It is also used for the ANSI fgetpos and fsetpos functions. */ + /* The _IO_seek_cur and _IO_seek_end options are not allowed. */ + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-typedef _IO_fpos64_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_fpos64_t, int)); ++typedef _IO_off64_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); + #else +-typedef _IO_fpos_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_fpos_t, int)); ++typedef _IO_off_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_off_t, int)); + #endif + #define _IO_SEEKPOS(FP, POS, FLAGS) JUMP2 (__seekpos, FP, POS, FLAGS) + +@@ -213,9 +213,9 @@ typedef _IO_ssize_t (*_IO_write_t) __PMT + It matches the streambuf::sys_seek virtual function, which is + specific to this implementation. */ + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-typedef _IO_fpos64_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); ++typedef _IO_off64_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); + #else +-typedef _IO_fpos_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off_t, int)); ++typedef _IO_off_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off_t, int)); + #endif + #define _IO_SYSSEEK(FP, OFFSET, MODE) JUMP2 (__seek, FP, OFFSET, MODE) + +@@ -298,11 +298,11 @@ struct _IO_FILE_plus + /* Generic functions */ + + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +-extern _IO_fpos64_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos64_t, int)); ++extern _IO_off64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); ++extern _IO_off64_t _IO_seekpos __P ((_IO_FILE *, _IO_off64_t, int)); + #else +-extern _IO_fpos_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +-extern _IO_fpos_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); ++extern _IO_off_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); ++extern _IO_off_t _IO_seekpos __P ((_IO_FILE *, _IO_off_t, int)); + #endif + + extern void _IO_switch_to_main_get_area __P ((_IO_FILE *)); +@@ -340,22 +340,22 @@ extern _IO_size_t _IO_default_xsputn __P + _IO_size_t)); + extern _IO_size_t _IO_default_xsgetn __P ((_IO_FILE *, void *, _IO_size_t)); + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_default_seekoff __P ((_IO_FILE *, ++extern _IO_off64_t _IO_default_seekoff __P ((_IO_FILE *, + _IO_off64_t, int, int)); +-extern _IO_fpos64_t _IO_default_seekpos __P ((_IO_FILE *, +- _IO_fpos64_t, int)); ++extern _IO_off64_t _IO_default_seekpos __P ((_IO_FILE *, ++ _IO_off64_t, int)); + #else +-extern _IO_fpos_t _IO_default_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +-extern _IO_fpos_t _IO_default_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); ++extern _IO_off_t _IO_default_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); ++extern _IO_off_t _IO_default_seekpos __P ((_IO_FILE *, _IO_off_t, int)); + #endif + extern _IO_ssize_t _IO_default_write __P ((_IO_FILE *, const void *, + _IO_ssize_t)); + extern _IO_ssize_t _IO_default_read __P ((_IO_FILE *, void *, _IO_ssize_t)); + extern int _IO_default_stat __P ((_IO_FILE *, void *)); + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_default_seek __P ((_IO_FILE *, _IO_off64_t, int)); ++extern _IO_off64_t _IO_default_seek __P ((_IO_FILE *, _IO_off64_t, int)); + #else +-extern _IO_fpos_t _IO_default_seek __P ((_IO_FILE *, _IO_off_t, int)); ++extern _IO_off_t _IO_default_seek __P ((_IO_FILE *, _IO_off_t, int)); + #endif + extern int _IO_default_sync __P ((_IO_FILE *)); + #define _IO_default_close ((_IO_close_t) _IO_default_sync) +@@ -389,11 +389,11 @@ extern void _IO_flush_all_linebuffered _ + extern int _IO_file_doallocate __P ((_IO_FILE *)); + extern _IO_FILE* _IO_file_setbuf __P ((_IO_FILE *, char *, _IO_ssize_t)); + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +-extern _IO_fpos64_t _IO_file_seek __P ((_IO_FILE *, _IO_off64_t, int)); ++extern _IO_off64_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); ++extern _IO_off64_t _IO_file_seek __P ((_IO_FILE *, _IO_off64_t, int)); + #else +-extern _IO_fpos_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +-extern _IO_fpos_t _IO_file_seek __P ((_IO_FILE *, _IO_off_t, int)); ++extern _IO_off_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); ++extern _IO_off_t _IO_file_seek __P ((_IO_FILE *, _IO_off_t, int)); + #endif + extern _IO_size_t _IO_file_xsputn __P ((_IO_FILE *, const void *, _IO_size_t)); + extern int _IO_file_stat __P ((_IO_FILE *, void *)); +@@ -427,9 +427,9 @@ extern int _IO_str_underflow __P ((_IO_F + extern int _IO_str_overflow __P ((_IO_FILE *, int)); + extern int _IO_str_pbackfail __P ((_IO_FILE *, int)); + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-extern _IO_fpos64_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); ++extern _IO_off64_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); + #else +-extern _IO_fpos_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); ++extern _IO_off_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); + #endif + extern void _IO_str_finish __P ((_IO_FILE *, int)); + +@@ -544,12 +544,12 @@ extern int _IO_vscanf __P ((const char * + where an _IO_fpos_t is a struct. + Note that _IO_off_t must be an integral type. */ + +-/* _IO_pos_BAD is an _IO_fpos_t value indicating error, unknown, or EOF. */ ++/* _IO_pos_BAD is an _IO_off_t value indicating error, unknown, or EOF. */ + #ifndef _IO_pos_BAD + # if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +-# define _IO_pos_BAD ((_IO_fpos64_t) -1) ++# define _IO_pos_BAD ((_IO_off64_t) -1) + # else +-# define _IO_pos_BAD ((_IO_fpos_t) -1) ++# define _IO_pos_BAD ((_IO_off_t) -1) + # endif + #endif + /* _IO_pos_as_off converts an _IO_fpos_t value to an _IO_off_t value. */ +--- gcc-2.95.2/libio/streambuf.h.jj Mon Aug 9 02:07:01 1999 ++++ gcc-2.95.2/libio/streambuf.h Tue Oct 10 11:40:57 2000 +@@ -72,10 +72,10 @@ class ostream; class streambuf; + + #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 + typedef _IO_off64_t streamoff; +-typedef _IO_fpos64_t streampos; ++typedef _IO_off64_t streampos; + #else + typedef _IO_off_t streamoff; +-typedef _IO_fpos_t streampos; ++typedef _IO_off_t streampos; + #endif + typedef _IO_ssize_t streamsize; + +--- gcc-2.95.2/libio/parsestream.h.jj Fri Aug 22 00:58:20 1997 ++++ gcc-2.95.2/libio/parsestream.h Tue Oct 10 11:40:57 2000 +@@ -42,7 +42,7 @@ extern "C++" { + + class parsebuf : public streambuf { + protected: +- _IO_fpos_t pos_at_line_start; ++ _IO_off_t pos_at_line_start; + long _line_length; + unsigned long __line_number; + char *buf_start; +--- gcc-2.95.2/libio/iostream.cc.jj Sat Aug 7 08:01:46 1999 ++++ gcc-2.95.2/libio/iostream.cc Thu Nov 2 17:33:00 2000 +@@ -1,5 +1,5 @@ + /* This is part of libio/iostream, providing -*- C++ -*- input/output. +- Copyright (C) 1993, 1997 Free Software Foundation, Inc. ++ Copyright (C) 1993, 1997, 2000 Free Software Foundation, Inc. + + This file is part of the GNU IO Library. This library is free + software; you can redistribute it and/or modify it under the +@@ -687,6 +687,10 @@ ostream& ostream::operator<<(double n) + /* extra: */ 0, + #if __GLIBC_MINOR__ >= 1 + /* is_char: */ 0, ++#if __GLIBC_MINOR__ >= 2 ++ /* wide: */ 0, ++ /* i18n: */ 0, ++#endif + #endif + #endif + /* pad: */ fill() +@@ -793,6 +797,10 @@ ostream& ostream::operator<<(long double + /* extra: */ 0, + #if __GLIBC_MINOR__ >= 1 + /* is_char: */ 0, ++#if __GLIBC_MINOR__ >= 2 ++ /* wide: */ 0, ++ /* i18n: */ 0, ++#endif + #endif + #endif + /* pad: */ fill() +--- gcc-2.95.2/libio/iolibio.h.jj Tue Feb 24 21:09:50 1998 ++++ gcc-2.95.2/libio/iolibio.h Thu Nov 2 17:33:00 2000 +@@ -1,4 +1,4 @@ +-#include "libio.h" ++#include <libio.h> + + /* These emulate stdio functionality, but with a different name + (_IO_ungetc instead of ungetc), and using _IO_FILE instead of FILE. */ +@@ -38,7 +38,11 @@ extern int _IO_obstack_vprintf __P ((str + _IO_va_list)); + extern int _IO_obstack_printf __P ((struct obstack *, const char *, ...)); + #ifndef _IO_pos_BAD +-#define _IO_pos_BAD ((_IO_fpos_t)(-1)) ++# if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 ++# define _IO_pos_BAD ((_IO_off64_t) -1) ++# else ++# define _IO_pos_BAD ((_IO_off_t) -1) ++# endif + #endif + #define _IO_clearerr(FP) ((FP)->_flags &= ~(_IO_ERR_SEEN|_IO_EOF_SEEN)) + #define _IO_fseek(__fp, __offset, __whence) \ +--- gcc-2.95.2/libio/stdstreams.cc.jj Fri Aug 22 00:58:21 1997 ++++ gcc-2.95.2/libio/stdstreams.cc Thu Nov 2 17:33:00 2000 +@@ -36,7 +36,7 @@ the executable file might be covered by + // then we don't need to, since in that case stdin/stdout/stderr + // are identical to _IO_stdin/_IO_stdout/_IO_stderr. + +-#include "libio.h" ++#include <libio.h> + + #ifdef _STDIO_USES_IOSTREAM + #define CIN_SBUF _IO_stdin_ diff --git a/gnu/egcs/install/index.html b/gnu/egcs/install/index.html index 981ec480695..b5ed29ed28f 100644 --- a/gnu/egcs/install/index.html +++ b/gnu/egcs/install/index.html @@ -6,45 +6,40 @@ <h1 align="center">Installing GCC</h1> <p>The latest version of this document is always available at <a href=" -http://egcs.cygnus.com/install/">http://egcs.cygnus.com/install/</a>. +http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>. <p>This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. <p>GCC includes several components that previously were separate distributions -with their own installation instructions. This document supercedes all +with their own installation instructions. This document supersedes all package specific installation instructions. We provide the component specific installation information in the source distribution for historical reference purposes only. -<p>We recommend you read the entire generic installation instructions as -well as any target specific installation instructions before you proceed -to configure, build, test and install GCC. - -<p>If something goes wrong in the configure, build, test or install -procedures, first double check that you followed the generic and target -specific installation instructions carefully. Then check the -<a href="../faq.html">FAQ</a> to see if your problem is covered before you file -a bug report. - -<p><em>Before</em> starting the build/install procedure <em>please</em> browse +<p><em>Before</em> starting the build/install procedure please check the <a href="specific.html">host/target specific installation notes</a>. +We recommend you browse the entire generic installation instructions +before you proceed.</p> -<p>The installation procedure is broken into five steps. - -<ul> +<p>The installation procedure itself is broken into five steps. - <li> <a href="download.html">downloading the source</a> - <li> <a href="configure.html">configure</a> - <li> <a href="build.html">build</a> - <li> <a href="test.html">test</a> (optional) - <li> <a href="finalinstall.html">install</a> +<ol> + <li><a href="download.html">Downloading the source</a></li> + <li><a href="configure.html">Configuration</a></li> + <li><a href="build.html">Building</a></li> + <li><a href="test.html">Testing</a> (optional)</li> + <li><a href="finalinstall.html">Final install</a></li> +</ol> -</ul> +<p>Please note that GCC does not support <CODE>`make uninstall`</CODE> +and probably won't do so in the near future as this would open a can +of worms. Instead, we suggest that you install GCC into a directory of +its own and simply remove that directory when you do not need that +specific version of GCC any longer. <hr> -<a href="../index.html">Return to the GCC home page</a> -<hr> -<i>Last modified on July 15, 1999.</i> +<p><a href="./index.html">Return to the GCC Installation page</a></p> + </body> </html> diff --git a/gnu/egcs/install/specific.html b/gnu/egcs/install/specific.html index f2a21f54ecd..b116cbfc3b1 100644 --- a/gnu/egcs/install/specific.html +++ b/gnu/egcs/install/specific.html @@ -6,17 +6,21 @@ <h1 align="center">Host/Target specific installation notes for GCC</h1> -<p>Please read this document carefully <i>before</i> installing the GNU Compiler Collection on your machine.</p> +<p>Please read this document carefully <i>before</i> installing the +GNU Compiler Collection on your machine.</p> <ul> <li><a href="#alpha*-dec-linux*">alpha*-dec-linux*</a></li> <li><a href="#alpha*-dec-osf*">alpha*-dec-osf*</a></li> - <li><a href="#dos">GCC with DOS</a></li> + <li><a href="#dos">DOS</a></li> <li><a href="#hppa*-hp-hpux*">hppa*-hp-hpux*</a></li> <li><a href="#hppa*-hp-hpux9">hppa*-hp-hpux9</a></li> <li><a href="#hppa*-hp-hpux10">hppa*-hp-hpux10</a></li> + <li><a href="#hppa*-hp-hpux11">hppa*-hp-hpux11</a></li> + <li><a href="#*-*-linux-gnu">*-*-linux-gnu</a></li> <li><a href="#ix86-*-linux*">i?86-*-linux*</a></li> <li><a href="#ix86-*-sco3.2v5*">i?86-*-sco3.2v5*</a></li> + <li><a href="#ix86-*-solaris*">i?86-*-solaris*</a></li> <li><a href="#ix86-*-udk">i?86-*-udk</a></li> <li><a href="#*-ibm-aix*">*-ibm-aix*</a></li> <li><a href="#m68k-*-nextstep*">m68k-*-nextstep*</a></li> @@ -31,7 +35,8 @@ <li><a href="#sparc-sun-sunos*">sparc-sun-sunos*</a></li> <li><a href="#sparc-unknown-linux-gnulibc1">sparc-unknown-linux-gnulibc1</a></li> <li><a href="#sparc64-*-*">sparc64-*-*</a></li> - <li><a href="#win+os2">GCC with Windows or OS/2</a></li> + <li><a href="#windows">Microsoft Windows</a></li> + <li><a href="#os2">OS/2</a></li> </ul> <ul> @@ -45,42 +50,13 @@ <hr> <h3><a name="alpha*-dec-linux*">alpha*-dec-linux*</a></h3> -<p>GNU/Linux Alpha EV56 or PCA56 hosts running Red Hat 4.2 or 5.0 may -see errors of this sort:</p> -<pre> - Error: Unknown pseudo-op: `.arch' -</pre> -<p>This is a signal that a new assembler is needed if you want to generate BWX insns for your machine.</p> - -<p>The version of GCC shipped with Red Hat 4.2 (2.7.0.2) has a fault wherein -it will silently generate incorrect code. The version shipped with -Red Hat 5.0 (2.8.0.1) is not broken, but required an extra -m21164a -argument on the command-line. In order to visibly trap 2.7.0.2, -I now issue DEC's .arch pseudo into the assembly. Relieving the -problem of mucking with command-line arguments for 2.8.0.1 is a -pleasant side effect.</p> - -<p>If you've got Red Hat 5.0 installed, you may grab binutils 2.9.1 -and be happy. If you've got Red Hat 4.2, bugs make it much harder -to upgrade pieces on your own, and you are better off upgrading -the entire system.</p> - -<p>In either case, your problem may be bypassed by not emitting BWX -code by default. Do this by using</p> -<pre> - configure alphaev5-unknown-linux-gnulibc1 -</pre> -<p>if you have RH 4.2, or</p> -<pre> - configure alphaev5-unknown-linux-gnu -</pre> -<p>if you have RH 5.0.</p> +<p>We strongly recommend to upgrade to binutils 2.10 (or newer).</p> <p>The following error:</p> <pre> Error: macro requires $at register while noat in effect </pre> -<p>also indicates that you should upgrade to a newer version of +<p>indicates that you should upgrade to a newer version of the assembler, 2.9 or later. If you can not upgrade the assembler, the compiler option "-Wa,-m21164a" may work around this problem.</p> @@ -99,7 +75,7 @@ to remove the shared libstdc++.</p> <p>An alternative solution is to arrange that all symbols from <code>libgcc</code> get copied to the shared <code>libstdc++</code>; see detailed solution below. (Surprising as it may seem, this does -indeed fix the problem!) <b>Beware</b> that this may bring you +indeed fix the problem!) <em>Beware</em> that this may bring you binary-compatibility problems in the future, if you don't use the same work-around next time you build <code>libstdc++</code>: if programs start to depend on <code>libstdc++</code> to provide symbols that used @@ -109,7 +85,7 @@ will have to be relinked.</p> <p>The magic spell is to add <code>-Wl,-all,-lgcc,-none</code> to the definition of macro <code>SHDEPS</code> in -<code>libstdc++/config/dec-osf.ml</code> <b>before</b> +<code>libstdc++/config/dec-osf.ml</code> <em>before</em> <code>alpha*-dec-osf*/libstdc++/Makefile</code> is created (a <a href="dec-osf-shlibstdc++.patch">patch</a> that does just that is available). If the Makefile already exists, run @@ -129,22 +105,26 @@ flag <code>-mieee</code>.</p> <hr> -<h3><a name="dos">GCC with DOS</h3> +<h3><a name="dos">DOS</a></h3> -<p>A binary distribution is available at <a -href="ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/">Simtel.Net</A> and its -mirrors.</p> +<p>Please have a look at our <a href="binaries.html">binaries page</a>.</p> <hr> <h3><a name="hppa*-hp-hpux*">hppa*-hp-hpux*</a></h3> -<p>We <b>highly</b> recommend using gas/binutils-2.8 or newer on all hppa +<p>We <em>highly</em> recommend using gas/binutils-2.8 or newer on all hppa platforms; you may encounter a variety of problems when using the HP assembler.</p> -<p>If you wish to use pa-risc 2.0 architecture support, you must use either the -HP assembler or a recent -<a href="ftp://sourceware.cygnus.com/pub/binutils/snapshots">snapshot of gas</a>.</p> +<p>Specifically, <code>-g</code> 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 and configure GCC with the <code>--with-gnu-as</code> +option.</p> + +<p>If you wish to use pa-risc 2.0 architecture support, you must use either +the HP assembler or a recent +<a href="ftp://sources.redhat.com/pub/binutils/snapshots">snapshot of +gas</a>.</p> <p>More specific information to hppa*-hp-hpux* targets follows.</p> @@ -165,8 +145,8 @@ shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to <hr> <h3><a name="hppa*-hp-hpux10">hppa*-hp-hpux10</a></h3> -<p>For hpux10.20, we <b>highly</b> recommend you pick up the latest sed -patch <code>PHCO_15468</code> from HP. HP has two sites which provide patches free of charge:</p> +<p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed +patch <code>PHCO_19798</code> from HP. HP has two sites which provide patches free of charge:</p> <ul> <li><a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and Latin-America</a></li> @@ -182,7 +162,24 @@ bootstrap</code>'.</p> <hr> +<h3><a name="hppa*-hp-hpux11">hppa*-hp-hpux11</a></h3> + +<p>GCC 2.95.2 does not support HP-UX 11, and it cannot generate 64-bit +object files. Current (as of late 2000) snapshots and GCC 3.0 do support +HP-UX 11.</p> + + +<hr> +<h3><a name="*-*-linux-gnu">*-*-linux-gnu</a></h3> + +<p>If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install +out-of-the-box. You'll get compile errors while building libstdc++. +The patch <a href="glibc-2.2.patch">glibc-2.2.patch</a>, that is to be +applied in the GCC source tree, fixes the compatibility problems.</p> + +<hr> <h3><a name="ix86-*-linux*">i?86-*-linux*</a></h3> + <p>You will need binutils-2.9.1.0.15 or newer for exception handling to work.</p> <p>If you receive Signal 11 errors when building on GNU/Linux, then it is @@ -210,15 +207,16 @@ building affected files with that flag or by using the GNU assembler. Users of GNU assembler should see the note below for hazards on doing so.</p> <p>If you choose to configure with <code>--enable-shared</code> you should also -specificy <code>--with-gnu-as --disable-multilib</code> even if you are not +specify <code>--with-gnu-as --disable-multilib</code> even if you are not using the GNU assembler. In doing so you will give up the ability to generate COFF executables as described below. This combination of flags is necessary to suppress negative interactions with multilibing.</p> <p>The native SCO assembler that is provided with the OS at no charge is normally required. If, however, you must be able to use the GNU -assembler you may configure this package using the flags <code>--with-gnu-as</code>. -You must use a recent version of GNU binutils; version 2.9.1 seems to work well. +assembler (perhaps you're compiling code with asms that require GAS syntax) +you may configure this package using the flags <code>--with-gnu-as</code>. +You must use a recent version of GNU binutils; versions past 2.9.1 seems to work well. If you select this option, you will be unable to reliably build COFF images. In general, the <code>--with-gnu-as</code> option isn't as well tested as the native assembler.</p> @@ -243,7 +241,7 @@ ftp://ftp.sco.com/Supplements/rs505a/</a> and <a href="ftp://ftp.sco.com/SLS/"> OSS499A</a>.</p> <p>The dynamic linker in OpenServer 5.0.5 (earlier versions may show -the same problem) aborts on certain g77-compiled programs. It's particluarly +the same problem) aborts on certain g77-compiled programs. It's particularly likely to be triggered by building Fortran code with the <code>-fPIC</code> flag. Although it's conceivable that the error could be triggered by other @@ -259,6 +257,16 @@ and will hopefully be addressed in later releases.</p> <hr> +<h3><a name="ix86-*-solaris*">i?86-*-solaris*</a></h3> + +<p>GCC 2.95.2, when configured to use the GNU assembler, would invoke +it with the <code>-s</code> switch, that GNU as up to 2.9.5.0.12 does +not support. If you'd rather not use a newer GNU as nor the native +assembler, you'll need the patch <a +href="x86-sol2-gas.patch"><code>`x86-sol2-gas.patch'</code></a>.</p> + + +<hr> <h3><a name="ix86-*-udk">i?86-*-udk</a></h3> <p>This target emulates the SCO Universal Development Kit and requires that @@ -278,7 +286,7 @@ from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this:</p> <pre> - CC=/udk/usr/ccs/bin/cc <i>/your/path/to/</i>gcc/configure --host=i686-pc-udk --target=i686-pc-udk --exec-prefix=udk- + CC=/udk/usr/ccs/bin/cc <i>/your/path/to/</i>gcc/configure --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk- </pre> <p><i>You should substitute 'i686' in the above command with the appropriate processor for your host.</i></p> @@ -330,14 +338,16 @@ using the original "small format". A correct version of the routines is shipped with AIX 4.3.2.</p> <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object -files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUPUT FROM COMPILER FAILS +files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its <a href="http://service.boulder.ibm.com/">service.boulder.ibm.com</a> website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.</p> <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for -APAR IX87327 will be available from IBM Customer Support.</p> +APAR IX87327 is available from IBM Customer Support and from its +<a href="http://service.boulder.ibm.com/">service.boulder.ibm.com</a> +website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.</p> <hr> @@ -365,7 +375,8 @@ replacement that does can be obtained at <p>If you try to build the integrated C++ & C++ runtime libraries on this system you will run into trouble with include files. The way to get around this is to use the following sequence. Note you must have write permission to -the directory <i>prefix</i> you secified in the configuration preocess of GCC for this sequence to work.</p> +the directory <i>prefix</i> you specified in the configuration process of GCC +for this sequence to work.</p> <pre> cd bld-gcc make all-texinfo all-bison all-byacc all-binutils all-gas all-ld @@ -415,21 +426,43 @@ IRIX 5.2. We recommend you use GNU make instead of the vendor supplied make program; however, you may have success with "smake" on IRIX 5.2 if you do not have GNU make available.</p> -<p>See <a href="http://reality.sgi.com/ariel/freeware/"> -http://reality.sgi.com/ariel/freeware</a> for more information about using GCC on IRIX platforms.</p> +<p>See <a href="http://reality.sgi.com/ariel/freeware/"> +http://reality.sgi.com/ariel/freeware</a> for more information about +using GCC on IRIX platforms.</p> <hr> <h3><a name="mips*-sgi-irix6">mips*-sgi-irix6</a></h3> -<p>You must <i>not</i> use GAS on irix6 platforms; doing so will only cause problems.</p> +<p>You must <i>not</i> use GAS on irix6 platforms; doing so will only +cause problems.</p> <p>These systems don't have ranlib, which various components in GCC need; you should be able to avoid this problem by making a dummy script called ranlib which just exits with zero status and placing it in your path.</p> +<p>If you are using Irix cc as your bootstrap compiler, you must +ensure that the N32 ABI is in use. To test this, compile a simple C +file with <CODE>cc</CODE> and then run <CODE>file</CODE> on the +resulting object file. The output should look like:</p> + +<blockquote><code> +test.o: ELF N32 MSB ... +</code></blockquote> + +If you see: +<blockquote><code> +test.o: ELF 32-bit MSB +</code></blockquote> + +<p>then your version of <CODE>cc</CODE> uses the O32 ABI default. You +should set the environment variable <CODE>CC</CODE> to 'cc -n32' +before configuring GCC.</p> + <p>GCC does not currently support generating O32 ABI binaries in the -mips-sgi-irix6 configurations. It used to be possible to create a GCC with O32 ABI only support by configuring it for the mips-sgi-irix5 target. See the link below for details.</p> +mips-sgi-irix6 configurations. It used to be possible to create a GCC +with O32 ABI only support by configuring it for the mips-sgi-irix5 +target. See the link below for details.</p> <p>GCC does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very @@ -441,13 +474,14 @@ of the register when it should be loaded into the upper 4 bytes of the register. </p> <p>GCC is consistent with itself, but not consistent with the SGI C compiler -[and the SGI supplied runtime libraries], so the only failures that can +(and the SGI supplied runtime libraries), so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. I can only recall seeing two of them: inet_ntoa, and semctl. </p> -<p>See <a href="http://reality.sgi.com/ariel/freeware/"> -http://reality.sgi.com/ariel/freeware</a> for more information about using GCC on IRIX platforms.</p> +<p>See <a href="http://reality.sgi.com/ariel/freeware/"> +http://reality.sgi.com/ariel/freeware</a> for more information about +using GCC on IRIX platforms.</p> <hr> @@ -463,16 +497,16 @@ if you initially built it with gcc-2.7.2.x.</p> <p>Starting with Solaris, Sun does not ship a C compiler any more. To bootstrap and install GCC you first have to install a pre-built -compiler, for example from <a href="http://www.sunfreeware.com/"> -http://www.sunfreeware.com</a>.</p> +compiler, see our <a href="binaries.html">binaries page</a> for +details.</p> <p>Sun as 4.X is broken in that it cannot cope with long symbol names. -A typical error message might look similiar to the following: +A typical error message might look similar to the following: <BLOCKQUOTE><CODE> /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: can't compute value of an expression involving an external symbol. </CODE></BLOCKQUOTE> -See the <a href="../faq.html#squangle">How to work around too long C++ +<p>See the <a href="../faq.html#squangle">How to work around too long C++ symbol names?</a> FAQ entry for further information.</p> <p>Sun make in all known Solaris 1 (SunOS 4) and Solaris 2 releases has a @@ -482,16 +516,22 @@ broken <i>VPATH</i> mechanism, which means you must either: <li>Always build in the source directory, <em>or:</em></li> <li><em>(For GCC 2.95.1 only)</em> apply the patches mentioned at - <a href="http://www.gnu.org/software/gcc/egcstensions.html#sun-make"> - http://www.gnu.org/software/gcc/egcstensions.html#sun-make</a>.</li> -</ul></p> + <a href="http://www.gnu.org/software/gcc/extensions.html#sun-make"> + http://www.gnu.org/software/gcc/extensions.html#sun-make</a>.</li> +</ul> <hr> <h3><a name="sparc-sun-solaris*">sparc-sun-solaris*</a></h3> -<p>binutils 2.9.1 has known bugs on this platform. We recommend to use the -vendor tools (Sun as, Sun ld) until these have been fixed.</p> +<p>binutils 2.9.1 has known bugs on this platform. We recommend to use +the vendor tools (Sun as, Sun ld) until these have been fixed. +Unfortunately, C++ shared libraries, including libstdc++, won't work +properly if assembled with Sun as: the linker will complain about +relocations in read-only sections, in the definition of virtual +tables. Some possible work-arounds: use some development release of +binutils, wait for the next stable binutils release or refrain from +creating C++ shared libraries.</p> <hr> @@ -527,14 +567,13 @@ recommend it only for people who use Sun's compilers.</p> partial fix is adequate for GCC. Revision -08 or later should fix the bug, but (as of 1999-10-06) it is still being tested.</li> </ul> -</p> <hr> <h3><a name="sunv5">Sun V5.0 Compiler Bugs</a></h3> -The Sun V5.0 compilers are known to mis-compile GCC, which in turn causes -GCC to fail its bootstrap comparison test. We expect to have a workaround -ready in time for GCC 2.95.2. +The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1, +which in turn causes GCC to fail its bootstrap comparison test. +GCC 2.95.2 has a workaround. <hr> @@ -560,22 +599,33 @@ for this platform, too.</p> <hr> <h3><a name="sparc64-*-*">sparc64-*-*</a></h3> -<p>GCC version 2.95 is not able to compile code correctly for <code>sparc64</code> targets. Users of the Linux kernel, at least, can use the <code>sparc32</code> program to start up a new shell invocation with an environment that causes <code>configure</code> to recognize (via <code>uname -a</code>) the system as <code>sparc-*-*</code> instead.</p> +<p>GCC version 2.95 is not able to compile code correctly for +<code>sparc64</code> targets. Users of the Linux kernel, at least, +can use the <code>sparc32</code> program to start up a new shell +invocation with an environment that causes <code>configure</code> to +recognize (via <code>uname -a</code>) the system as +<code>sparc-*-*</code> instead.</p> <hr> -<h3><a name="win+os2"></a>GCC with Windows or OS/2</h3> +<h3><a name="windows"></a>Microsoft Windows (32 bit)</h3> -<p>GCC does not currently support Windows, either natively or with the -cygwin32 dll. However Mumit Khan has been working on supporting Windows -with GCC. You should check out his site if you're interested in Windows -support. -<a href="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/">GNU Win32 related projects</a></p> +<p>GCC currently builds under the <a href="http://www.cygwin.com/">Cygwin +environment</a>. However you need to delete (or rename) the texinfo +directory included with the GCC sources. You will also need to configure +with the option <code>--with-included-gettext</code>.</p> + +<hr> +<h3><a name="os2"></a>OS/2</h3> <p>GCC does not currently support OS/2. However, Andrew Zabolotny has been -working on a generic os/2 port with pgcc. The current code code can be found +working on a generic OS/2 port with pgcc. The current code code can be found at <a href="http://www.goof.com/pcg/os2/">http://www.goof.com/pcg/os2/</a>.</p> +<p>An older copy of GCC 2.8.1 is included with the EMX tools available at +<a href="ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/"> +ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/</a>.</p> + <hr> <h3><a name="elf_targets">all ELF targets (SVR4, Solaris, etc.)</a></h3> @@ -587,7 +637,6 @@ will be discarded automatically.</p> <hr> <p><a href="./index.html">Return to the GCC Installation page</a></p> -<p><i>Last modified on October 17, 1999.</i></p> </body> </html> diff --git a/gnu/egcs/install/test.html b/gnu/egcs/install/test.html index 4113bb3c4d1..b1774de94fd 100644 --- a/gnu/egcs/install/test.html +++ b/gnu/egcs/install/test.html @@ -1,21 +1,134 @@ <html> + <head> -<title>Installation Instructions: Testing GCC</title> +<title>Installing GCC: Testing</title> </head> <body> -<h1 align="center">Installation Instructions: Testing GCC</h1> +<h1 align="center">Installing GCC: Testing</h1> + +<p><strong>Please note that this is only applicable to current development +versions of GCC and GCC 3.0 or later. GCC 2.95.x does not come with a +testsuite.</strong></p> + +<p>Before you install GCC, you might wish to run the testsuite. This +step is optional and may require you to download additional software.</p> + +<p>First, you must have <a href="download.html">downloaded the +testsuites</a>. The full distribution contains testsuites; only if you +downloaded the "core" compiler plus any front ends, you do not have the +testsuites.</p> + +<p>Second, you must have a new version of dejagnu on your system; +dejagnu 1.3 will not work. We have made dejagnu snapshots available at +<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure">ftp://gcc.gnu.org/pub/gcc/infrastructure</a> +until a new version of dejagnu has been released.</p> + +<p>A few targets require specific preparations:</p> + +<ul> + +<li> +In order to run the libio tests on targets which do not fully +support Unix/POSIX commands (e.g. Cgwin), the references to the dbz +directory may be deleted from libio/configure.in. +</li> + +<li> +<p>When there is difficulty resolving paths to the files init.tcl and +runtest.exp, the following environment variables should be set +appropriately, for example:</p> + +<blockquote><code> +TCL_LIBRARY = /usr/share/tcl8.0<br> +DEJAGNULIBS = /usr/share/dejagnu +</code></blockquote> + +<p>On systems such as Cygwin, these paths are required to be actual +paths, not mounts or links; presumably this is due to some lack of +portability in the dejagnu code.</p> +</li> +</ul> + +<p>Finally, you can run the testsuite (which may take a long time):</p> +<blockquote><code> +cd <i>objdir</i>; make -k check +</code></blockquote> + +<p>The testing process will try to test as many components in the GCC +distribution as possible, including the C, C++ and Fortran compilers as +well as the C++ runtime libraries.</p> + + +<h2>How can I run the test suite on selected tests?</h2> + +<p>As a first possibility to cut down the number of tests that are run it is +possible to use `<code>make check-gcc</code>` or `<code>make check-g++</code>` +in the gcc subdirectory of the object directory. To further cut down the +tests the following is possible:</p> + +<blockquote><code> + make check-gcc RUNTESTFLAGS="execute.exp <other options>" +</code></blockquote> + +<p>This will run all gcc execute tests in the testsuite.</p> + +<blockquote><code> + make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>" +</code></blockquote> + +<p>This will run the g++ "old-deja" tests in the testsuite where the filename +matches 9805*.</p> + +<p>The *.exp files are located in the testsuite directories of the GCC +source, the most important ones being compile.exp, execute.exp, dg.exp +and old-deja.exp. To get a list of the possible *.exp files, pipe the +output of `<code>make check</code>` into a file and look at the +"<code>Running ... .exp</code>" lines. + + +<h2>How to interpret test results</h2> + +<p>After the testsuite has run you'll find various *.sum and *.log +files in the testsuite subdirectories. The *.log files contain a +detailed log of the compiler invocations and the corresponding +results, the *.sum files summarize the results. These summaries list +all the tests that have been run with a corresponding status code:</p> + +<ul> +<li>PASS: the test passed as expected +<li>FAIL: the test unexpectedly failed +<li>XFAIL: the test failed as expected +<li>UNSUPPORTED: the test is not supported on this platform +<li>ERROR: the testsuite detected an error +<li>WARNING: the testsuite detected a possible problem +</ul> + +<p> It is normal for some tests to report +unexpected failures. At the current time our testing harness does not allow +fine grained control over whether or not a test is expected to fail. We expect +to fix this problem in future releases.</p> -<p>The testsuite has been temporarily removed from the gcc distributions -until the copyright status of some tests can be determined. It is hoped -that the testsuite will be included in the gcc releases again soon. -<p>Until the testsuite is included it is impossible to run the testsuite. -Sorry. +<h2>Submitting test results</h2> +<p>If you want to report the results to the GCC project, use the +<code>contrib/test_summary</code> shell script. Start it in the objdir with</p> +<blockquote><code> +<i>srcdir</i>/contrib/test_summary -p your_commentary.txt -m gcc-testresults@gcc.gnu.org |sh +</code></blockquote> -<hr> -<i>Last modified on July 15, 1999.</i> +<p>This script uses the <code>Mail</code> program to send the results, so +make sure it is in your PATH. The file your_commentary.txt is +prepended to the testsuite summary and should contain any special +remarks you have on your results or your build environment. Please +do not edit the testsuite result block or the subject line, as these +messages are automatically parsed and presented at the <a +href="http://gcc.gnu.org/testresults/">GCC testresults</a> web +page. Here you can also gather information on how specific tests +behave on different platforms and compare them with your results. A +few failing testcases are possible even on released versions and you +should look here first if you think your results are unreasonable.</p> </body> </html> diff --git a/gnu/egcs/install/x86-sol2-gas.patch b/gnu/egcs/install/x86-sol2-gas.patch new file mode 100644 index 00000000000..9a2373cf05b --- /dev/null +++ b/gnu/egcs/install/x86-sol2-gas.patch @@ -0,0 +1,70 @@ +Index: gcc/ChangeLog +from Alexandre Oliva <oliva@lsd.ic.unicamp.br> + + * config/i386/sol2gas.h: I had installed the wrong version of Sept + 22's patch in the release branch. Fixed. + * configure.in: Likewise. + * configure: Rebuilt. + Reported by Jason Beardsley <jbeardsley@origin.ea.com> + +Index: gcc/configure.in +=================================================================== +RCS file: /cvs/gcc/egcs/gcc/configure.in,v +retrieving revision 1.246.4.12 +diff -u -r1.246.4.12 configure.in +--- gcc/configure.in 1999/10/13 07:58:02 1.246.4.12 ++++ gcc/configure.in 1999/10/28 23:05:38 +@@ -1399,11 +1399,10 @@ + changequote([,])dnl + xm_file="xm-siglist.h xm-alloca.h ${xm_file}" + xm_defines="USG POSIX SMALL_ARG_MAX" ++ tm_file=i386/sol2.h + if test x$gas = xyes; then + # Only needed if gas does not support -s +- tm_file=i386/sol2gas.h +- else +- tm_file=i386/sol2.h ++ tm_file="i386/sol2gas.h ${tm_file}" + fi + tmake_file=i386/t-sol2 + extra_parts="crt1.o crti.o crtn.o gcrt1.o gmon.o crtbegin.o crtend.o" +Index: gcc/config/i386/sol2gas.h +=================================================================== +RCS file: /cvs/gcc/egcs/gcc/config/i386/sol2gas.h,v +retrieving revision 1.1.2.1 +diff -u -r1.1.2.1 sol2gas.h +--- gcc/config/i386/sol2gas.h 1999/09/22 10:44:21 1.1.2.1 ++++ gcc/config/i386/sol2gas.h 1999/10/28 23:05:38 +@@ -4,8 +4,6 @@ + Copyright (C) 1999 Free Software Foundation, Inc. + */ + +-#ifndef GAS_DOES_NOT_SUPPORT_MINUS_S +-#define GAS_DOES_NOT_SUPPORT_MINUS_S 1 ++#ifndef GAS_REJECTS_MINUS_S ++#define GAS_REJECTS_MINUS_S 1 + #endif +- +-#include "i386/sol2.h" +Index: gcc/configure +=================================================================== +RCS file: /cvs/gcc/egcs/gcc/configure,v +retrieving revision 1.242.4.12 +diff -u -r1.242.4.12 configure +--- gcc/configure 1999/10/13 07:58:02 1.242.4.12 ++++ gcc/configure 1999/10/28 23:10:32 +@@ -3750,11 +3750,11 @@ + i[34567]86-*-solaris2*) + xm_file="xm-siglist.h xm-alloca.h ${xm_file}" + xm_defines="USG POSIX SMALL_ARG_MAX" ++ tm_file=i386/sol2.h + if test x$gas = xyes; then + # Only needed if gas does not support -s +- tm_file=i386/sol2gas.h +- else +- tm_file=i386/sol2.h ++ tm_file="i386/sol2gas.h ${tm_file}" ++ # + fi + tmake_file=i386/t-sol2 + extra_parts="crt1.o crti.o crtn.o gcrt1.o gmon.o crtbegin.o crtend.o" diff --git a/gnu/egcs/libio/ChangeLog b/gnu/egcs/libio/ChangeLog index d78e5056a4e..ead89e4b1ea 100644 --- a/gnu/egcs/libio/ChangeLog +++ b/gnu/egcs/libio/ChangeLog @@ -1,3 +1,31 @@ +2000-12-10 Bernd Schmidt <bernds@redhat.com> + + 2000-10-16 Jakub Jelinek <jakub@redhat.com> + * iostream.cc (ostream::operator<<(double n)) [__GLIBC_MINOR__ >= 2]: + Initialize new fields wide and i18n of struct printf_info. + (ostream::operator<<(long double n)) [__GLIBC_MINOR__ >= 2]: + Likewise. + + 2000-09-23 Franz Sirl <Franz.Sirl-kernel@lauterbach.com> + * stdstreams.cc: Include <libio.h>, not "libio.h". + * iolibio.h: Likewise. + (_IO_pos_BAD): Use _IO_off_t instead of _IO_fpos_t. + * libio.h (_IO_USER_LOCK): Define. + + 1999-12-22 Jakub Jelinek <jakub@redhat.com> + * libio.h (_IO_cookie_io_functions_t): Use _IO_off_t instead of + _IO_fpos_t. + (_IO_seekoff, _IO_seekpos): Likewise. Use _IO_off64_t instead of + _IO_fpos64_t. + * libioP.h (_IO_seekoff_t, _IO_seekpos_t, _IO_seek_t): Likewise. + (_IO_seekoff, _IO_seekpos): Likewise. + (_IO_default_seekoff, _IO_default_seekpos): Likewise. + (_IO_default_seek): Likewise. + (_IO_file_seekoff, _IO_file_seek, _IO_str_seekoff): Likewise. + * streambuf.h (streampos): Typedef to _IO_off_t resp. _IO_off64_t. + * parsestream.h (class parsebuf::pos_at_line_start): Change type + to _IO_off_t. + 2000-01-28 Martin v. Löwis <loewis@informatik.hu-berlin.de> * fstream.h (ifstream::ifstream): Add ios::in to mode. diff --git a/gnu/egcs/libio/dbz/dbzmain.c b/gnu/egcs/libio/dbz/dbzmain.c index d6b92e86486..c9e538c2076 100644 --- a/gnu/egcs/libio/dbz/dbzmain.c +++ b/gnu/egcs/libio/dbz/dbzmain.c @@ -19,7 +19,7 @@ #define STREQ(a, b) (*(a) == *(b) && strcmp((a), (b)) == 0) #ifndef lint -static char RCSid[] = "$Header: /cvs/OpenBSD/src/gnu/egcs/libio/dbz/dbzmain.c,v 1.1.1.3 2000/06/05 22:23:28 espie Exp $"; +static char RCSid[] = "$Header: /cvs/OpenBSD/src/gnu/egcs/libio/dbz/dbzmain.c,v 1.1.1.4 2001/01/29 15:26:38 espie Exp $"; #endif char *progname; diff --git a/gnu/egcs/libio/dbz/fake.c b/gnu/egcs/libio/dbz/fake.c index 9d07951f034..785e4fa5c91 100644 --- a/gnu/egcs/libio/dbz/fake.c +++ b/gnu/egcs/libio/dbz/fake.c @@ -13,7 +13,7 @@ #define STREQ(a, b) (*(a) == *(b) && strcmp((a), (b)) == 0) #ifndef lint -static char RCSid[] = "$Header: /cvs/OpenBSD/src/gnu/egcs/libio/dbz/fake.c,v 1.1.1.3 2000/06/05 22:23:29 espie Exp $"; +static char RCSid[] = "$Header: /cvs/OpenBSD/src/gnu/egcs/libio/dbz/fake.c,v 1.1.1.4 2001/01/29 15:26:38 espie Exp $"; #endif int midonly = 0; /* just message ids, rest not realistic */ diff --git a/gnu/egcs/libio/iolibio.h b/gnu/egcs/libio/iolibio.h index 083b198b448..0ebc14f7ac2 100644 --- a/gnu/egcs/libio/iolibio.h +++ b/gnu/egcs/libio/iolibio.h @@ -1,4 +1,4 @@ -#include "libio.h" +#include <libio.h> /* These emulate stdio functionality, but with a different name (_IO_ungetc instead of ungetc), and using _IO_FILE instead of FILE. */ @@ -38,7 +38,11 @@ extern int _IO_obstack_vprintf __P ((struct obstack *, const char *, _IO_va_list)); extern int _IO_obstack_printf __P ((struct obstack *, const char *, ...)); #ifndef _IO_pos_BAD -#define _IO_pos_BAD ((_IO_fpos_t)(-1)) +# if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 +# define _IO_pos_BAD ((_IO_off64_t) -1) +# else +# define _IO_pos_BAD ((_IO_off_t) -1) +# endif #endif #define _IO_clearerr(FP) ((FP)->_flags &= ~(_IO_ERR_SEEN|_IO_EOF_SEEN)) #define _IO_fseek(__fp, __offset, __whence) \ diff --git a/gnu/egcs/libio/iostream.cc b/gnu/egcs/libio/iostream.cc index 4b75fca764d..792eaae6b4c 100644 --- a/gnu/egcs/libio/iostream.cc +++ b/gnu/egcs/libio/iostream.cc @@ -1,5 +1,5 @@ /* This is part of libio/iostream, providing -*- C++ -*- input/output. - Copyright (C) 1993, 1997 Free Software Foundation, Inc. + Copyright (C) 1993, 1997, 2000 Free Software Foundation, Inc. This file is part of the GNU IO Library. This library is free software; you can redistribute it and/or modify it under the @@ -687,6 +687,10 @@ ostream& ostream::operator<<(double n) /* extra: */ 0, #if __GLIBC_MINOR__ >= 1 /* is_char: */ 0, +#if __GLIBC_MINOR__ >= 2 + /* wide: */ 0, + /* i18n: */ 0, +#endif #endif #endif /* pad: */ fill() @@ -793,6 +797,10 @@ ostream& ostream::operator<<(long double n) /* extra: */ 0, #if __GLIBC_MINOR__ >= 1 /* is_char: */ 0, +#if __GLIBC_MINOR__ >= 2 + /* wide: */ 0, + /* i18n: */ 0, +#endif #endif #endif /* pad: */ fill() diff --git a/gnu/egcs/libio/libio.h b/gnu/egcs/libio/libio.h index b152874d1f6..c453b77bf30 100644 --- a/gnu/egcs/libio/libio.h +++ b/gnu/egcs/libio/libio.h @@ -136,6 +136,7 @@ #define _IO_IS_APPENDING 0x1000 #define _IO_IS_FILEBUF 0x2000 #define _IO_BAD_SEEN 0x4000 +#define _IO_USER_LOCK 0x8000 /* These are "formatting flags" matching the iostream fmtflags enum values. */ #define _IO_SKIPWS 01 @@ -277,7 +278,7 @@ typedef struct { _IO_ssize_t (*read) __PMT ((struct _IO_FILE *, void *, _IO_ssize_t)); _IO_ssize_t (*write) __PMT ((struct _IO_FILE *, const void *, _IO_ssize_t)); - _IO_fpos_t (*seek) __PMT ((struct _IO_FILE *, _IO_off_t, int)); + _IO_off_t (*seek) __PMT ((struct _IO_FILE *, _IO_off_t, int)); int (*close) __PMT ((struct _IO_FILE *)); } _IO_cookie_io_functions_t; @@ -348,11 +349,11 @@ extern _IO_ssize_t _IO_padn __P ((_IO_FILE *, int, _IO_ssize_t)); extern _IO_size_t _IO_sgetn __P ((_IO_FILE *, void *, _IO_size_t)); #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); -extern _IO_fpos64_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos64_t, int)); +extern _IO_off64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +extern _IO_off64_t _IO_seekpos __P ((_IO_FILE *, _IO_off64_t, int)); #else -extern _IO_fpos_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); -extern _IO_fpos_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); +extern _IO_off_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +extern _IO_off_t _IO_seekpos __P ((_IO_FILE *, _IO_off_t, int)); #endif extern void _IO_free_backup_area __P ((_IO_FILE *)); diff --git a/gnu/egcs/libio/libioP.h b/gnu/egcs/libio/libioP.h index 629e4fd8cf6..be70f526bbe 100644 --- a/gnu/egcs/libio/libioP.h +++ b/gnu/egcs/libio/libioP.h @@ -146,10 +146,10 @@ typedef _IO_size_t (*_IO_xsgetn_t) __PMT ((_IO_FILE *FP, void *DATA, It matches the streambuf::seekoff virtual function. It is also used for the ANSI fseek function. */ #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -typedef _IO_fpos64_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off64_t OFF, +typedef _IO_off64_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off64_t OFF, int DIR, int MODE)); #else -typedef _IO_fpos_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off_t OFF, +typedef _IO_off_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off_t OFF, int DIR, int MODE)); #endif #define _IO_SEEKOFF(FP, OFF, DIR, MODE) JUMP3 (__seekoff, FP, OFF, DIR, MODE) @@ -160,9 +160,9 @@ typedef _IO_fpos_t (*_IO_seekoff_t) __PMT ((_IO_FILE *FP, _IO_off_t OFF, It is also used for the ANSI fgetpos and fsetpos functions. */ /* The _IO_seek_cur and _IO_seek_end options are not allowed. */ #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -typedef _IO_fpos64_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_fpos64_t, int)); +typedef _IO_off64_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); #else -typedef _IO_fpos_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_fpos_t, int)); +typedef _IO_off_t (*_IO_seekpos_t) __PMT ((_IO_FILE *, _IO_off_t, int)); #endif #define _IO_SEEKPOS(FP, POS, FLAGS) JUMP2 (__seekpos, FP, POS, FLAGS) @@ -213,9 +213,9 @@ typedef _IO_ssize_t (*_IO_write_t) __PMT ((_IO_FILE *,const void *,_IO_ssize_t)) It matches the streambuf::sys_seek virtual function, which is specific to this implementation. */ #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -typedef _IO_fpos64_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); +typedef _IO_off64_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off64_t, int)); #else -typedef _IO_fpos_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off_t, int)); +typedef _IO_off_t (*_IO_seek_t) __PMT ((_IO_FILE *, _IO_off_t, int)); #endif #define _IO_SYSSEEK(FP, OFFSET, MODE) JUMP2 (__seek, FP, OFFSET, MODE) @@ -298,11 +298,11 @@ struct _IO_FILE_plus /* Generic functions */ #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); -extern _IO_fpos64_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos64_t, int)); +extern _IO_off64_t _IO_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +extern _IO_off64_t _IO_seekpos __P ((_IO_FILE *, _IO_off64_t, int)); #else -extern _IO_fpos_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); -extern _IO_fpos_t _IO_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); +extern _IO_off_t _IO_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +extern _IO_off_t _IO_seekpos __P ((_IO_FILE *, _IO_off_t, int)); #endif extern void _IO_switch_to_main_get_area __P ((_IO_FILE *)); @@ -340,22 +340,22 @@ extern _IO_size_t _IO_default_xsputn __P ((_IO_FILE *, const void *, _IO_size_t)); extern _IO_size_t _IO_default_xsgetn __P ((_IO_FILE *, void *, _IO_size_t)); #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_default_seekoff __P ((_IO_FILE *, +extern _IO_off64_t _IO_default_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); -extern _IO_fpos64_t _IO_default_seekpos __P ((_IO_FILE *, - _IO_fpos64_t, int)); +extern _IO_off64_t _IO_default_seekpos __P ((_IO_FILE *, + _IO_off64_t, int)); #else -extern _IO_fpos_t _IO_default_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); -extern _IO_fpos_t _IO_default_seekpos __P ((_IO_FILE *, _IO_fpos_t, int)); +extern _IO_off_t _IO_default_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +extern _IO_off_t _IO_default_seekpos __P ((_IO_FILE *, _IO_off_t, int)); #endif extern _IO_ssize_t _IO_default_write __P ((_IO_FILE *, const void *, _IO_ssize_t)); extern _IO_ssize_t _IO_default_read __P ((_IO_FILE *, void *, _IO_ssize_t)); extern int _IO_default_stat __P ((_IO_FILE *, void *)); #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_default_seek __P ((_IO_FILE *, _IO_off64_t, int)); +extern _IO_off64_t _IO_default_seek __P ((_IO_FILE *, _IO_off64_t, int)); #else -extern _IO_fpos_t _IO_default_seek __P ((_IO_FILE *, _IO_off_t, int)); +extern _IO_off_t _IO_default_seek __P ((_IO_FILE *, _IO_off_t, int)); #endif extern int _IO_default_sync __P ((_IO_FILE *)); #define _IO_default_close ((_IO_close_t) _IO_default_sync) @@ -389,11 +389,11 @@ extern void _IO_flush_all_linebuffered __P ((void)); extern int _IO_file_doallocate __P ((_IO_FILE *)); extern _IO_FILE* _IO_file_setbuf __P ((_IO_FILE *, char *, _IO_ssize_t)); #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); -extern _IO_fpos64_t _IO_file_seek __P ((_IO_FILE *, _IO_off64_t, int)); +extern _IO_off64_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +extern _IO_off64_t _IO_file_seek __P ((_IO_FILE *, _IO_off64_t, int)); #else -extern _IO_fpos_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); -extern _IO_fpos_t _IO_file_seek __P ((_IO_FILE *, _IO_off_t, int)); +extern _IO_off_t _IO_file_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +extern _IO_off_t _IO_file_seek __P ((_IO_FILE *, _IO_off_t, int)); #endif extern _IO_size_t _IO_file_xsputn __P ((_IO_FILE *, const void *, _IO_size_t)); extern int _IO_file_stat __P ((_IO_FILE *, void *)); @@ -427,9 +427,9 @@ extern int _IO_str_underflow __P ((_IO_FILE *)); extern int _IO_str_overflow __P ((_IO_FILE *, int)); extern int _IO_str_pbackfail __P ((_IO_FILE *, int)); #if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -extern _IO_fpos64_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); +extern _IO_off64_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off64_t, int, int)); #else -extern _IO_fpos_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); +extern _IO_off_t _IO_str_seekoff __P ((_IO_FILE *, _IO_off_t, int, int)); #endif extern void _IO_str_finish __P ((_IO_FILE *, int)); @@ -544,12 +544,12 @@ extern int _IO_vscanf __P ((const char *, _IO_va_list)); where an _IO_fpos_t is a struct. Note that _IO_off_t must be an integral type. */ -/* _IO_pos_BAD is an _IO_fpos_t value indicating error, unknown, or EOF. */ +/* _IO_pos_BAD is an _IO_off_t value indicating error, unknown, or EOF. */ #ifndef _IO_pos_BAD # if defined(_G_IO_IO_FILE_VERSION) && _G_IO_IO_FILE_VERSION == 0x20001 -# define _IO_pos_BAD ((_IO_fpos64_t) -1) +# define _IO_pos_BAD ((_IO_off64_t) -1) # else -# define _IO_pos_BAD ((_IO_fpos_t) -1) +# define _IO_pos_BAD ((_IO_off_t) -1) # endif #endif /* _IO_pos_as_off converts an _IO_fpos_t value to an _IO_off_t value. */ diff --git a/gnu/egcs/libio/parsestream.h b/gnu/egcs/libio/parsestream.h index 326ab87a809..97655bcbf69 100644 --- a/gnu/egcs/libio/parsestream.h +++ b/gnu/egcs/libio/parsestream.h @@ -42,7 +42,7 @@ extern "C++" { class parsebuf : public streambuf { protected: - _IO_fpos_t pos_at_line_start; + _IO_off_t pos_at_line_start; long _line_length; unsigned long __line_number; char *buf_start; diff --git a/gnu/egcs/libio/stdstreams.cc b/gnu/egcs/libio/stdstreams.cc index a5889d738e2..7a74eaaa443 100644 --- a/gnu/egcs/libio/stdstreams.cc +++ b/gnu/egcs/libio/stdstreams.cc @@ -36,7 +36,7 @@ the executable file might be covered by the GNU General Public License. */ // then we don't need to, since in that case stdin/stdout/stderr // are identical to _IO_stdin/_IO_stdout/_IO_stderr. -#include "libio.h" +#include <libio.h> #ifdef _STDIO_USES_IOSTREAM #define CIN_SBUF _IO_stdin_ diff --git a/gnu/egcs/libstdc++/ChangeLog b/gnu/egcs/libstdc++/ChangeLog index f0e953012b6..1d48242b6cd 100644 --- a/gnu/egcs/libstdc++/ChangeLog +++ b/gnu/egcs/libstdc++/ChangeLog @@ -1,3 +1,19 @@ +2001-01-01 Bernd Schmidt <bernds@redhat.co.uk> + + 1999-12-07 Martin v. Löwis <loewis@informatik.hu-berlin.de> + * stl_deque.h (_Deque_base::const_iterator): Change third + template argument to pointer type. + Reported by Carlo Wood <carlo@node1500a.a2000.nl> + + 1999-11-10 Benjamin Kosnik <bkoz@haight.constant.com> + Matthias Klose <doko@cs.tu-berlin.de> + * stl_rope.h: Fix initialization order. + * stl_deque.h: Use static_casts<size_type>(signed_type). + +2000-11-24 Magnus Fromreide <magfr@lysator.liu.se> + + * sstream: Backport libstdc++-V3 sstream to V2. + 2000-04-24 Magnus Fromreide <magfr@lysator.liu.se> * sstream: New file. diff --git a/gnu/egcs/libstdc++/stl/stl_deque.h b/gnu/egcs/libstdc++/stl/stl_deque.h index 48a4c76d55a..24a8bfb1bc8 100644 --- a/gnu/egcs/libstdc++/stl/stl_deque.h +++ b/gnu/egcs/libstdc++/stl/stl_deque.h @@ -342,7 +342,7 @@ public: _Base; typedef typename _Base::allocator_type allocator_type; typedef _Deque_iterator<_Tp,_Tp&,_Tp*,__bufsiz> iterator; - typedef _Deque_iterator<_Tp,const _Tp&,const _Tp&, __bufsiz> const_iterator; + typedef _Deque_iterator<_Tp,const _Tp&,const _Tp*, __bufsiz> const_iterator; _Deque_base(const allocator_type& __a, size_t __num_elements) : _Base(__a), _M_start(), _M_finish() @@ -815,7 +815,7 @@ public: // Erase iterator __next = __pos; ++__next; difference_type __index = __pos - _M_start; - if (__index < (size() >> 1)) { + if (static_cast<size_type>(__index) < (size() >> 1)) { copy_backward(_M_start, __pos, __next); pop_front(); } @@ -1048,7 +1048,7 @@ deque<_Tp,_Alloc,__bufsize>::erase(iterator __first, iterator __last) else { difference_type __n = __last - __first; difference_type __elems_before = __first - _M_start; - if (__elems_before < (size() - __n) / 2) { + if (static_cast<size_type>(__elems_before) < (size() - __n) / 2) { copy_backward(_M_start, __first, __last); iterator __new_start = _M_start + __n; destroy(_M_start, __new_start); @@ -1282,7 +1282,7 @@ deque<_Tp,_Alloc,__bufsize>::_M_insert_aux(iterator __pos, { difference_type __index = __pos - _M_start; value_type __x_copy = __x; - if (__index < size() / 2) { + if (static_cast<size_type>(__index) < size() / 2) { push_front(front()); iterator __front1 = _M_start; ++__front1; @@ -1311,7 +1311,7 @@ typename deque<_Tp,_Alloc,__bufsize>::iterator deque<_Tp,_Alloc,__bufsize>::_M_insert_aux(iterator __pos) { difference_type __index = __pos - _M_start; - if (__index < size() / 2) { + if (static_cast<size_type>(__index) < size() / 2) { push_front(front()); iterator __front1 = _M_start; ++__front1; @@ -1344,7 +1344,7 @@ deque<_Tp,_Alloc,__bufsize>::_M_insert_aux(iterator __pos, const difference_type __elems_before = __pos - _M_start; size_type __length = size(); value_type __x_copy = __x; - if (__elems_before < __length / 2) { + if (static_cast<size_type>(__elems_before) < __length / 2) { iterator __new_start = _M_reserve_elements_at_front(__n); iterator __old_start = _M_start; __pos = _M_start + __elems_before; @@ -1403,7 +1403,7 @@ deque<_Tp,_Alloc,__bufsize>::_M_insert_aux(iterator __pos, { const difference_type __elemsbefore = __pos - _M_start; size_type __length = size(); - if (__elemsbefore < __length / 2) { + if (static_cast<size_type>(__elemsbefore) < __length / 2) { iterator __new_start = _M_reserve_elements_at_front(__n); iterator __old_start = _M_start; __pos = _M_start + __elemsbefore; diff --git a/gnu/egcs/libstdc++/stl/stl_rope.h b/gnu/egcs/libstdc++/stl/stl_rope.h index 44f51aed1ae..fa1e848c065 100644 --- a/gnu/egcs/libstdc++/stl/stl_rope.h +++ b/gnu/egcs/libstdc++/stl/stl_rope.h @@ -386,8 +386,8 @@ struct _Rope_RopeRep : public _Rope_rep_base<_CharT,_Alloc> { typedef _Rope_rep_base<_CharT,_Alloc>::allocator_type allocator_type; _Rope_RopeRep(_Tag __t, int __d, bool __b, size_t __size, allocator_type __a) - : _M_tag(__t), _M_depth(__d), _M_is_balanced(__b), _M_c_string(0), - _Rope_rep_base<_CharT,_Alloc>(__size, __a) + : _Rope_rep_base<_CharT,_Alloc>(__size, __a), + _M_tag(__t), _M_depth(__d), _M_is_balanced(__b), _M_c_string(0) { # ifndef __GC _M_refcount = 1; @@ -562,8 +562,8 @@ struct _Rope_RopeLeaf : public _Rope_RopeRep<_CharT,_Alloc> { /* doesn't matter. */ typedef _Rope_rep_base<_CharT,_Alloc>::allocator_type allocator_type; _Rope_RopeLeaf(__GC_CONST _CharT* __d, size_t __size, allocator_type __a) - : _M_data(__d) - , _Rope_RopeRep<_CharT,_Alloc>(_S_leaf, 0, true, __size, __a) + : _Rope_RopeRep<_CharT,_Alloc>(_S_leaf, 0, true, __size, __a), + _M_data(__d) { __stl_assert(__size > 0); if (_S_is_basic_char_type((_CharT *)0)) { @@ -593,10 +593,10 @@ struct _Rope_RopeConcatenation : public _Rope_RopeRep<_CharT,_Alloc> { _Rope_RopeConcatenation(_Rope_RopeRep<_CharT,_Alloc>* __l, _Rope_RopeRep<_CharT,_Alloc>* __r, allocator_type __a) - : _M_left(__l), _M_right(__r) - , _Rope_RopeRep<_CharT,_Alloc>( + : _Rope_RopeRep<_CharT,_Alloc>( _S_concat, max(__l->_M_depth, __r->_M_depth) + 1, false, - __l->_M_size + __r->_M_size, __a) + __l->_M_size + __r->_M_size, __a), + _M_left(__l), _M_right(__r) {} # ifndef __GC ~_Rope_RopeConcatenation() { @@ -629,11 +629,12 @@ struct _Rope_RopeFunction : public _Rope_RopeRep<_CharT,_Alloc> { typedef _Rope_rep_base<_CharT,_Alloc>::allocator_type allocator_type; _Rope_RopeFunction(char_producer<_CharT>* __f, size_t __size, bool __d, allocator_type __a) - : _M_fn(__f) + :_Rope_RopeRep<_CharT,_Alloc>(_S_function, 0, true, __size, __a), + _M_fn(__f) # ifndef __GC , _M_delete_when_done(__d) # endif - , _Rope_RopeRep<_CharT,_Alloc>(_S_function, 0, true, __size, __a) { + { __stl_assert(__size > 0); # ifdef __GC if (__d) { @@ -693,9 +694,8 @@ struct _Rope_RopeSubstring : public _Rope_RopeFunction<_CharT,_Alloc>, typedef _Rope_rep_base<_CharT,_Alloc>::allocator_type allocator_type; _Rope_RopeSubstring(_Rope_RopeRep<_CharT,_Alloc>* __b, size_t __s, size_t __l, allocator_type __a) - : _M_base(__b) + : _Rope_RopeFunction<_CharT,_Alloc>(this, __l, false, __a), _M_base(__b) , _M_start(__s) - , _Rope_RopeFunction<_CharT,_Alloc>(this, __l, false, __a) { __stl_assert(__l > 0); __stl_assert(__s + __l <= __b->_M_size); @@ -766,16 +766,16 @@ class _Rope_char_ref_proxy { _My_rope* _M_root; // The whole rope. public: _Rope_char_ref_proxy(_My_rope* __r, size_t __p) : - _M_pos(__p), _M_root(__r), _M_current_valid(false) {} + _M_pos(__p), _M_current_valid(false), _M_root(__r) {} _Rope_char_ref_proxy(const _Rope_char_ref_proxy& __x) : - _M_pos(__x._M_pos), _M_root(__x._M_root), _M_current_valid(false) {} + _M_pos(__x._M_pos), _M_current_valid(false), _M_root(__x._M_root) {} // Don't preserve cache if the reference can outlive the // expression. We claim that's not possible without calling // a copy constructor or generating reference to a proxy // reference. We declare the latter to have undefined semantics. _Rope_char_ref_proxy(_My_rope* __r, size_t __p, _CharT __c) : - _M_pos(__p), _M_root(__r), _M_current(__c), _M_current_valid(true) {} + _M_pos(__p), _M_current(__c), _M_current_valid(true), _M_root(__r) {} inline operator _CharT () const; _Rope_char_ref_proxy& operator= (_CharT __c); _Rope_char_ptr_proxy<_CharT,_Alloc> operator& () const; |