From: Andrew Morton <akpm@linux-foundation.org>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts/ver_linux use 'gcc -dumpversion'
Date: Wed, 21 May 2008 23:29:19 -0700 [thread overview]
Message-ID: <20080521232919.70f47341.akpm@linux-foundation.org> (raw)
In-Reply-To: <48346BA3.2050806@googlemail.com>
On Wed, 21 May 2008 20:36:19 +0200 Gabriel C <nix.or.die@googlemail.com> wrote:
>
> These magic greps and hacks in ver_linux to get the gcc version always break after some gcc releases.
>
> Since now gcc >4.3 allows compiling with '--with-pkgversion' ( which can be everything 'My Cool Gcc' or something )
> ver_linux will report random junk for these.
gcc sometimes looks like an anti-Linux plot.
> Simply use 'gcc -dumpversion' to get the gcc version which should always work.
>
> Signed-off-by: Gabriel C <nix.or.die@googlemail.com>
> ---
>
> Andrew sorry to bug you about that but
> I have no clue how is maintaining scripts/*
Depends on the script, really. Most of them are Sam stuff.
> scripts/ver_linux | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/ver_linux b/scripts/ver_linux
> index ab69ece..7ac0e30 100755
> --- a/scripts/ver_linux
> +++ b/scripts/ver_linux
> @@ -12,12 +12,9 @@ echo ' '
> uname -a
> echo ' '
>
> -gcc --version 2>&1| head -n 1 | grep -v gcc | awk \
> +gcc -dumpversion 2>&1| 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}'
including this one, I believe.
prev parent reply other threads:[~2008-05-22 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 18:36 [PATCH] scripts/ver_linux use 'gcc -dumpversion' Gabriel C
2008-05-22 6:29 ` Andrew Morton [this message]
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=20080521232919.70f47341.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.