From: Thomas Rast <trast@student.ethz.ch>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Compiling git with -Werror
Date: Fri, 27 Apr 2012 11:58:45 +0200 [thread overview]
Message-ID: <87bomd338q.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <4F9A6AB0.1050504@alum.mit.edu> (Michael Haggerty's message of "Fri, 27 Apr 2012 11:45:20 +0200")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> Is there some other mechanism to set strict CFLAGS parameters for the
> build without confusing ./configure?
As mentioned on IRC, you can put
CFLAGS = -g -O2 -Wall -Werror -Wdeclaration-after-statement
in config.mak. The Makefile includes that if it exists, so it is a good
place to gather your custom settings.
One trick I like to do in every Makefile is
O = 3
CFLAGS = -g -O$(O) -Wall <blah>
That way 'make O=0' does a build suitable for debugging.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-04-27 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:45 Compiling git with -Werror Michael Haggerty
2012-04-27 9:58 ` Thomas Rast [this message]
2012-04-27 10:07 ` Jeff King
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=87bomd338q.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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 NNTP newsgroup(s).