From: "David S. Miller" <davem@davemloft.net>
To: Alan Modra <amodra@bigpond.net.au>
Cc: schwab@suse.de, nickc@redhat.com, binutils@sources.redhat.com
Subject: Re: Problems compiling elfxx-sparc.c
Date: Fri, 22 Apr 2005 03:53:00 -0000 [thread overview]
Message-ID: <20050421204552.2cfe2f9d.davem@davemloft.net> (raw)
In-Reply-To: <20050422031857.GB7783@bubble.modra.org>
On Fri, 22 Apr 2005 12:48:57 +0930
Alan Modra <amodra@bigpond.net.au> wrote:
> Perhaps. It's a little different situation. The elflink.c function
> handles both 32-bit and 64-bit relocs, whereas I presume
> sparc_elf_r_symndx_64 will only be used on 64-bit relocs. But yes, this
> is a pot/kettle scenario. :)
And it's even more moot now that it has been determined that
we'll need to set want_64=yes in config.bfd to get this to
build in the very cases where these warnings were showing up,
which will in turn make all the things causing those warnings
go away.
next prev parent reply other threads:[~2005-04-22 3:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 10:19 Nick Clifton
2005-04-20 13:15 ` Andreas Schwab
2005-04-20 18:26 ` David S. Miller
2005-04-20 18:40 ` David S. Miller
2005-04-20 22:38 ` Andreas Schwab
2005-04-20 23:21 ` David S. Miller
2005-04-21 12:20 ` Andreas Schwab
2005-04-21 3:16 ` Alan Modra
2005-04-21 3:24 ` David S. Miller
2005-04-22 3:19 ` Alan Modra
2005-04-22 3:53 ` David S. Miller [this message]
2005-04-21 10:50 ` Nick Clifton
2005-04-21 11:54 ` Eric Botcazou
2005-04-21 13:42 ` Ian Lance Taylor
2005-04-21 18:48 ` David S. Miller
2005-04-22 9:52 ` Nick Clifton
2005-04-22 10:02 ` Nick Clifton
2005-04-22 13:25 ` Ian Lance Taylor
2005-04-22 19:10 ` David S. Miller
2005-04-25 9:47 ` Nick Clifton
2005-04-25 18:32 ` David S. Miller
2005-04-25 19:10 ` David S. Miller
2005-04-25 21:54 ` David S. Miller
2005-04-26 8:45 ` Nick Clifton
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=20050421204552.2cfe2f9d.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=schwab@suse.de \
/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).