<p dir="ltr"><br>
On 12 May 2016 9:15 a.m., "Richard Purdie" <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
><br>
> On Thu, 2016-05-12 at 17:45 +0300, Ioan-Adrian Ratiu wrote:<br>
> > On Thu, 12 May 2016 07:38:00 -0700<br>
> > Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
> ><br>
> > > On Thu, May 12, 2016 at 6:12 AM, Ioan-Adrian Ratiu <<br>
> > > <a href="mailto:adrian.ratiu@ni.com">adrian.ratiu@ni.com</a>> wrote:<br>
> > > > Building gcc-cross 4.9.3 with gcc 6 fails with the following<br>
> > > > error:<br>
> > > ><br>
> > > > error: 'const char* libc_name_p(const char*, unsigned int)'<br>
> > > > redeclared inline with 'gnu_inline' attribute<br>
> > > ><br>
> > > > This is a backport of the upstream fix.<br>
> > ><br>
> > > I have seen couple of such patches being proposed. I was of the<br>
> > > opinion to drop 4.9 from master however if we still want to<br>
> > > refresh it the I would propose that we change the SRC_URI to point<br>
> > > to<br>
> > > latest on gcc-4_9-branch and remove any backports<br>
> > > we have done since 4.9.3 release. It can also be merged into<br>
> > > krogoth.<br>
> > > Then we can latest decide if we want to keep 4.9 in<br>
> > > 2.2 release or not. Would you be able to test such a patch<br>
> ><br>
> > Actually I'm all for dropping gcc 4 from master. It's about time IMO.<br>
> ><br>
> > I need this patch to fix the build in krogoth and was just waiting<br>
> > for<br>
> > feedback on master before I sent this patch there.<br>
> ><br>
> > I'll resend for krogoth directly then :)<br>
><br>
> Since several people are hitting this and we have the patch, lets merge<br>
> it, then drop 4.9 as a followup.<br>
></p>
<p dir="ltr">I also sent a patch for gcc 5.3. It has the same issue.<br></p>
<p dir="ltr">> Cheers,<br>
><br>
> Richard<br>
> --<br>
> _______________________________________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</p>