From: Rusty Russell <rusty@rustcorp.com.au>
To: "LKML" <linux-kernel@vger.kernel.org>
Cc: <linux-kbuild@vger.kernel.org>
Subject: [PATCH] scripts/gcc-version.sh: handle CC="gcc -m32"
Date: Tue, 10 Dec 2013 17:43:29 +1030 [thread overview]
Message-ID: <87d2l5ji06.fsf@rustcorp.com.au> (raw)
Without it we get ugly warnings (though build still succeeds).
$ make -j8 CC="gcc -m32"
In file included from <command-line>:0:0:
/usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such file or directory
#include <bits/predefs.h>
^
compilation terminated.
In file included from <command-line>:0:0:
/usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such file or directory
#include <bits/predefs.h>
^
compilation terminated.
/home/rusty/devel/kernel/linux/scripts/gcc-version.sh: line 31: printf: #: invalid number
/home/rusty/devel/kernel/linux/scripts/gcc-version.sh: line 31: printf: #: invalid number
/bin/sh: 1: [: 0001: unexpected operator
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
make[1]: Nothing to be done for `all'.
...
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff --git a/scripts/gcc-version.sh b/scripts/gcc-version.sh
index 7f2126df91f2..d48b0cbaf246 100644
--- a/scripts/gcc-version.sh
+++ b/scripts/gcc-version.sh
@@ -14,7 +14,7 @@ if [ "$1" = "-p" ] ; then
shift;
fi
-compiler="$*"
+compiler="$1"
if [ ${#compiler} -eq 0 ]; then
echo "Error: No compiler specified."
next reply other threads:[~2013-12-10 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 7:13 Rusty Russell [this message]
2014-01-03 17:10 ` [PATCH] scripts/gcc-version.sh: handle CC="gcc -m32" Michal Marek
2014-01-03 20:34 ` Michal Marek
2014-01-15 4:18 ` Rusty Russell
2014-01-16 15:34 ` Michal Marek
2014-01-16 22:26 ` Rusty Russell
2014-01-22 4:39 ` Rusty Russell
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=87d2l5ji06.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.
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).