diff options
Diffstat (limited to 'gcc/doc/install.texi')
| -rw-r--r-- | gcc/doc/install.texi | 76 |
1 files changed, 50 insertions, 26 deletions
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 2904265..0c27b7c 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -33,7 +33,7 @@ @settitle Installing GCC: Binaries @end ifset -@comment $Id$ +@comment $Id: install.texi,v 1.1 2001/05/11 22:10:54 gerald Exp $ @c Copyright (C) 2001 Free Software Foundation, Inc. @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com @@ -242,10 +242,10 @@ where @emph{srcdir} == @emph{objdir} should still work, but doesn't get extensive testing; building where @emph{objdir} is a subdirectory of @emph{srcdir} is unsupported. -Second, when configuring a native system, either ``@command{cc}'' or -``@command{gcc}'' must be in your path or you must set CC in your -environment before running configure. -Otherwise the configuration scripts may fail. +Second, when configuring a native system, either ``@command{cc}'' or +``@command{gcc}'' must be in your path or you must set @command{CC} in +your environment before running configure. Otherwise the configuration +scripts may fail. To configure GCC: @@ -806,7 +806,14 @@ contact their makers. @itemize @item -@uref{http://www-frec.bull.com/docs/download.htm,,AIX}; +AIX: +@itemize +@item +@uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and Shareware Archive for AIX}; + +@item +@uref{http://aixpdlib.seas.ucla.edu,,UCLA Software Library for AIX}; +@end itemize @item DOS - @uref{http://www.delorie.com/djgpp/,,DJGPP}; @@ -1314,11 +1321,35 @@ compiled with the native C compiler and GCC. During the stage1 phase of the build, the native AIX compiler @strong{must} be invoked as "cc" (not "xlc"). Once @command{configure} has been informed of "xlc", one needs to use "make distclean" to remove the -configure cache files and ensure that @command{$CC} environment variable +configure cache files and ensure that @command{CC} environment variable does not provide a definition that will confuse @command{configure}. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). +Binutils 2.10 does not support AIX 4.3. Binutils available from the +@uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX Toolbox for Linux: GNU and Open Source tools for AIX}; +website does work. Binutils 2.11 is expected to include AIX 4.3 +support. The GNU Assembler is necessary for libstdc++ to build. The +AIX native ld still is recommended. The native AIX tools do +interoperate with GCC. + +Linking executables and shared libraries may produce warnings of +duplicate symbols. The assembly files generated by GCC for AIX always +have included multiple symbol definitions for certain global variable +and function declarations in the original program. The warnings should +not prevent the linker from producing a correct library or runnable +executable. + +AIX 4.3 utilizes a "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 correctly. +These routines are used by GCC and result in error messages during +linking such as "not a COFF file". The version of the routines shipped +with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} +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. + Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the @option{-bbigtoc} option is used to link GCC-produced object files into an executable that overflows the TOC. A fix @@ -1327,20 +1358,11 @@ available from IBM Customer Support and from its @uref{http://service.boulder.ibm.com/,,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 correctly. -These routines are used by GCC and result in error messages during linking -such as "not a COFF file". The version of the routines shipped -with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} 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 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 is available from IBM Customer Support and from its +@uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com} +website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS @@ -1348,11 +1370,13 @@ TO ASSEMBLE/BIND) is available from IBM Customer Support and from its @uref{http://service.boulder.ibm.com/,,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 is available from IBM Customer Support and from its -@uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com} -website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. +AIX provides National Language Support (NLS). Compilers and assemblers +use NLS to support locale-specific representations of various data +formats including floating-point numbers (e.g., "." vs "," for +separating decimal fractions). There have been problems reported where +GCC does not produce the same floating-point formats that the assembler +expects. If one encouters this problem, set the @command{LANG} +environment variable to "C" or "En_US". @html |