From: DJ Delorie <dj@redhat.com>
To: gcc@gcc.gnu.org
Subject: fixing vs WARN_CFLAGS vs cross builds
Date: Tue, 30 Mar 2004 00:29:00 -0000 [thread overview]
Message-ID: <200403292112.i2TLC2xB002927@greed.delorie.com> (raw)
I'm trying to cross-build a native DJGPP. It tries to build fixinc,
but uses "gcc" as the compiler. It passes a full WARN_CFLAGS, which
includes options that the system gcc doesn't understand, and so fails.
Should we just not pass WARN_CFLAGS when cross compiling that way?
next reply other threads:[~2004-03-29 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:29 DJ Delorie [this message]
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
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=200403292112.i2TLC2xB002927@greed.delorie.com \
--to=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).