From: Ian Lance Taylor <ian@zembu.com>
To: snowball3@bigfoot.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: objdump --debug and COFF weak functions
Date: Sat, 24 Jun 2000 15:48:00 -0000 [thread overview]
Message-ID: <20000624224811.5266.qmail@daffy.airs.com> (raw)
In-Reply-To: <395501BD.14163.1943715@localhost>
From: "Mark E." <snowball3@bigfoot.com>
Date: Sat, 24 Jun 2000 18:45:17 -0400
Below is a patch that fixes it for me. In case you're wondering, I used the
COFF_WITH_PE guards like in bfd/coffcode.h since C_NT_WEAK clashes with another C_*
symbol.
That doesn't work, though.
bfd/coffcode.h is included by many coff-*.c files with differing
definitions. It is compiled differently for each different COFF
target.
This is not true of binutils/rdcoff.c. It is only compiled once, in
the same way. A #ifdef test here is meaningless.
Ian
next prev parent reply other threads:[~2000-06-24 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-24 15:45 Mark E.
2000-06-24 15:48 ` Ian Lance Taylor [this message]
2000-06-24 16:48 ` Mark E.
2000-06-24 15:53 Mark E.
2000-06-24 16:48 Mark E.
2000-06-25 9:40 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=20000624224811.5266.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=snowball3@bigfoot.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).