From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id C0E14ADAF for ; Tue, 24 Feb 2015 12:21:53 +0100 (CET) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1OBLpvP012798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 24 Feb 2015 06:21:51 -0500 Received: from localhost.localdomain (vpn1-4-61.ams2.redhat.com [10.36.4.61]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1OBLnxv025662; Tue, 24 Feb 2015 06:21:50 -0500 Message-ID: <54EC5ECD.4060707@redhat.com> Date: Tue, 24 Feb 2015 13:21:49 +0200 From: Panu Matilainen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Olivier MATZ , David Marchand References: <7529e243896615deb7d93e6080dfd2aced92bf86.1424774816.git.pmatilai@redhat.com> <54EC5D20.9090807@6wind.com> In-Reply-To: <54EC5D20.9090807@6wind.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] mk: Work around Debian/Ubuntu-specific 'gcc -dumpversion' output X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 11:21:54 -0000 On 02/24/2015 01:14 PM, Olivier MATZ wrote: > Hi Panu, David, > > On 02/24/2015 11:59 AM, David Marchand wrote: >>> >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. >>> > >>> >Signed-off-by: Panu Matilainen >> >> ack (and works with my debian gcc). >> > > One question: will it work with a version like with 2 digits > for major or minor like 4.10.0 or 10.0.0? > (or maybe it cannot happen with gcc naming conventions?) The original change mentions this: This [...] scheme would run into trouble if gcc ever went to two-digit version segments, but that hasn't happened in the last 10+ years so it seems like a safe assumption. ...but that's not entirely accurate, 4.10.0 would be a problem but 10.0.0 not. - Panu -