From: "J . A . Magallon" <jamagallon@able.es>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: [PATCH] ver_linux+kgcc
Date: Thu, 14 Dec 2000 01:07:47 +0100 [thread overview]
Message-ID: <20001214010747.A859@werewolf.able.es> (raw)
Hello.
In short: scripts/ver_linux can lie about the cc version used to build
kernel. With recent add for the detection of gcc727, kgcc anc cc, kernel
can be compiled with one cc and ver_linux report one other.
This can help people reporting hangs or bugs, because usually give the
output of ver_linux and it usually is wrong about gcc used for kernel.
BTW, I have added the GNU make version info present in 2.4 but not in 2.2.
NOTE: the cc misversioning also happens in 2.4
================== patch-ver_linux
--- linux/scripts/ver_linux.org Thu Dec 14 00:52:16 2000
+++ linux/scripts/ver_linux Thu Dec 14 01:07:15 2000
@@ -9,7 +9,13 @@
echo '-- unusual then possibly you have very old versions)'
uname -a
insmod -V 2>&1 | awk 'NR==1 {print "Kernel modules ",$NF}'
-echo "Gnu C " `gcc --version`
+echo "Gnu C " \
+ `gcc272 --version 2>/dev/null || \
+ kgcc --version 2>/dev/null || \
+ gcc --version 2>/dev/null || \
+ cc --version`
+make --version 2>&1 | awk -F, '{print $1}' | awk \
+ '/GNU Make/{print "Gnu Make ",$NF}'
ld -v 2>&1 | awk -F\) '{print $1}' | awk \
'/BFD/{print "Binutils ",$NF}'
ls -l `ldd /bin/sh | awk '/libc/{print $3}'` | sed -e 's/\.so$//' \
================== patch-ver_linux
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux werewolf 2.2.18-aa1 #1 SMP Mon Dec 11 21:26:28 CET 2000 i686
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-14 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001214010747.A859@werewolf.able.es \
--to=jamagallon@able.es \
--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).