From: Alex Dowad <alexinbeijing@gmail.com>
To: musl@lists.openwall.com
Subject: [PATCH v2] When building, don't use compiler flags which cause warnings
Date: Tue, 26 May 2015 20:36:45 +0200 [thread overview]
Message-ID: <1432665405-26308-1-git-send-email-alexinbeijing@gmail.com> (raw)
In-Reply-To: <20150526181830.GD17573@brightrain.aerifal.cx>
This silences some warnings when building with clang.
---
Dear Rich Felker,
This accomplishes the same thing as the previous patch by "promoting" all
warnings to errors. Look better?
Thanks,
Alex Dowad
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index cf9227a..bca2bd9 100755
--- a/configure
+++ b/configure
@@ -80,7 +80,7 @@ fi
tryflag () {
printf "checking whether compiler accepts %s... " "$2"
echo "typedef int x;" > "$tmpc"
-if $CC $2 -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
+if $CC $2 -Werror -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "yes\n"
eval "$1=\"\${$1} \$2\""
eval "$1=\${$1# }"
@@ -94,7 +94,7 @@ fi
tryldflag () {
printf "checking whether linker accepts %s... " "$2"
echo "typedef int x;" > "$tmpc"
-if $CC -nostdlib -shared "$2" -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
+if $CC -Werror -nostdlib -shared "$2" -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "yes\n"
eval "$1=\"\${$1} \$2\""
eval "$1=\${$1# }"
--
2.0.0.GIT
next prev parent reply other threads:[~2015-05-26 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 17:51 [PATCH] When building, don't use flags which cause compiler warning Alex Dowad
2015-05-26 18:18 ` Rich Felker
2015-05-26 18:36 ` Alex Dowad [this message]
2015-05-26 18:47 ` [PATCH v2] When building, don't use compiler flags which cause warnings Rich Felker
2015-05-26 18:55 ` Alex Dowad
2015-05-26 19:36 ` Rich Felker
2015-05-26 19:57 ` Alex Dowad
2015-05-27 2:22 ` Shiz
2015-05-27 3:14 ` Rich Felker
2015-05-27 12:30 ` Shiz
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=1432665405-26308-1-git-send-email-alexinbeijing@gmail.com \
--to=alexinbeijing@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).