From: DJ Delorie <dj@redhat.com>
To: wilson@specifixinc.com
Cc: gcc@gcc.gnu.org
Subject: Re: fixing vs WARN_CFLAGS vs cross builds
Date: Wed, 31 Mar 2004 07:55:00 -0000 [thread overview]
Message-ID: <200403310310.i2V3ACS1015846@greed.delorie.com> (raw)
In-Reply-To: <1080701413.1213.25.camel@leaf.tuliptree.org> (message from Jim Wilson on 30 Mar 2004 18:50:13 -0800)
For background, I'm doing this:
--build=i686-pc-linux-gnu
--host=i586-pc-msdosdjgpp
--target=i586-pc-msdosdjgpp
So, it's a native build, but cross-built. DJGPP *does* use
fixincludes, so that should run.
Apparently, configure tests $CC for support of -Wno-long-long
-Wno-variadic-macros (and a few others) and adds them to the stage1
flags if supported. However, $CC is a cross compiler, different
from $BUILD_CC.
"If the native compiler is GCC, we can enable warnings even in stage1."
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).
next prev parent reply other threads:[~2004-03-31 3:10 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 [this message]
2004-03-31 8:09 ` Jim Wilson
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=200403310310.i2V3ACS1015846@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=wilson@specifixinc.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).