[RFT] gcc7 and glibc-2.26 recipes

[RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

Hello All

I have put together recipes for upcoming gcc-7 major release as well
as glibc 2.26 release, which we would target for next release ( 2.4 )

There are several changes in gcc-7 which will need fixing packages. If you have
time to spare feel free to give it a shot and send fixes for the packages or bug
reports. Below are commits you can cherry-pick independently.

gcc7 -  http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/gcc7&id=9562231d6a37ea9c59086927bf0c854fd40b29cd

glib-2.26 - http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/glibc-2.26&id=6e91059d3f6ca0f4468ff59a2c7449be301ee100

Refer to

https://gcc.gnu.org/gcc-7/porting_to.html

For porting issues with gcc7

Cheers
-Khem

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:

> I have put together recipes for upcoming gcc-7 major release as well
> as glibc 2.26 release, which we would target for next release ( 2.4 )
>

I threw these at the autobuilder and the errors are starting to appear:

http://errors.yoctoproject.org/Errors/Latest/?filter=
eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit

Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
have your grub fix already).

Ross

[-- Attachment #2: Type: text/html, Size: 1456 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:

> I have put together recipes for upcoming gcc-7 major release as well
> as glibc 2.26 release, which we would target for next release ( 2.4 )
>

I threw these at the autobuilder and the errors are starting to appear:

http://errors.yoctoproject.org/Errors/Latest/?filter=
eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit

Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
have your grub fix already).

Ross

[-- Attachment #2: Type: text/html, Size: 1456 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:

> I have put together recipes for upcoming gcc-7 major release as well
> as glibc 2.26 release, which we would target for next release ( 2.4 )
>

I threw these at the autobuilder and the errors are starting to appear:

http://errors.yoctoproject.org/Errors/Latest/?filter=
eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit

Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
have your grub fix already).

Ross

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com> wrote:

> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>
> > I have put together recipes for upcoming gcc-7 major release as well
> > as glibc 2.26 release, which we would target for next release ( 2.4 )
> >
>
> I threw these at the autobuilder and the errors are starting to appear:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=
> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>
> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
> have your grub fix already).
>

I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
should be at a high enough stable
release to build with gcc7. So if there's a direct link to that error, I
can take a closer look.

Bruce


>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2226 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com> wrote:

> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>
> > I have put together recipes for upcoming gcc-7 major release as well
> > as glibc 2.26 release, which we would target for next release ( 2.4 )
> >
>
> I threw these at the autobuilder and the errors are starting to appear:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=
> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>
> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
> have your grub fix already).
>

I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
should be at a high enough stable
release to build with gcc7. So if there's a direct link to that error, I
can take a closer look.

Bruce


>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2226 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com> wrote:

> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>
> > I have put together recipes for upcoming gcc-7 major release as well
> > as glibc 2.26 release, which we would target for next release ( 2.4 )
> >
>
> I threw these at the autobuilder and the errors are starting to appear:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=
> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>
> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
> have your grub fix already).
>

I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
should be at a high enough stable
release to build with gcc7. So if there's a direct link to that error, I
can take a closer look.

Bruce


>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
>
>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> > I have put together recipes for upcoming gcc-7 major release as well
>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>> >
>>
>> I threw these at the autobuilder and the errors are starting to appear:
>>
>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>
>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>> have your grub fix already).
>>
>
> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
> should be at a high enough stable
> release to build with gcc7. So if there's a direct link to that error, I
> can take a closer look.
>

And sure enough, after I sent that the error page with linux-yocto finally
wheezed in.

I see that it was the 4.1 kernel, which is expected to fail. I haven't
looked into backporting gcc7 fixes
that far, but if there's demand, it is something we can consider/look into.

Bruce


>
> Bruce
>
>
>>
>> Ross
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 3564 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
>
>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> > I have put together recipes for upcoming gcc-7 major release as well
>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>> >
>>
>> I threw these at the autobuilder and the errors are starting to appear:
>>
>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>
>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>> have your grub fix already).
>>
>
> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
> should be at a high enough stable
> release to build with gcc7. So if there's a direct link to that error, I
> can take a closer look.
>

And sure enough, after I sent that the error page with linux-yocto finally
wheezed in.

