From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23714 invoked by alias); 10 Sep 2002 17:56:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 23683 invoked by uid 71); 10 Sep 2002 17:56:01 -0000 Date: Tue, 10 Sep 2002 10:56:00 -0000 Message-ID: <20020910175601.23680.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Dave Cuthbert Subject: Re: bootstrap/7882: HP bootstrap failure when building on PA 2.0 for PA 1.1 Reply-To: Dave Cuthbert X-SW-Source: 2002-09/txt/msg00178.txt.bz2 List-Id: The following reply was made to PR bootstrap/7882; it has been noted by GNATS. From: Dave Cuthbert To: law@redhat.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 13:52:24 -0400 Jeff Law wrote: > 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. Ah, thanks for this info. We got burned by the HP compiler here (we have PA2.0 machines only, and one of our beta releases failed at a customer site which had PA1.1 machines), so I was being paranoid. Dave