git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elia Pinto <gitter.spiros@gmail.com>
To: git@vger.kernel.org
Cc: jnareb@gmail.com, Elia Pinto <gitter.spiros@gmail.com>
Subject: [PATCH 0/2] add some new autoconf macros for searching the possible warning flags allowed by the current version of the gcc compiler
Date: Mon,  3 Nov 2014 06:57:19 -0800	[thread overview]
Message-ID: <1415026641-24767-1-git-send-email-gitter.spiros@gmail.com> (raw)

This patch series introduces some new autoconf macros for searching the possible warning flags allowed by the current version of the gcc compiler. 
Using these macros it adds a new option --enable-gcc-warnings (default off). There are several possible gcc warnings flags, 
i have included some of the most useful in my opinion but certainly there are several other perhaps more useful for git, so comments are welcome. 
Naturally the new macro are not limited only to the portable search of the gcc warning flags or to gcc in first place in any way

Elia Pinto (2):
  configure.ac: add new autoconf macro for checking valid compiler
    flags
  configure.ac: use GIT_CC_CHECK_FLAG_APPEND for adding
    --with-gcc-warnings configure option

 Makefile     |   12 ++++-
 configure.ac |  141 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 149 insertions(+), 4 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2014-11-03 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 14:57 Elia Pinto [this message]
2014-11-03 14:57 ` [PATCH 1/2] configure.ac: add new autoconf macro for checking valid compiler flags Elia Pinto
2014-11-03 19:39   ` Junio C Hamano
2014-11-03 14:57 ` [PATCH 2/2] configure.ac: use GIT_CC_CHECK_FLAG_APPEND for adding --with-gcc-warnings configure option Elia Pinto
2014-11-03 19:49   ` Junio C Hamano

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=1415026641-24767-1-git-send-email-gitter.spiros@gmail.com \
    --to=gitter.spiros@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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).