The python-m2crypto turned to be unrelated to gcc upgrade, it was caused by
one of your patches:
https://patchwork.openembedded.org/patch/142879/
I've dropped it from master-next for now.
On Mon, Aug 21, 2017 at 4:03 PM, Khem Raj wrote:
>
> On Mon, Aug 21, 2017 at 12:12 AM Martin Jansa
> wrote
On Mon, Aug 21, 2017 at 12:12 AM Martin Jansa
wrote:
> Still reproducible without thumb:
> http://errors.yoctoproject.org/Errors/Details/152666/
>
> this might be also triggered by this upgrade:
> http://errors.yoctoproject.org/Errors/Details/152770/
>
May be passing -cpperraswarn to swig will h
Still reproducible without thumb:
http://errors.yoctoproject.org/Errors/Details/152666/
this might be also triggered by this upgrade:
http://errors.yoctoproject.org/Errors/Details/152770/
or from glibc final upgrade or something else, hard to know when exactly it
started as previous world builds
On Sun, Aug 20, 2017 at 5:31 PM Martin Jansa wrote:
> Seems like python-matplotlib reliably triggers ICE in this version of gcc:
>
> http://errors.yoctoproject.org/Errors/Details/152664/
>
> I think I haven't seen this one with 7.1.
>
Can you try disabling thumb mode and see if this works ?
>
>
Seems like python-matplotlib reliably triggers ICE in this version of gcc:
http://errors.yoctoproject.org/Errors/Details/152664/
I think I haven't seen this one with 7.1.
On Tue, Aug 15, 2017 at 7:42 AM, Khem Raj wrote:
> Drop upstreamed patches
>
> Signed-off-by: Khem Raj
> ---
> ...r-Use-s
Drop upstreamed patches
Signed-off-by: Khem Raj
---
...r-Use-stack_t-instead-of-struct-sigaltsta.patch | 81 ---
...0-replace-struct-ucontext-with-ucontext_t.patch | 149 -
.../gcc/{gcc-7.1.inc => gcc-7.2.inc} | 14 +-
.../0001-gcc-4.3.1-ARCH_FLAGS_FOR
