From: Nick Clifton <nickc@redhat.com>
To: Dave Korn <dave.korn@artimi.com>
Cc: binutils@sourceware.org
Subject: Re: HEAD b0rked re coff-tic80?
Date: Thu, 28 Apr 2005 20:14:00 -0000 [thread overview]
Message-ID: <427115F1.4060704@redhat.com> (raw)
In-Reply-To: <SERRANOp3b6uIU1Gj0300000164@SERRANO.CAM.ARTIMI.COM>
Hi Dave,
> I refer the honourable gentleman to my earlier reply! It was of course an
> all-targets build.
Our emails crossed in the ether...
> I notice that the last-modified date on my /usr/include/_ansi.h is 1
> April. I'll see if maybe the w32api package changed recently.
Hmmm - that would still not explain the tc-i386.h vs obj-coff.h conflict
though. Since I cannot reproduce this problem locally however, I am
going to have to leave it with you to come up with a solution. Perhaps
something as simple as protecting the #define TARGET_FORMAT
declarations, although it would be nice to know why it is breaking for
you and not for me.
Cheers
Nick
next prev parent reply other threads:[~2005-04-28 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 11:32 Dave Korn
2005-04-26 17:10 ` Nick Clifton
2005-04-27 10:09 ` Dave Korn
2005-04-28 12:05 ` Nick Clifton
2005-04-28 12:08 ` Dave Korn
2005-04-28 12:19 ` Dave Korn
2005-04-28 13:04 ` Nick Clifton
2005-04-28 14:05 ` Dave Korn
2005-04-28 20:14 ` Nick Clifton [this message]
2005-04-28 22:47 ` Dave Korn
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=427115F1.4060704@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=dave.korn@artimi.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).