bash's read.c: http://paste.ubuntu.com/p/TMD7Z4gKxK/
libjpeg-turbo's turbojpeg.c: http://paste.ubuntu.com/p/FsV7zXnKHq/
On Sun, Aug 5, 2018 at 9:59 PM Khem Raj wrote:
>
>
> On 8/5/18 12:45 PM, Martin Jansa wrote:
> > Turned out to be related to -fno-omit-frame-pointer from DEBUG_BUILD
> > togeth
On 8/5/18 12:45 PM, Martin Jansa wrote:
> Turned out to be related to -fno-omit-frame-pointer from DEBUG_BUILD
> together with security_flags.inc together with thumb, I've sent a work
> around which works for me:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-August/153741.html
Turned out to be related to -fno-omit-frame-pointer from DEBUG_BUILD
together with security_flags.inc together with thumb, I've sent a work
around which works for me:
http://lists.openembedded.org/pipermail/openembedded-core/2018-August/153741.html
it's reproducible with gcc-8.1 as well, so it was
Sure my builds with gold did not end up in the fails for qemuarm and thumb1
the setup is very similar but I might have been lucky let me know how it
goes
On Mon, Jul 30, 2018 at 7:53 AM Martin Jansa wrote:
> I'm not sure if it was caused by this change, but I've included it from
> patchwork on F
I'm not sure if it was caused by this change, but I've included it from
patchwork on Friday and since then I've seen 3 builds getting stuck in gcc
for 50 hours.
In all 3 cases it was qemuarm (with thumb and gold enabled), twice while
building bash and once building libjpeg-turbo. I will let you kn
Signed-off-by: Khem Raj
---
...003-build-failures-with-with-cpu-xsc.patch | 61 ---
.../gcc/{gcc-8.1.inc => gcc-8.2.inc} | 11 ++--
...0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch | 0
.../0003-gcc-poison-system-directories.patch | 0
.../0004-gcc-poison-dir-extend.patch
