From: Panu Matilainen <pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Mcnamara, John" <john.mcnamara-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] mk: Work around Debian/Ubuntu-specific 'gcc -dumpversion' output
Date: Tue, 24 Feb 2015 16:13:38 +0200 [thread overview]
Message-ID: <54EC8712.5060104@redhat.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2EC7480-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 02/24/2015 03:34 PM, Mcnamara, John wrote:
>> -----Original Message-----
>> From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of Panu Matilainen
>> Sent: Tuesday, February 24, 2015 10:47 AM
>> To: dev-VfR2kkLFssw@public.gmane.org
>> Subject: [dpdk-dev] [PATCH] mk: Work around Debian/Ubuntu-specific 'gcc -
>> dumpversion' output
>>
>> Commit 71f0ab1849b4fc3ca928deb566df12ca725ed150 broke compilation on some
>> versions of Debian and Ubuntu where gcc has been modified to only emit
>> MAJOR.MINOR part of the version from 'gcc -dumpversion'.
>> Drop the micro-version from gcc version comparisons to work around this,
>> it wasn't being used for anything anyway.
>>
>> -ifeq ($(shell test $(GCC_VERSION) -ge 440 && echo 1), 1)
>> +ifeq ($(shell test $(GCC_VERSION) -ge 44 && echo 1), 1)
>
> Hi,
>
> I see this has been applied already but to me this version is less clear than the previous patch version.
>
> And are we sure we won't need the micro-version. If we do, to account for something broken in a point release of gcc, we will have to redo this patch again.
Sure? I'm not enough of a fool to say yes to a question like that. I
just know it hasn't been needed before, and it seems unlikely it will be
needed later on either, gcc micro-version updates tend to be conservative.
My only interest here was to fix the version comparisons in a way that
makes gcc 5 naturally supported, and I dont really give a damn whether
there's a micro-version involved or not :) If you feel strongly about
it, send a patch. I'm not going to object.
- Panu -
prev parent reply other threads:[~2015-02-24 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 10:46 [PATCH] mk: Work around Debian/Ubuntu-specific 'gcc -dumpversion' output Panu Matilainen
[not found] ` <7529e243896615deb7d93e6080dfd2aced92bf86.1424774816.git.pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-24 10:59 ` David Marchand
[not found] ` <CALwxeUuEzJhxksjUuCNjDvpW=Z3BUb9Ac6H=GemeWKW+VVhP7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 11:14 ` Olivier MATZ
[not found] ` <54EC5D20.9090807-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2015-02-24 11:21 ` Panu Matilainen
2015-02-24 11:32 ` Thomas Monjalon
2015-02-24 13:34 ` Mcnamara, John
[not found] ` <B27915DBBA3421428155699D51E4CFE2EC7480-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-24 14:13 ` Panu Matilainen [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=54EC8712.5060104@redhat.com \
--to=pmatilai-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=john.mcnamara-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 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.