<div dir="ltr">Thanks Andre!<div><br></div><div>I've seen another failure probably caused by this gcc upgrade in morty-next:</div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">python-matplotlib triggers ICE:</span><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><div>src/_png.cpp: In function 'void init_png()':</div><div>src/_png.cpp:497:25: warning: variable '_png' set but not used [-Wunused-but-set-variable]</div><div> static _png_module* _png = NULL;</div><div> ^~~~</div><div>src/_png.cpp: In member function 'Py::Object _png_module::read_png(const Py::Tuple&)':</div><div>src/_png.cpp:272:1: internal compiler error: Segmentation fault</div><div> _png_module::read_png(const Py::Tuple& args)</div><div> ^~~~~~~~~~~</div><div>Please submit a full bug report,</div><div>with preprocessed source if appropriate.</div><div>See <<a href="http://gcc.gnu.org/bugs.html">http://gcc.gnu.org/bugs.html</a>> for instructions.</div><div>error: command 'i586-oe-linux-gcc' failed with exit status 1</div><div>ERROR: Function failed: do_compile (log file is located at python-matplotlib/1.1.0-r1/temp/log.do_compile.15213)</div></div><div><br></div><div>I'll try to build it with Khem's and Andre's patches only to eliminate <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">hjl/indirect/gcc-6-branch/</span><wbr style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">master changes.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 7:37 AM, Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sun, Mar 4, 2018 at 8:22 AM, Martin Jansa <<a href="mailto:martin.jansa@gmail.com">martin.jansa@gmail.com</a>> wrote:<br>
> On Sun, Mar 04, 2018 at 03:15:38PM +0100, Martin Jansa wrote:<br>
>> On Sun, Mar 04, 2018 at 11:21:32AM +0000, Richard Purdie wrote:<br>
>> > From: Juro Bystricky <<a href="mailto:juro.bystricky@intel.com">juro.bystricky@intel.com</a>><br>
>> ><br>
>> > Changed BINV and PV from 6.2.0 to 6.4.0<br>
>> > Modified BASEURI to load xz tarball instead of bz2<br>
>> ><br>
>> > Backported series of patches from <a href="https://github.com/hjl-tools/gcc.git" rel="noreferrer" target="_blank">https://github.com/hjl-tools/<wbr>gcc.git</a><br>
>> > branch /hjl/indirect/gcc-6-branch/<wbr>master which contains<br>
>> > an IA patch series for security related issues<br>
>> ><br>
>> > ubsan-fix-check-empty-string.<wbr>patch : removed, already applied<br>
>><br>
>> Very limited testing with this change in morty shows that raspberrypi3<br>
>> (cortexa7hf-neon-vfpv4) build of glibc-initial fails with:<br>
>><br>
>> configure:5344: checking for broken __attribute__((alias()))<br>
>> configure:5359: arm-oe-linux-gnueabi-gcc -march=armv7ve -marm<br>
>> -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7<br>
>> --sysroot=sysroots/<wbr>raspberrypi3-tcbootstrap<br>
>> -Werror -S conftest.c -o conftest.s 1>&5<br>
>> conftest.c:1:0: error: switch -mcpu=cortex-a7 conflicts with<br>
>> -march=armv7ve switch [-Werror]<br>
>> extern int foo (int x) __asm ("xyzzy");<br>
>><br>
>> cc1: all warnings being treated as errors<br>
>> configure:5362: $? = 1<br>
>> configure:5372: result: yes<br>
>> configure:5375: error: working alias attribute support required<br>
>><br>
>> Which is a bit strange as armv7ve was added to resolve this error with<br>
>> -mcpu=cortexa7 and -march=armv7a in:<br>
>><br>
>> commit 35392025f3236f5e5393f9cf085773<wbr>2da9a2e503<br>
>> Author: Martin Jansa <<a href="mailto:Martin.Jansa@gmail.com">Martin.Jansa@gmail.com</a>><br>
>> Date: Tue Oct 6 17:08:59 2015 +0200<br>
>><br>
>> arch-armv7ve: add tune include for armv7ve and use it from cortexa7<br>
>> and cortexa15<br>
>><br>
>> * be aware that this -march value is available only in gcc-4.9 and<br>
>> newer:<br>
>> <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57907" rel="noreferrer" target="_blank">https://gcc.gnu.org/bugzilla/<wbr>show_bug.cgi?id=57907</a><br>
>> * -mcpu=cortex15 and -mcpu=cortexa7 conflict with -march=armv7a<br>
>> We either have to stop putting -march in default CCARGS or at<br>
>> least set it compatible one like this patch does.<br>
>><br>
>> Regards,<br>
><br>
> It seems to be known regression in 6.4, with fix available here:<br>
> <a href="https://patchwork.ozlabs.org/patch/835592/" rel="noreferrer" target="_blank">https://patchwork.ozlabs.org/<wbr>patch/835592/</a><br>
<br>
</div></div>Yes. Not only was the patch submitted upstream to gcc, it was even<br>
submitted to oe-core:<br>
<br>
<a href="http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144159.html" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>pipermail/openembedded-core/<wbr>2017-November/144159.html</a><br>
<br>
Unfortunately gcc 6.4.0 was dropped from oe-core master before the fix<br>
was merged...<br>
</blockquote></div><br></div>