From: Chong Yidong <cyd@stupidchicken.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: CC, CFLAGS, and -m32 [was Re: Pretest compilation problem]
Date: Sat, 19 Feb 2011 12:39:00 -0500 [thread overview]
Message-ID: <87y65bj557.fsf@stupidchicken.com> (raw)
In-Reply-To: <4D5D5AAE.2000206@cs.ucla.edu> (Paul Eggert's message of "Thu, 17 Feb 2011 09:28:14 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 02/16/2011 07:16 PM, Glenn Morris wrote:
>> I've seen this advertized elsewhere, and it's off-topic for Emacs, but
>> can you explain this to me?
>
> It's to cater to a common usage, where one does
> "configure CC='cc -m32'; [edit]; make CFLAGS=-g".
>
> "configure" may decide to use "-g -O2", but you may find it easier
> to compile with plain -g than with -g -O2, because it's easier to debug
> code that isn't optimized.
>
> If instead you use "configure CC=cc CFLAGS=-m32", it's more of
> a pain: "configure" won't set all the CFLAGS for you, and when
> you run "make" yourself you need to say "make CFLAGS='-m32 -g'".
Nonetheless, there should be no downside for us to add CFLAGS to this
Makefile rule, correct? If you know of any risk, let me know.
next prev parent reply other threads:[~2011-02-19 17:39 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 [this message]
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
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=87y65bj557.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.
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).