I see that it was the 4.1 kernel, which is expected to fail. I haven't
looked into backporting gcc7 fixes
that far, but if there's demand, it is something we can consider/look into.

Bruce


>
> Bruce
>
>
>>
>> Ross
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 3564 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
>
>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> > I have put together recipes for upcoming gcc-7 major release as well
>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>> >
>>
>> I threw these at the autobuilder and the errors are starting to appear:
>>
>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>
>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>> have your grub fix already).
>>
>
> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
> should be at a high enough stable
> release to build with gcc7. So if there's a direct link to that error, I
> can take a closer look.
>

And sure enough, after I sent that the error page with linux-yocto finally
wheezed in.

I see that it was the 4.1 kernel, which is expected to fail. I haven't
looked into backporting gcc7 fixes
that far, but if there's demand, it is something we can consider/look into.

Bruce


>
> Bruce
>
>
>>
>> Ross
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Sun, Apr 23, 2017 at 5:31 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
>
>
> On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>>
>>
>>
>> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
>> wrote:
>>>
>>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> > I have put together recipes for upcoming gcc-7 major release as well
>>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>>> >
>>>
>>> I threw these at the autobuilder and the errors are starting to appear:
>>>
>>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>>
>>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>>> have your grub fix already).
>>
>>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

I think we will need them on 4.1 too but lets wait for gkh to apply them first.

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Sun, Apr 23, 2017 at 5:31 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
>
>
> On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>>
>>
>>
>> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
>> wrote:
>>>
>>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> > I have put together recipes for upcoming gcc-7 major release as well
>>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>>> >
>>>
>>> I threw these at the autobuilder and the errors are starting to appear:
>>>
>>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>>
>>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>>> have your grub fix already).
>>
>>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

I think we will need them on 4.1 too but lets wait for gkh to apply them first.

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Sun, Apr 23, 2017 at 5:31 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
>
>
> On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>>
>>
>>
>> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.burton@intel.com>
>> wrote:
>>>
>>> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> > I have put together recipes for upcoming gcc-7 major release as well
>>> > as glibc 2.26 release, which we would target for next release ( 2.4 )
>>> >
>>>
>>> I threw these at the autobuilder and the errors are starting to appear:
>>>
>>> http://errors.yoctoproject.org/Errors/Latest/?filter=
>>> eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>>>
>>> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
>>> have your grub fix already).
>>
>>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

I think we will need them on 4.1 too but lets wait for gkh to apply them first.

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Sun, Apr 23, 2017 at 3:04 PM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> I have put together recipes for upcoming gcc-7 major release as well
>> as glibc 2.26 release, which we would target for next release ( 2.4 )
>
>
> I threw these at the autobuilder and the errors are starting to appear:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>
> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
> have your grub fix already).

There are few other fixes that needs to be in there. glibc and gcc recipes
also needed some fixes. I have pushed the whole series to kraj/master
branch on contrib repo

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master

give it a whirl again.

>
> Ross

