Commit 08b3d104 by John David Anglin Committed by John David Anglin

* install.texi (hppa64-hp-hpux11*): Document installation procedure.

From-SVN: r56660
parent 54f3c60d
2002-08-29 John David Anglin <dave@hiauly1.hia.nrc.ca>
* install.texi (hppa64-hp-hpux11*): Document installation procedure.
2002-08-29 Catherine Moore <clm@redhat.com> 2002-08-29 Catherine Moore <clm@redhat.com>
* config/v850/v850.h (MULDI3_LIBCALL, UCMPDI2_LIBCALL, CMPDI2_LIBCALL, * config/v850/v850.h (MULDI3_LIBCALL, UCMPDI2_LIBCALL, CMPDI2_LIBCALL,
......
...@@ -2036,7 +2036,8 @@ longer a multiple of 2 bytes. ...@@ -2036,7 +2036,8 @@ longer a multiple of 2 bytes.
We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
platforms; you may encounter a variety of problems when using the HP platforms; you may encounter a variety of problems when using the HP
assembler. assembler. The HP assembler does not work with the @samp{hppa64-hp-hpux11*}
port.
Specifically, @option{-g} does not work on HP-UX (since that system Specifically, @option{-g} does not work on HP-UX (since that system
uses a peculiar debugging format which GCC does not know about), unless you uses a peculiar debugging format which GCC does not know about), unless you
...@@ -2044,8 +2045,9 @@ use GAS and GDB and configure GCC with the ...@@ -2044,8 +2045,9 @@ use GAS and GDB and configure GCC with the
@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
@option{--with-as=@dots{}} options. @option{--with-as=@dots{}} options.
If you wish to use pa-risc 2.0 architecture support, you must use either If you wish to use the pa-risc 2.0 architecture support with a 32-bit
the HP assembler, gas/binutils 2.11 or a recent runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
or a recent
@uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}. @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
There are two default scheduling models for instructions. These are There are two default scheduling models for instructions. These are
...@@ -2117,15 +2119,35 @@ bootstrap}. ...@@ -2117,15 +2119,35 @@ bootstrap}.
@end html @end html
@heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
GCC 3.0 and up support HP-UX 11. You must use GNU binutils 2.11 or above on GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
this platform. Thread support is not currently implemented for this are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
platform, so @option{--enable-threads} does not work. code for the 32-bit pa-risc runtime architecture. It uses the HP
See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html} linker and is currently the default selected by config.guess. The
optional @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
pa-risc 2.0 architecture. It must be explicitly selected using the
@samp{--host=hppa64-hp-hpux11*} configure option. Different prefixes
must be used if both ports are to be installed on the same system.
You must use GNU binutils 2.11 or above with the 32-bit port. Thread
support is not currently implemented, so @option{--enable-threads} does
not work. See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}. and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
GCC 2.95.x is not supported under HP-UX 11 and cannot be used to GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
information about obtaining precompiled GCC binaries for HP-UX. information about obtaining precompiled GCC binaries for HP-UX.
GNU binutils 2.13 or later is recommended with the 64-bit port.
The HP assembler is not supported. It is @emph{highly} recommended
that the GNU linker be used as well. Either binutils must be built
prior to gcc, or a binary distribution of gcc or binutils must be
obtained for the initial builds. When starting with a HP compiler,
it is preferable to use the ANSI compiler as the bundled compiler
only supports traditional C. Bootstrapping with the bundled compiler
is tested infrequently and problems often arise because of the subtle
differences in semantics between traditional and ISO C. There also
have been problems reported with various binary distributions. This
port still is undergoing significant development.
@html @html
</p> </p>
<hr> <hr>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment