From: Glenn Morris <rgm@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: CC, CFLAGS, and -m32 [was Re: Pretest compilation problem]
Date: Wed, 16 Feb 2011 22:16:16 -0500 [thread overview]
Message-ID: <daaahv4agv.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <m31v380zbz.fsf@linux-m68k.org> (Andreas Schwab's message of "Wed, 16 Feb 2011 16:32:48 +0100")
Andreas Schwab wrote:
> You really should put -m32 into CC, since it is a different compiler.
I've seen this advertized elsewhere, and it's off-topic for Emacs, but
can you explain this to me?
Eg `info make' says:
`CC'
Program for compiling C programs; default `cc'.
"gcc -m32" is not a program. It is a program plus some switches.
I believe you if you say that switch causes an entirely different compiler
to be invoked behind the scenes, but I don't buy that as a justification
for why -m32 should go there and not in CFLAGS.
It just seems like an excuse to get round the fact that some Makefiles
don't pass CFLAGS during the linking stage...
`info make' also says:
`CFLAGS'
Extra flags to give to the C compiler.
Not "flags passed to the compiler if it is being invoked as a compiler,
not a linker". Just "flags passed to the C compiler", full-stop.
next prev parent reply other threads:[~2011-02-17 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CMM.0.94.0.1297820041.beebe@psi.math.utah.edu>
2011-02-16 14:22 ` Pretest compilation problem Chong Yidong
2011-02-16 15:32 ` Andreas Schwab
2011-02-17 3:16 ` Glenn Morris [this message]
2011-02-17 17:28 ` CC, CFLAGS, and -m32 [was Re: Pretest compilation problem] Paul Eggert
2011-02-19 17:39 ` Chong Yidong
2011-02-19 18:14 ` Paul Eggert
2011-02-17 22:57 ` Miles Bader
2011-02-16 19:11 ` Pretest compilation problem Glenn Morris
2011-02-16 22:22 ` Andreas Schwab
2011-02-17 1:40 ` Chong Yidong
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=daaahv4agv.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.