From: "Paul R. Nash" <nashpaulr@gmail.com>
To: "H. J. Lu" <hjl@lucon.org>, "Paul Nash" <nashpaulr@gmail.com>,
binutils@sourceware.org
Subject: Re: binutils-2.17: --cref broken? Extra warnings and corrupted data
Date: Wed, 19 Jul 2006 03:44:00 -0000 [thread overview]
Message-ID: <e6f772530607182044w3d0cb87djffd9b6a9871e8e34@mail.gmail.com> (raw)
In-Reply-To: <20060719015355.GP18571@bubble.grove.modra.org>
On 7/18/06, Alan Modra <amodra@bigpond.net.au> wrote:
> On Tue, Jul 18, 2006 at 12:34:09PM +0930, Alan Modra wrote:
> > On Mon, Jul 17, 2006 at 03:30:53PM -0700, H. J. Lu wrote:
> > > --cref was broken by --as-needed.
> >
> > Ah. My bug then.
>
> This extends the horrible hack of saving the main symbol table to saving
> the cref table too. I'm not proud at all of this hack for --as-needed.
> Some day when I have a some time on my hands I'll look at implementing
> a two-pass approach to loading --as-needed library syms.
>
Attempting to build this on 2.17, I encountered two problems:
1) I had to figure out bfd-in2.h so I could put that in my patch
against the dist tarball. That wasn't hard, I got around it.
2) After that, building yields:
gcc -DHAVE_CONFIG_H -I. -I../.././binutils-2.17/binutils -I.
-D_GNU_SOURCE -I. -I../.././binutils-2.17/binutils -I../bfd
-I../.././binutils-2.17/binutils/../bfd
-I../.././binutils-2.17/binutils/../include
-I../.././binutils-2.17/binutils/../intl -I../intl
-DLOCALEDIR="\"/usr/local/i686/4.1.1-1b/share/locale\""
-Dbin_dummy_emulation=bin_vanilla_emulation -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -Werror -O2 -pipe
-fno-stack-protector -c ../.././binutils-2.17/binutils/size.c
gcc -DHAVE_CONFIG_H -I. -I../.././binutils-2.17/gas -I. -D_GNU_SOURCE
-I. -I../.././binutils-2.17/gas -I../bfd
-I../.././binutils-2.17/gas/config
-I../.././binutils-2.17/gas/../include -I../.././binutils-2.17/gas/..
-I../.././binutils-2.17/gas/../bfd -I../.././binutils-2.17/gas/../intl
-I../intl -DLOCALEDIR="\"/usr/local/i686/4.1.1-1b/share/locale\"" -W
-Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -O2 -pipe
-fno-stack-protector -c ../.././binutils-2.17/gas/output-file.c
../.././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?
Thx...
-PN
next prev parent reply other threads:[~2006-07-19 3:44 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 [this message]
2006-07-19 4:23 ` Alan Modra
2006-07-19 16:33 ` Paul R. Nash
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=e6f772530607182044w3d0cb87djffd9b6a9871e8e34@mail.gmail.com \
--to=nashpaulr@gmail.com \
--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).