This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
bootstrap/5485: Document 64-bit bootstrap using 32-bit compiler {sparc,hppa}64
- From: rbrown64 at csc dot com dot au
- To: gcc-gnats at gcc dot gnu dot org
- Date: 25 Jan 2002 04:08:58 -0000
- Subject: bootstrap/5485: Document 64-bit bootstrap using 32-bit compiler {sparc,hppa}64
- Reply-to: rbrown64 at csc dot com dot au
>Number: 5485
>Category: bootstrap
>Synopsis: Document 64-bit bootstrap using 32-bit compiler {sparc,hppa}64
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 24 20:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Rodney Brown
>Release: gcc-3.1 20020121
>Organization:
>Environment:
sparcv9-sun-solaris2.8
>Description:
For sparc{v9,64}-sun-solaris2.[78] and maybe hppa64-hp-hpux11*
the 64-bit compiler will need to be installed with a different
--exec-prefix or --prefix from the 32-bit compiler (I think).
For the sparc at least this also requires a binutils build configured for the 64-bit environment.
On the sparc, the bootstrap using a 32-bit compiler fails attempting to link genflags with the stage1 compiler, since
libiberty was built with the 32-bit compiler.
Rebuilding libiberty with the stage1 compiler lets the bootstrap proceed.
In general, could gcc/doc/install.texi be updated with the
recommended procedure for building a 64-bit compiler using
an existing 32-bit gcc version and link to that from the
new sparc{v9,64}-sun-solaris2.[78] and hppa64-hp-hpux11.*
specific target entries.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: