From: Greg Schafer <gschafer@zip.com.au>
To: "H.J. Lu" <hjl@lucon.org>, binutils@sourceware.org
Subject: Re: GNU hash-style compatibility problem on x86_64
Date: Tue, 14 Aug 2007 22:45:00 -0000 [thread overview]
Message-ID: <20070814224531.GA5638@eyo32.local> (raw)
In-Reply-To: <20070814125638.GA11842@caradoc.them.org>
On Tue, Aug 14, 2007 at 08:56:38AM -0400, Daniel Jacobowitz wrote:
> On Tue, Aug 14, 2007 at 05:47:47AM -0700, H.J. Lu wrote:
> > Well, it sounds like a bug in binutils 2.17. There are so many of them
> > and they have been fixed in the current binutils. I don't want to spend
> > time on it unless it is reproducible in the current binutils.
>
> But wasn't the point of --hash-style=both to be compatible with older
> tools?
Yes, that was my understanding too and the main reason for my report. Roland
mentioned back-compat issues in this LKML posting:
http://lkml.org/lkml/2006/7/26/262
but admittedly he only touches on dynamic linkers, and of course he was
talking in the context of kernel vDSO.
> At a guess this has to do with the unrecognized shdr type.
I can understand HJ's response in that there isn't much incentive to fix
bugs in an old binutils release, but I was kind of hoping one of the experts
here might be able to pinpoint the problem and produce a minimal patch.
Regards
Greg
next prev parent reply other threads:[~2007-08-14 22:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 7:22 Greg Schafer
2007-08-14 12:48 ` H.J. Lu
2007-08-14 12:56 ` Daniel Jacobowitz
2007-08-14 13:02 ` H.J. Lu
2007-08-14 13:07 ` Mike Frysinger
2007-08-14 13:23 ` Jakub Jelinek
2007-08-14 13:31 ` Mike Frysinger
2007-08-14 13:39 ` Daniel Jacobowitz
2007-08-14 22:45 ` Greg Schafer [this message]
2007-08-14 23:35 ` DJ Delorie
2007-08-15 0:58 ` Greg Schafer
2007-08-15 1:01 ` DJ Delorie
2007-08-25 0:05 ` Eric Botcazou
2007-08-29 17:12 ` Mike Frysinger
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=20070814224531.GA5638@eyo32.local \
--to=gschafer@zip.com.au \
--cc=binutils@sourceware.org \
--cc=hjl@lucon.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).