bootstrap/7882: HP bootstrap failure when building on PA 2.0 for PA 1.1
Jeff Law
law@porcupine.slc.redhat.com
Tue Sep 10 10:46:00 GMT 2002
The following reply was made to PR bootstrap/7882; it has been noted by GNATS.
From: Jeff Law <law@porcupine.slc.redhat.com>
To: dacut@neolinear.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/7882: HP bootstrap failure when building on PA 2.0 for
PA 1.1
Date: Tue, 10 Sep 2002 11:48:07 -0600
In message <20020910165058.2609.qmail@sources.redhat.com>, dacut@neolinear.com
writes:
>
>>Number: 7882
>>Category: bootstrap
>>Synopsis: HP bootstrap failure when building on PA 2.0 for PA 1.1
>>Confidential: no
>>Severity: non-critical
>>Priority: low
>>Responsible: unassigned
>>State: open
>>Class: sw-bug
>>Submitter-Id: net
>>Arrival-Date: Tue Sep 10 09:56:01 PDT 2002
>>Closed-Date:
>>Last-Modified:
>>Originator: dacut@neolinear.com
>>Release: gcc-3.2
>>Organization:
>>Environment:
>HP-UX packard B.11.11 U 9000/785 2002930816 unlimited-user license
>Build host is HPPA2.0, but building for HPPA1.1.
>>Description:
>bootstrapping fails on our HP-UX boxes (which have a PA2.0 processor, but we'
>re building for PA1.1 for compatibility) because __gcc_plt_call (defined in g
>cc-3.2/gcc/config/pa/lib2funcs.asm) is missing from
>libgcc.a.
>
>It appears to be a bug in the configuration step; lib2funcs.asm is missing fr
>om all of the generated makefiles, regardless of the version of as (gas, HP a
>s, etc.) used.
[ ... ]
Note that the PA port generates PA1.1 code unless you explicitly ask for
PA2.0 code via the -mpa-risc-2-0 runtime switch.
So you really shouldn't need to do anything special to generate PA1.1 code,
and in fact, by trying to do something special (configure for hppa1.1-hpux)
you've confused the compiler into thinking it's building cross tools which
is the root cause of your link time failures.
Jeff
More information about the Gcc-prs
mailing list