Richard Purdie writes:
> On Fri, 2017-09-01 at 12:14 -0700, akuster wrote:
>> On 08/29/2017 01:03 AM, Richard Purdie wrote:
>> >
>> > On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
>> > >
>> > > I've recently updated my host system to Fedora 26, which has GCC
>> > > 7.
>> > >
>>
On Fri, 2017-09-01 at 12:14 -0700, akuster wrote:
>
> On 08/29/2017 01:03 AM, Richard Purdie wrote:
> >
> > On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
> > >
> > > I've recently updated my host system to Fedora 26, which has GCC
> > > 7.
> > >
> > > This seems to be causing
On 08/29/2017 01:03 AM, Richard Purdie wrote:
On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
I've recently updated my host system to Fedora 26, which has GCC 7.
This seems to be causing some issues on Pyro, where I have a -native
recipe that is built with my system's g++ and
On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
> I've recently updated my host system to Fedora 26, which has GCC 7.
>
> This seems to be causing some issues on Pyro, where I have a -native
> recipe that is built with my system's g++ and ends up generating a
> binary with the foll
Hi,
You could try to build your own uninative:
bitbake uninative-tarball
and use your own uninative:
update: poky/meta/conf/distro/include/yocto-uninative.inc
Or stop using uninative.
But I'm also curios why native built with newer gcc is not using glibc
from uninative (older glibc than gcc 7
I've recently updated my host system to Fedora 26, which has GCC 7.
This seems to be causing some issues on Pyro, where I have a -native
recipe that is built with my system's g++ and ends up generating a
binary with the following symbol:
DF *UND* GLIBC
