public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, merijn@a5.procura.nl,
	nobody@gcc.gnu.org
Subject: Re: bootstrap/5205: [HP-UX] gas fed with unrecognized pseudo-op's in 64-bit build
Date: Wed, 27 Feb 2002 17:02:00 -0000	[thread overview]
Message-ID: <20020227170221.4921.qmail@sources.redhat.com> (raw)

Synopsis: [HP-UX] gas fed with unrecognized pseudo-op's in 64-bit build

State-Changed-From-To: feedback->analyzed
State-Changed-By: rodrigc
State-Changed-When: Wed Feb 27 09:02:20 2002
State-Changed-Why:
    This information contributed by Steve Ellcey at HP:
    
    This person is actually building a 32 bit compiler, not a 64 bit one
    like he thinks he is.  hppa2.0w-hp-hpux11.00 is a 64 bit capabable
    machine, but it still generates 32 bit code by default.  To build a 64
    bit HPPA compiler, use a target, build, and host setting of
    hppa64-hp-hpux11.00 and use an existing 64 bit GCC or HP C with the
    +DD64 option to do the build.  If he doesn't have a 64 bit GAS he
    needs to build binutils with the same target/build/host."
    
    Can you rebuild your GCC and binutils with the
    correct target information and tell us if that works?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5205


             reply	other threads:[~2002-02-27 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 17:02 rodrigc [this message]
2003-05-07 18:16 Dara Hazeghi
2003-05-07 19:06 Dara Hazeghi
2003-05-07 21:20 bangerth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020227170221.4921.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=merijn@a5.procura.nl \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).