From: Jim Wilson <wilson@specifixinc.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: fixing vs WARN_CFLAGS vs cross builds
Date: Wed, 31 Mar 2004 08:09:00 -0000 [thread overview]
Message-ID: <1080712699.1213.41.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <200403310310.i2V3ACS1015846@greed.delorie.com>
On Tue, 2004-03-30 at 19:10, DJ Delorie wrote:
> Well, it is GCC, and strict1 propogates to WARN_CFLAGS, and
> WARN_CFLAGS is passed to fixinc. But the compiler used in fixinc is a
> different gcc (BUILD_CC vs CC).
Thanks. I see the problem now. There is configure support that adds
options to strict1_warn based on CC. I missed this when looking at the
code. This was the info I was looking for. These tests are obviously
unsafe when WARN_STRICT is used with CC_FOR_BUILD where CC_FOR_BUILD is
different from CC.
We would need a parallel set of tests and macros for a
BUILD_WARN_STRICT, and it seems unreasonable to ask you do that much
work to fix your cross compiler build problem. So I think that simply
changing the fixinc.sh rule to not use WARN_STRICT is an acceptable
solution.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-03-31 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:29 DJ Delorie
2004-03-31 6:38 ` Jim Wilson
2004-03-31 6:40 ` DJ Delorie
2004-03-31 7:53 ` Jim Wilson
2004-03-31 7:55 ` DJ Delorie
2004-03-31 8:09 ` Jim Wilson [this message]
2004-03-31 8:03 Nathanael Nerode
2004-03-31 10:52 ` Jim Wilson
2004-03-31 12:43 ` Zack Weinberg
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=1080712699.1213.41.camel@leaf.tuliptree.org \
--to=wilson@specifixinc.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.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).