From: Steven Cole <elenstev@mesatop.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] update ver_linux script to work with gcc 3.2.
Date: 28 Aug 2002 15:18:09 -0600 [thread overview]
Message-ID: <1030569489.4032.113.camel@spc9.esa.lanl.gov> (raw)
A commonly used gcc reports its version number thusly:
[steven@spc5 steven]$ gcc --version
2.96
But the new gcc 3.2 reports its version number thusly:
[steven@spc1 scripts]$ gcc --version
gcc (GCC) 3.2 (Mandrake Linux 9.0 3.2-1mdk)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This causes the current ver_linux script to produce less
than readable output for the gcc version when using gcc 3.2.
Here is a patch to the ver_linux script which allows it
to work both with the new gcc and the old gcc.
The patch was made against 2.4.20-pre4-ac2, but also applies to
2.4.20-pre4 and to 2.5.32 as well.
This was tested for the gcc 3.2 on Mandrake 9.0 beta4, but
will probably work for Red Hat Limbo or (null). Testing is
always welcomed. Backward compatibility with gcc 2.96 was
tested with Red Hat 7.3 and Mandrake 8.2.
Steven
--- linux-2.4.20-pre4-ac2/scripts/ver_linux.orig Wed Aug 28 14:37:39 2002
+++ linux-2.4.20-pre4-ac2/scripts/ver_linux Wed Aug 28 14:37:51 2002
@@ -12,7 +12,11 @@
uname -a
echo ' '
-echo "Gnu C " `gcc --version`
+gcc --version 2>&1| head -n 1 | grep -v gcc | awk \
+'NR==1{print "Gnu C ", $1}'
+
+gcc --version 2>&1| grep gcc | awk \
+'NR==1{print "Gnu C ", $3}'
make --version 2>&1 | awk -F, '{print $1}' | awk \
'/GNU Make/{print "Gnu make ",$NF}'
next reply other threads:[~2002-08-28 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 21:18 Steven Cole [this message]
2002-08-28 21:30 ` Thunder from the hill
2002-08-28 21:32 ` Christoph Hellwig
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=1030569489.4032.113.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®