From: Panu Matilainen <pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: David Marchand <david.marchand-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH v2] mk: Rework gcc version detection to permit versions newer than 4.x
Date: Tue, 24 Feb 2015 12:21:59 +0200 [thread overview]
Message-ID: <54EC50C7.7050105@redhat.com> (raw)
In-Reply-To: <CALwxeUt0oDQ5nZB00mAAA=MV7nmPaLCXxos-fvPv1yMnrdP6YQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/24/2015 12:09 PM, David Marchand wrote:
> On Tue, Feb 24, 2015 at 10:50 AM, Panu Matilainen <pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
> <mailto:pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>> wrote:
>
> On 02/24/2015 11:25 AM, David Marchand wrote:
>
> Hello Panu,
>
> Looks like there is an issue with gcc 4.7 on my debian.
>
> $ make config T=x86_64-native-linuxapp-gcc && make -j8
> ../mk/toolchain/gcc/rte.__toolchain-compat.mk:46
> <http://rte.toolchain-compat.mk:46>
> <http://rte.toolchain-compat.__mk:46
> <http://rte.toolchain-compat.mk:46>>: You are using GCC < 4.x.
> This is
> neither supported, nor tested.
> ../mk/toolchain/gcc/rte.__toolchain-compat.mk:46
> <http://rte.toolchain-compat.mk:46>
> <http://rte.toolchain-compat.__mk:46
> <http://rte.toolchain-compat.mk:46>>: You are using GCC < 4.x.
> This is
> neither supported, nor tested.
>
> $ gcc -dumpversion
> 4.7
>
>
> Meh. This seems to be a Debian specific modification to gcc,
> discussed here and there including but not limited to:
> https://bugs.debian.org/cgi-__bin/bugreport.cgi?bug=759038
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759038>
> https://bugs.launchpad.net/__ubuntu/+source/gcc-4.8/+bug/__1360404
> <https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1360404>
>
> Dunno about Ubuntu, but at least Ubuntu already changed it back. But
> I guess there's no choice but to work around it anyway... Easiest
> solution is probably just to drop the micro version out, back to the
> granularity where it used to be.
>
>
> Yes, I suppose so, but then we are almost at square one :-)
Not really, the big deal about the change was to compare the version as
a regular number instead of segmented comparison. Bringing in the
micro-version was more of a side-effect than anything else, it just
seemed simpler than having to cut out major.minor specifically.
So no big loss, just mildly annoying workaround for upstream deviation :)
- Panu -
prev parent reply other threads:[~2015-02-24 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:11 [PATCH] mk: Rework gcc version detection to permit versions newer than 4.x Panu Matilainen
[not found] ` <7a06a1e8019a40d4175c6bc2e1d7e62cf956b291.1424261465.git.pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-20 14:04 ` Thomas Monjalon
2015-02-20 15:25 ` Panu Matilainen
2015-02-23 14:53 ` [PATCH v2] " Panu Matilainen
[not found] ` <e2043c84f5643ec1c1bb09d9f695c214df6e9966.1424703222.git.pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-24 2:46 ` Thomas Monjalon
2015-02-24 9:25 ` David Marchand
[not found] ` <CALwxeUsPydmOr+Rt6q4CK4uVGGp-Zq6cr+N4FxZC=sicL-HG-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 9:50 ` Panu Matilainen
[not found] ` <54EC496C.7050200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-24 10:09 ` David Marchand
[not found] ` <CALwxeUt0oDQ5nZB00mAAA=MV7nmPaLCXxos-fvPv1yMnrdP6YQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 10:21 ` David Marchand
[not found] ` <CALwxeUvM=Tsw3kYnE36c0i-+29XmnxY6MWSjwk0ESyn74xiiSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 10:36 ` Mcnamara, John
[not found] ` <B27915DBBA3421428155699D51E4CFE2EC72CF-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-24 10:44 ` David Marchand
[not found] ` <CALwxeUvV=mHpjToixfdK02zDdhndLjvTAyfHBWz2KvQLikGShg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-24 10:50 ` Bruce Richardson
2015-02-24 10:53 ` Panu Matilainen
2015-02-24 10:58 ` Mcnamara, John
2015-02-24 10:21 ` 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=54EC50C7.7050105@redhat.com \
--to=pmatilai-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=david.marchand-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@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.