From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-4.9: fix build with gcc 6
Date: Thu, 12 May 2016 16:14:47 +0100 [thread overview]
Message-ID: <1463066087.9746.15.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160512174542.332fae80@adi-pc-linux.emea.corp.natinst.com>
On Thu, 2016-05-12 at 17:45 +0300, Ioan-Adrian Ratiu wrote:
> On Thu, 12 May 2016 07:38:00 -0700
> Khem Raj <raj.khem@gmail.com> wrote:
>
> > On Thu, May 12, 2016 at 6:12 AM, Ioan-Adrian Ratiu <
> > adrian.ratiu@ni.com> wrote:
> > > Building gcc-cross 4.9.3 with gcc 6 fails with the following
> > > error:
> > >
> > > error: 'const char* libc_name_p(const char*, unsigned int)'
> > > redeclared inline with 'gnu_inline' attribute
> > >
> > > This is a backport of the upstream fix.
> >
> > I have seen couple of such patches being proposed. I was of the
> > opinion to drop 4.9 from master however if we still want to
> > refresh it the I would propose that we change the SRC_URI to point
> > to
> > latest on gcc-4_9-branch and remove any backports
> > we have done since 4.9.3 release. It can also be merged into
> > krogoth.
> > Then we can latest decide if we want to keep 4.9 in
> > 2.2 release or not. Would you be able to test such a patch
>
> Actually I'm all for dropping gcc 4 from master. It's about time IMO.
>
> I need this patch to fix the build in krogoth and was just waiting
> for
> feedback on master before I sent this patch there.
>
> I'll resend for krogoth directly then :)
Since several people are hitting this and we have the patch, lets merge
it, then drop 4.9 as a followup.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-12 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 13:12 [PATCH] gcc-4.9: fix build with gcc 6 Ioan-Adrian Ratiu
2016-05-12 14:38 ` Khem Raj
2016-05-12 14:45 ` Ioan-Adrian Ratiu
2016-05-12 15:14 ` Richard Purdie [this message]
2016-05-12 23:30 ` Dan McGregor
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=1463066087.9746.15.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adrian.ratiu@ni.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox