public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Piet/Pete Delaney <piet@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Updating to the latest binutils - any tips on how to do it easily?
Date: Wed, 30 Jan 2002 22:37:20 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805968@msgid-missing> (raw)

On Wed, Jan 30, 2002 at 01:57:33PM -0800, Jim Wilson wrote:
> >/tmp/ccC11dFe.s:15538: Error: Unknown opcode `data16.ua @iplt
> 
> You need a newer binutils if you want to use gcc 3.0.[23] to compile C++ code.
> 
> New IA-64 assembler syntax was introduced last summer, because it was not
> possible to fully implement the C++ ABI with the original assembler syntax.
> This new assembler syntax is used starting with gcc 3.0.2, and is not supported
> by any binutils older that last summer.  That unfortunately means that binutils
> 2.11 is not new enough, you have to use an unreleased binutils from the FSF
> development source tree.
> 
> Jim

Any suggestions on installing a newer binutils? I tried installing 
a recient version (binutils-2.11.2 or binutils-2.10.1) to /usr/local
and had problems with commands compiled with the current compiler,
(egcs-2.91.66/(egcs-1.1.2 release)), getting a SEGV when they started; 
so I backed out the changed binutils installation for now.

Perhaps the compiler and binutils have to be changed together?

The newer binutils seems to be needed for our LKCD lcrash stuff to work 
corectly for disassembling ia64 code.

-piet


             reply	other threads:[~2002-01-30 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 22:37 Piet/Pete Delaney [this message]
2002-01-30 23:13 ` [Linux-ia64] Updating to the latest binutils - any tips on how to do it easily? Jim Wilson

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=marc-linux-ia64-105590698805968@msgid-missing \
    --to=piet@sgi.com \
    --cc=linux-ia64@vger.kernel.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