From: "Paul R. Nash" <nashpaulr@gmail.com>
To: binutils@sourceware.org
Subject: Re: binutils-2.17: --cref broken? Extra warnings and corrupted data
Date: Wed, 19 Jul 2006 16:33:00 -0000 [thread overview]
Message-ID: <e6f772530607190933s5c45dc4bvbf18ebf117a7231c@mail.gmail.com> (raw)
In-Reply-To: <20060719042334.GS18571@bubble.grove.modra.org>
On 7/18/06, Alan Modra <amodra@bigpond.net.au> wrote:
> On Tue, Jul 18, 2006 at 08:44:31PM -0700, Paul R. Nash wrote:
> > ../.././binutils-2.17/ld/ldcref.c: In function `handle_asneeded_cref':
> > ../.././binutils-2.17/ld/ldcref.c:242: error: structure has no member
> > named `count'
> > ../.././binutils-2.17/ld/ldcref.c:283: error: structure has no member
> > named `count'
> > make[4]: *** [ldcref.o] Error 1
> >
> > Indeed, there is no count in my version of struct
> > bfd_hash_table...actually there's no other usage of ".count" anywhere
> > in ld at least. Is that mainline only?
>
> Yes, you need a slightly different patch for 2.17. Just delete all
> occurrences of old_count in the patch you have, or pull the 2.17 version
> from CVS binutils-2_17-branch.
Oh -- duh, I didn't realize the patch was in CVS already (not on that list)!
Okay, I applied this and rebuilt my toolchain, and everything is
working much better!
Thanks all...
-PN
next prev parent reply other threads:[~2006-07-19 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 6:41 Paul Nash
2006-07-17 2:03 ` Alan Modra
2006-07-17 22:30 ` H. J. Lu
2006-07-17 22:53 ` H. J. Lu
2006-07-18 3:04 ` Alan Modra
2006-07-18 16:28 ` Paul R. Nash
2006-07-18 17:20 ` Andreas Schwab
2006-07-19 1:54 ` Alan Modra
2006-07-19 3:44 ` Paul R. Nash
2006-07-19 4:23 ` Alan Modra
2006-07-19 16:33 ` Paul R. Nash [this message]
2006-07-18 16:08 ` Paul R. Nash
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=e6f772530607190933s5c45dc4bvbf18ebf117a7231c@mail.gmail.com \
--to=nashpaulr@gmail.com \
--cc=binutils@sourceware.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).