Re: [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Sun, Apr 23, 2017 at 3:04 PM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 16 April 2017 at 16:50, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> I have put together recipes for upcoming gcc-7 major release as well
>> as glibc 2.26 release, which we would target for next release ( 2.4 )
>
>
> I threw these at the autobuilder and the errors are starting to appear:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=eddf6362e17899113f10cf53ed0db8a4b13ff3fc&type=commit
>
> Repeated diffutils and rpcbind failures, but linux-yocto and grub too (I
> have your grub fix already).

There are few other fixes that needs to be in there. glibc and gcc recipes
also needed some fixes. I have pushed the whole series to kraj/master
branch on contrib repo

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master

give it a whirl again.

>
> Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
>
> give it a whirl again.
>

All merged, I'll fire in a moment.

Thanks Khem!

Ross

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
>
> give it a whirl again.
>

All merged, I'll fire in a moment.

Thanks Khem!

Ross

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
>
> give it a whirl again.
>

All merged, I'll fire in a moment.

Thanks Khem!

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

The updated glibc recipe doesn't appear to be very happy:
https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio

Ross

[-- Attachment #2: Type: text/html, Size: 855 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

The updated glibc recipe doesn't appear to be very happy:
https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio

Ross

[-- Attachment #2: Type: text/html, Size: 855 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

The updated glibc recipe doesn't appear to be very happy:
https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/237/steps/BuildImages/logs/stdio
shows that the old elfutils in meta-gpl2 doesn't like gcc7 either.

Ross

[-- Attachment #2: Type: text/html, Size: 879 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/237/steps/BuildImages/logs/stdio
shows that the old elfutils in meta-gpl2 doesn't like gcc7 either.

Ross

[-- Attachment #2: Type: text/html, Size: 879 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/237/steps/BuildImages/logs/stdio
shows that the old elfutils in meta-gpl2 doesn't like gcc7 either.

Ross

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

| kernel/built-in.o: In function `update_wall_time':
| (.text+0x65ecc): undefined reference to `____ilog2_NaN'

I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
update the BSP with some fixes you've made?

Ross

[-- Attachment #2: Type: text/html, Size: 1796 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

| kernel/built-in.o: In function `update_wall_time':
| (.text+0x65ecc): undefined reference to `____ilog2_NaN'

I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
update the BSP with some fixes you've made?

Ross

[-- Attachment #2: Type: text/html, Size: 1796 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>> should be at a high enough stable
>> release to build with gcc7. So if there's a direct link to that error, I
>> can take a closer look.
>>
>
> And sure enough, after I sent that the error page with linux-yocto finally
> wheezed in.
>
> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

| kernel/built-in.o: In function `update_wall_time':
| (.text+0x65ecc): undefined reference to `____ilog2_NaN'

I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
update the BSP with some fixes you've made?

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>

grub is still failing on musl on the autobuilder:

| ../../grub-2.00/grub-core/video/i386/pc/vbe.c: In function
'vbe2videoinfo':
| ../../grub-2.00/grub-core/video/i386/pc/vbe.c:882:28: error: this
statement may fall through [-Werror=implicit-fallthrough=]
|        mode_info->mode_type |= GRUB_VIDEO_MODE_TYPE_CGA;
|        ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~

https://autobuilder.yocto.io/builders/nightly-musl/builds/243/steps/BuildImages/logs/stdio

Ross

[-- Attachment #2: Type: text/html, Size: 1367 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>

grub is still failing on musl on the autobuilder:

| ../../grub-2.00/grub-core/video/i386/pc/vbe.c: In function
'vbe2videoinfo':
| ../../grub-2.00/grub-core/video/i386/pc/vbe.c:882:28: error: this
statement may fall through [-Werror=implicit-fallthrough=]
|        mode_info->mode_type |= GRUB_VIDEO_MODE_TYPE_CGA;
|        ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~

https://autobuilder.yocto.io/builders/nightly-musl/builds/243/steps/BuildImages/logs/stdio

Ross

[-- Attachment #2: Type: text/html, Size: 1367 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 06:45, Khem Raj <raj.khem@gmail.com> wrote:

> There are few other fixes that needs to be in there. glibc and gcc recipes
> also needed some fixes. I have pushed the whole series to kraj/master
> branch on contrib repo
>

grub is still failing on musl on the autobuilder:

| ../../grub-2.00/grub-core/video/i386/pc/vbe.c: In function
'vbe2videoinfo':
| ../../grub-2.00/grub-core/video/i386/pc/vbe.c:882:28: error: this
statement may fall through [-Werror=implicit-fallthrough=]
|        mode_info->mode_type |= GRUB_VIDEO_MODE_TYPE_CGA;
|        ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~

https://autobuilder.yocto.io/builders/nightly-musl/builds/243/steps/BuildImages/logs/stdio

Ross

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:

> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>

Or ideally telling myself to update meta-intel for the fixes that Saul has
already merged...

Ross

[-- Attachment #2: Type: text/html, Size: 676 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:

> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>

Or ideally telling myself to update meta-intel for the fixes that Saul has
already merged...

Ross

[-- Attachment #2: Type: text/html, Size: 676 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:

> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>

Or ideally telling myself to update meta-intel for the fixes that Saul has
already merged...

Ross

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Mon, Apr 24, 2017 at 6:29 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>>> should be at a high enough stable
>>> release to build with gcc7. So if there's a direct link to that error,
>>> I can take a closer look.
>>>
>>
>> And sure enough, after I sent that the error page with linux-yocto
>> finally wheezed in.
>>
>> I see that it was the 4.1 kernel, which is expected to fail. I haven't
>> looked into backporting gcc7 fixes
>> that far, but if there's demand, it is something we can consider/look
>> into.
>>
>
> | kernel/built-in.o: In function `update_wall_time':
> | (.text+0x65ecc): undefined reference to `____ilog2_NaN'
>
> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>


4.9 would need fixes as well, or be on a -stable that contains the fix:

% git tag --contains 85f687708c811563df33c70c9cec9b5c2733acf8
v4.9.18
v4.9.19
v4.9.20
v4.9.21

Cheers,

Bruce


>
> Ross
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2987 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Mon, Apr 24, 2017 at 6:29 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>>> should be at a high enough stable
>>> release to build with gcc7. So if there's a direct link to that error,
>>> I can take a closer look.
>>>
>>
>> And sure enough, after I sent that the error page with linux-yocto
>> finally wheezed in.
>>
>> I see that it was the 4.1 kernel, which is expected to fail. I haven't
>> looked into backporting gcc7 fixes
>> that far, but if there's demand, it is something we can consider/look
>> into.
>>
>
> | kernel/built-in.o: In function `update_wall_time':
> | (.text+0x65ecc): undefined reference to `____ilog2_NaN'
>
> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>


4.9 would need fixes as well, or be on a -stable that contains the fix:

% git tag --contains 85f687708c811563df33c70c9cec9b5c2733acf8
v4.9.18
v4.9.19
v4.9.20
v4.9.21

Cheers,

Bruce


>
> Ross
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2987 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

On Mon, Apr 24, 2017 at 6:29 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>
>> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto
>>> should be at a high enough stable
>>> release to build with gcc7. So if there's a direct link to that error,
>>> I can take a closer look.
>>>
>>
>> And sure enough, after I sent that the error page with linux-yocto
>> finally wheezed in.
>>
>> I see that it was the 4.1 kernel, which is expected to fail. I haven't
>> looked into backporting gcc7 fixes
>> that far, but if there's demand, it is something we can consider/look
>> into.
>>
>
> | kernel/built-in.o: In function `update_wall_time':
> | (.text+0x65ecc): undefined reference to `____ilog2_NaN'
>
> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
> update the BSP with some fixes you've made?
>


4.9 would need fixes as well, or be on a -stable that contains the fix:

% git tag --contains 85f687708c811563df33c70c9cec9b5c2733acf8
v4.9.18
v4.9.19
v4.9.20
v4.9.21

Cheers,

Bruce


>
> Ross
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

On Mon, Apr 24, 2017 at 7:11 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:
>
>> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
>> update the BSP with some fixes you've made?
>>
>
> Or ideally telling myself to update meta-intel for the fixes that Saul has
> already merged...
>

ooops. I should read all the way to the bottom of the thread :D

Bruce


>
> Ross
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 1669 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

On Mon, Apr 24, 2017 at 7:11 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:
>
>> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
>> update the BSP with some fixes you've made?
>>
>
> Or ideally telling myself to update meta-intel for the fixes that Saul has
> already merged...
>

ooops. I should read all the way to the bottom of the thread :D

Bruce


>
> Ross
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 1669 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Bruce Ashfield]

On Mon, Apr 24, 2017 at 7:11 AM, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 24 April 2017 at 11:29, Burton, Ross <ross.burton@intel.com> wrote:
>
>> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to
>> update the BSP with some fixes you've made?
>>
>
> Or ideally telling myself to update meta-intel for the fixes that Saul has
> already merged...
>

ooops. I should read all the way to the bottom of the thread :D

Bruce


>
> Ross
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

On 24 April 2017 at 10:47, Burton, Ross <ross.burton@intel.com> wrote:

> The updated glibc recipe doesn't appear to be very happy:
> https://autobuilder.yocto.io/builders/buildtools/
> builds/240/steps/BuildImages/logs/stdio
>

Note that every nativesdk-glibc build is failing like this, so that's SDKs
broken.

Ross

[-- Attachment #2: Type: text/html, Size: 824 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

On 24 April 2017 at 10:47, Burton, Ross <ross.burton@intel.com> wrote:

> The updated glibc recipe doesn't appear to be very happy:
> https://autobuilder.yocto.io/builders/buildtools/
> builds/240/steps/BuildImages/logs/stdio
>

Note that every nativesdk-glibc build is failing like this, so that's SDKs
broken.

Ross

[-- Attachment #2: Type: text/html, Size: 824 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 10:47, Burton, Ross <ross.burton@intel.com> wrote:

> The updated glibc recipe doesn't appear to be very happy:
> https://autobuilder.yocto.io/builders/buildtools/
> builds/240/steps/BuildImages/logs/stdio
>

Note that every nativesdk-glibc build is failing like this, so that's SDKs
broken.

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Mon, Apr 24, 2017 at 8:54 AM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 24 April 2017 at 10:47, Burton, Ross <ross.burton@intel.com> wrote:
>>
>> The updated glibc recipe doesn't appear to be very happy:
>> https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio
>
>
> Note that every nativesdk-glibc build is failing like this, so that's SDKs
> broken.

thanks, yes I haven't been testing SDK yet, whats the gcc version on
your build host ?

>
> Ross

Re: [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Mon, Apr 24, 2017 at 8:54 AM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 24 April 2017 at 10:47, Burton, Ross <ross.burton@intel.com> wrote:
>>
>> The updated glibc recipe doesn't appear to be very happy:
>> https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio
>
>
> Note that every nativesdk-glibc build is failing like this, so that's SDKs
> broken.

thanks, yes I haven't been testing SDK yet, whats the gcc version on
your build host ?

>
> Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

lttng-modules fails:

In function 'lib_ring_buffer_align',
    inlined from 'lib_ring_buffer_try_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
    inlined from 'lib_ring_buffer_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
    inlined from 'lttng_event_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
error: call to '__compiletime_assert_269' declared with attribute error:
BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
((size_of_type) - 1))
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
                                      ^

Suggestions welcome :)

Ross

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

lttng-modules fails:

In function 'lib_ring_buffer_align',
    inlined from 'lib_ring_buffer_try_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
    inlined from 'lib_ring_buffer_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
    inlined from 'lttng_event_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
error: call to '__compiletime_assert_269' declared with attribute error:
BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
((size_of_type) - 1))
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
                                      ^

Suggestions welcome :)

Ross

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:

> All merged, I'll fire in a moment.
>

lttng-modules fails:

In function 'lib_ring_buffer_align',
    inlined from 'lib_ring_buffer_try_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
    inlined from 'lib_ring_buffer_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
    inlined from 'lttng_event_reserve' at
TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
error: call to '__compiletime_assert_269' declared with attribute error:
BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
((size_of_type) - 1))
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
                                      ^

Suggestions welcome :)

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

On 24 April 2017 at 17:10, Khem Raj <raj.khem@gmail.com> wrote:

> thanks, yes I haven't been testing SDK yet, whats the gcc version on
> your build host ?
>

It's failing across the autobuilder so I'd suggest it's not specific to a
gcc version.

It also breaks on my personal machine, which is Debian Jessie(ish) with gcc
4.9.2

Ross

[-- Attachment #2: Type: text/html, Size: 831 bytes --]

Re: [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

On 24 April 2017 at 17:10, Khem Raj <raj.khem@gmail.com> wrote:

> thanks, yes I haven't been testing SDK yet, whats the gcc version on
> your build host ?
>

It's failing across the autobuilder so I'd suggest it's not specific to a
gcc version.

It also breaks on my personal machine, which is Debian Jessie(ish) with gcc
4.9.2

Ross

[-- Attachment #2: Type: text/html, Size: 831 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 17:10, Khem Raj <raj.khem@gmail.com> wrote:

> thanks, yes I haven't been testing SDK yet, whats the gcc version on
> your build host ?
>

It's failing across the autobuilder so I'd suggest it's not specific to a
gcc version.

It also breaks on my personal machine, which is Debian Jessie(ish) with gcc
4.9.2

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Nathan Lynch]

"Burton, Ross" <ross.burton@intel.com> writes:

> On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:
>
>> All merged, I'll fire in a moment.
>>
>
> lttng-modules fails:
>
> In function 'lib_ring_buffer_align',
>     inlined from 'lib_ring_buffer_try_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
>     inlined from 'lib_ring_buffer_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
>     inlined from 'lttng_event_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
> TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
> error: call to '__compiletime_assert_269' declared with attribute error:
> BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
> ((size_of_type) - 1))
>   _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
>                                       ^
>
> Suggestions welcome :)


Does adding this patch to lttng-modules work around it?


diff --git a/lib/align.h b/lib/align.h
index 5b91ae87410b..5e134cd485fe 100644
--- a/lib/align.h
+++ b/lib/align.h
@@ -48,7 +48,7 @@
  */
 #define offset_align(align_drift, alignment)				       \
 	({								       \
-		BUILD_RUNTIME_BUG_ON((alignment) == 0			       \
+		BUG_ON((alignment) == 0					       \
 				   || ((alignment) & ((alignment) - 1)));      \
 		(((alignment) - (align_drift)) & ((alignment) - 1));	       \
 	})
@@ -63,7 +63,7 @@
  */
 #define offset_align_floor(align_drift, alignment)			       \
 	({								       \
-		BUILD_RUNTIME_BUG_ON((alignment) == 0			       \
+		BUG_ON((alignment) == 0					       \
 				   || ((alignment) & ((alignment) - 1)));      \
 		(((align_drift) - (alignment)) & ((alignment) - 1));	       \
 	})

Re: [yocto] [RFT] gcc7 and glibc-2.26 recipes

[Nathan Lynch]

"Burton, Ross" <ross.burton@intel.com> writes:

> On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:
>
>> All merged, I'll fire in a moment.
>>
>
> lttng-modules fails:
>
> In function 'lib_ring_buffer_align',
>     inlined from 'lib_ring_buffer_try_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
>     inlined from 'lib_ring_buffer_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
>     inlined from 'lttng_event_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
> TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
> error: call to '__compiletime_assert_269' declared with attribute error:
> BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
> ((size_of_type) - 1))
>   _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
>                                       ^
>
> Suggestions welcome :)


Does adding this patch to lttng-modules work around it?


diff --git a/lib/align.h b/lib/align.h
index 5b91ae87410b..5e134cd485fe 100644
--- a/lib/align.h
+++ b/lib/align.h
@@ -48,7 +48,7 @@
  */
 #define offset_align(align_drift, alignment)				       \
 	({								       \
-		BUILD_RUNTIME_BUG_ON((alignment) == 0			       \
+		BUG_ON((alignment) == 0					       \
 				   || ((alignment) & ((alignment) - 1)));      \
 		(((alignment) - (align_drift)) & ((alignment) - 1));	       \
 	})
@@ -63,7 +63,7 @@
  */
 #define offset_align_floor(align_drift, alignment)			       \
 	({								       \
-		BUILD_RUNTIME_BUG_ON((alignment) == 0			       \
+		BUG_ON((alignment) == 0					       \
 				   || ((alignment) & ((alignment) - 1)));      \
 		(((align_drift) - (alignment)) & ((alignment) - 1));	       \
 	})

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

There's demand in that the gcc7 merge is blocking on either kernel 4.1
being fixed or removed.  Your choice. :)

Ross

[-- Attachment #2: Type: text/html, Size: 786 bytes --]

Re: [oe] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

There's demand in that the gcc7 merge is blocking on either kernel 4.1
being fixed or removed.  Your choice. :)

Ross

[-- Attachment #2: Type: text/html, Size: 786 bytes --]

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> I see that it was the 4.1 kernel, which is expected to fail. I haven't
> looked into backporting gcc7 fixes
> that far, but if there's demand, it is something we can consider/look into.
>

There's demand in that the gcc7 merge is blocking on either kernel 4.1
being fixed or removed.  Your choice. :)

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Mon, Apr 24, 2017 at 12:13 PM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:
>>
>> All merged, I'll fire in a moment.
>
>
> lttng-modules fails:
>
> In function 'lib_ring_buffer_align',
>     inlined from 'lib_ring_buffer_try_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
>     inlined from 'lib_ring_buffer_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
>     inlined from 'lttng_event_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
> TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
> error: call to '__compiletime_assert_269' declared with attribute error:
> BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
> ((size_of_type) - 1))
>   _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
>                                       ^
>
> Suggestions welcome :)

my builds have been primarily arm/aarch64/x86_64 only thus far
probably BUILD_BUG_ON  can be replaced may be with BUG_ON

>
> Ross

Re: [RFT] gcc7 and glibc-2.26 recipes

[Khem Raj]

On Mon, Apr 24, 2017 at 12:13 PM, Burton, Ross <ross.burton@intel.com> wrote:
>
> On 24 April 2017 at 10:09, Burton, Ross <ross.burton@intel.com> wrote:
>>
>> All merged, I'll fire in a moment.
>
>
> lttng-modules fails:
>
> In function 'lib_ring_buffer_align',
>     inlined from 'lib_ring_buffer_try_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:118:3,
>     inlined from 'lib_ring_buffer_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lib/ringbuffer/frontend_api.h:179:6,
>     inlined from 'lttng_event_reserve' at
> TOPDIR/tmp/work/qemumips-poky-linux/lttng-modules/2.9.1-r0/lttng-modules-2.9.1/lttng-ring-buffer-metadata-client.h:317:6:
> TOPDIR/tmp/work-shared/qemumips/kernel-source/include/linux/compiler.h:518:38:
> error: call to '__compiletime_assert_269' declared with attribute error:
> BUILD_BUG_ON failed: (size_of_type) == 0 || ((size_of_type) &
> ((size_of_type) - 1))
>   _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
>                                       ^
>
> Suggestions welcome :)

my builds have been primarily arm/aarch64/x86_64 only thus far
probably BUILD_BUG_ON  can be replaced may be with BUG_ON

>
> Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

On 24 April 2017 at 23:00, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Does adding this patch to lttng-modules work around it?
>

Yes, it fixes the build here.  I'll throw it at the autobuilder now, can
you send a patch with a commit message that isn't "someone told me to try
this"? :)

Ross

[-- Attachment #2: Type: text/html, Size: 783 bytes --]

Re: [yocto] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

On 24 April 2017 at 23:00, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Does adding this patch to lttng-modules work around it?
>

Yes, it fixes the build here.  I'll throw it at the autobuilder now, can
you send a patch with a commit message that isn't "someone told me to try
this"? :)

Ross

[-- Attachment #2: Type: text/html, Size: 783 bytes --]

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 24 April 2017 at 23:00, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Does adding this patch to lttng-modules work around it?
>

Yes, it fixes the build here.  I'll throw it at the autobuilder now, can
you send a patch with a commit message that isn't "someone told me to try
this"? :)

Ross

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Nathan Lynch]

"Burton, Ross" <ross.burton@intel.com> writes:

> On 24 April 2017 at 23:00, Nathan Lynch <nathan_lynch@mentor.com> wrote:
>
>> Does adding this patch to lttng-modules work around it?
>>
>
> Yes, it fixes the build here.  I'll throw it at the autobuilder now, can
> you send a patch with a commit message that isn't "someone told me to try
> this"? :)

Done:
http://lists.openembedded.org/pipermail/openembedded-core/2017-April/136086.html

Re: [yocto] [RFT] gcc7 and glibc-2.26 recipes

[Nathan Lynch]

"Burton, Ross" <ross.burton@intel.com> writes:

> On 24 April 2017 at 23:00, Nathan Lynch <nathan_lynch@mentor.com> wrote:
>
>> Does adding this patch to lttng-modules work around it?
>>
>
> Yes, it fixes the build here.  I'll throw it at the autobuilder now, can
> you send a patch with a commit message that isn't "someone told me to try
> this"? :)

Done:
http://lists.openembedded.org/pipermail/openembedded-core/2017-April/136086.html

Re: [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 195 bytes --]

On 25 April 2017 at 23:35, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Done:
> http://lists.openembedded.org/pipermail/openembedded-core/
> 2017-April/136086.html
>

Thanks!

Ross

[-- Attachment #2: Type: text/html, Size: 737 bytes --]

Re: [yocto] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 195 bytes --]

On 25 April 2017 at 23:35, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Done:
> http://lists.openembedded.org/pipermail/openembedded-core/
> 2017-April/136086.html
>

Thanks!

Ross

[-- Attachment #2: Type: text/html, Size: 737 bytes --]

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

[Burton, Ross]

On 25 April 2017 at 23:35, Nathan Lynch <nathan_lynch@mentor.com> wrote:

> Done:
> http://lists.openembedded.org/pipermail/openembedded-core/
> 2017-April/136086.html
>

Thanks!

Ross