From: Miles Bader <miles@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Andreas Schwab <schwab@linux-m68k.org>,
emacs-devel@gnu.org
Subject: Re: CC, CFLAGS, and -m32 [was Re: Pretest compilation problem]
Date: Fri, 18 Feb 2011 07:57:31 +0900 [thread overview]
Message-ID: <87tyg2w9pg.fsf@catnip.gol.com> (raw)
In-Reply-To: <daaahv4agv.fsf_-_@fencepost.gnu.org> (Glenn Morris's message of "Wed, 16 Feb 2011 22:16:16 -0500")
Glenn Morris <rgm@gnu.org> writes:
>> 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.
CC is just the first part of the command line invoked to compile things.
The term "program" is used because it's easy for humans to understand,
but the documentation is not a strict rule.
Standard practice is to use that form (CC="compiler + options") for
options that be should used consistently for all invocations of the
compiler... CFLAGS, by comparison is a bit unreliable.
-Miles
--
Learning, n. The kind of ignorance distinguishing the studious.
next prev parent reply other threads:[~2011-02-17 22:57 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 ` CC, CFLAGS, and -m32 [was Re: Pretest compilation problem] Glenn Morris
2011-02-17 17:28 ` Paul Eggert
2011-02-19 17:39 ` Chong Yidong
2011-02-19 18:14 ` Paul Eggert
2011-02-17 22:57 ` Miles Bader [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tyg2w9pg.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).