From: Shaun Jackman <sjackman@pathwayconnect.com>
To: binutils@sources.redhat.com
Subject: ARM_COFF_BUGFIX for wince [PATCH]
Date: Fri, 11 Jul 2003 14:07:00 -0000 [thread overview]
Message-ID: <1057932467.3202.152.camel@bluesteel.pathway> (raw)
Just want to make sure this patch made it in.
Cheers,
Shaun
* bfd/config.bfd: Add -DARM_COFF_BUGFIX to targ_cflags for arm-wince-pe.
diff -ur binutils-2.14-/bfd/config.bfd binutils-2.14/bfd/config.bfd
--- binutils-2.14-/bfd/config.bfd 2003-06-17 15:57:35.000000000 -0600
+++ binutils-2.14/bfd/config.bfd 2003-06-17 16:03:02.000000000 -0600
@@ -169,7 +169,7 @@
targ_defvec=armpe_little_vec
targ_selvecs="armpe_little_vec armpe_big_vec armpei_little_vec armpei_big_vec"
targ_underscore=no
- targ_cflags=-DARM_WINCE
+ targ_cflags="-DARM_WINCE -DARM_COFF_BUGFIX"
;;
arm-*-pe*)
targ_defvec=armpe_little_vec
next reply other threads:[~2003-07-11 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 14:07 Shaun Jackman [this message]
2003-07-17 14:27 ` 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=1057932467.3202.152.camel@bluesteel.pathway \
--to=sjackman@pathwayconnect.com \
--cc=binutils@sources.redhat.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).