From: Adrian Bunk <bunk@stusta.de>
To: "Mittal, Anuj" <anuj.mittal@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/7] libtasn1: upgrade 4.14 -> 4.15.0
Date: Thu, 19 Dec 2019 08:16:47 +0200 [thread overview]
Message-ID: <20191219061647.GB24309@localhost> (raw)
In-Reply-To: <dbe34e0d561707fdc40350bab67685f8bf7d2da9.camel@intel.com>
On Thu, Dec 19, 2019 at 06:09:40AM +0000, Mittal, Anuj wrote:
> On Thu, 2019-12-19 at 08:01 +0200, Adrian Bunk wrote:
> > On Thu, Dec 19, 2019 at 01:41:08PM +0800, Anuj Mittal wrote:
> > > Remove backported patches and explicitly pass -std=gnu99 to native
> > > CFLAGS
> > > to make sure build passes on older and still supported OSes like
> > > CentOS 7.
> > > ...
> >
> > -std=gnu99 is default with the ancient gcc on CentOS 7,
> > you could pass -std=gnu11 to bring it to the same standard
> > as current gcc.
> >
>
> info gcc for gcc 4.8.5 says:
>
> The default, if no C language dialect options are
> given, is '-std=gnu90';
>...
Sorry you are correct, I got the versions mixed up.
> Thanks,
>
> Anuj
cu
Adrian
prev parent reply other threads:[~2019-12-19 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1576733575.git.anuj.mittal@intel.com>
2019-12-19 5:41 ` [PATCH 1/7] eudev: upgrade 3.2.8 -> 3.2.9 Anuj Mittal
2019-12-19 5:41 ` [PATCH 2/7] vte: upgrade 0.58.2 -> 0.58.3 Anuj Mittal
2019-12-19 5:41 ` [PATCH 3/7] glib-networking: upgrade 2.62.1 -> 2.62.2 Anuj Mittal
2019-12-19 5:41 ` [PATCH 4/7] libsolv: upgrade 0.7.8 -> 0.7.10 Anuj Mittal
2019-12-19 5:41 ` [PATCH 5/7] stress-ng: upgrade 0.10.11 -> 0.10.13 Anuj Mittal
2019-12-19 5:41 ` [PATCH 6/7] mmc-utils: upgrade to latest revision Anuj Mittal
2019-12-19 5:41 ` [PATCH 7/7] libtasn1: upgrade 4.14 -> 4.15.0 Anuj Mittal
2019-12-19 6:01 ` Adrian Bunk
2019-12-19 6:09 ` Mittal, Anuj
2019-12-19 6:16 ` Adrian Bunk [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=20191219061647.GB24309@localhost \
--to=bunk@stusta.de \
--cc=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox