public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: James E Wilson <wilson@specifixinc.com>
Cc: Alan Modra <amodra@bigpond.net.au>,
	Andreas Schwab <schwab@suse.de>, Ben Elliston <bje@au1.ibm.com>,
	binutils@sources.redhat.com
Subject: Re: build failure for ia64 (due to -Werror)
Date: Wed, 23 Mar 2005 19:24:00 -0000	[thread overview]
Message-ID: <4241421C.1080502@redhat.com> (raw)
In-Reply-To: <1111552545.18829.96.camel@aretha.corp.specifixinc.com>

Hi Jim,

> Anyways, I think the right solution is what Ian suggested, which is to
> remove elf32-ia64.lo from BDF32_BACKENDS.

I am happy to do that, but presumably the elf32-ia64.lo entry should be 
moved from BFD32_BACKENDS to BFD64_BACKENDS ?

Cheers
   Nick

  reply	other threads:[~2005-03-23 10:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  3:58 Ben Elliston
2005-03-18 13:14 ` Nick Clifton
2005-03-18 14:13   ` Alan Modra
2005-03-18 22:15     ` James E Wilson
2005-03-18 22:49       ` Ian Lance Taylor
2005-03-18 23:31         ` Ian Lance Taylor
2005-03-18 23:52           ` James E Wilson
2005-03-18 23:37       ` Andreas Schwab
2005-03-19  0:42         ` Alan Modra
2005-03-19  1:56           ` Andreas Schwab
2005-03-19  4:04             ` James E Wilson
2005-03-19  4:30               ` Andreas Schwab
2005-03-19  9:44                 ` James E Wilson
2005-03-19 12:13                 ` James E Wilson
2005-03-19 17:57                 ` James E Wilson
2005-03-19 18:37                   ` Alan Modra
2005-03-19 18:33                 ` James E Wilson
2005-03-19 19:00                   ` Andreas Schwab
2005-03-23  9:45           ` James E Wilson
2005-03-23 19:24             ` Nick Clifton [this message]
2005-03-24  9:27               ` James E Wilson
2005-03-24 14:58                 ` Nick Clifton
2005-03-19  0:56       ` Alan Modra
2005-03-22  2:19   ` Ben Elliston
2005-03-20  9:26 Paul Schlie
2005-03-20 19:42 ` Andreas Schwab

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=4241421C.1080502@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=bje@au1.ibm.com \
    --cc=schwab@suse.de \
    --cc=wilson@specifixinc.com \
    /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).