All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: State of OE World, 2019-03-16
Date: Wed, 27 Mar 2019 17:17:54 +0100	[thread overview]
Message-ID: <20190327161754.GD1598@jama> (raw)
In-Reply-To: <CAMKF1so7w4i4Kw-ymWayPx1Z_mmetRKcNeyb9pADFZwDY=jqmw@mail.gmail.com>

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

On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
> 
> == Failed tasks 2019-03-16 ==
> 
> INFO: jenkins-job.sh-1.8.45 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> 
>     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile

I was hit by this one as well on some arm targets.

http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log

shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper

| qemu: uncaught target signal 11 (Segmentation fault) - core dumped
| /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"

The interesting part is that this happens only when glibc is built with gold enabled.

I've put a bit more details in temporary work-around here:
https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743

I'm comparing qemuarm glibc build with bfd and gold to see if there is some
significant difference which might cause this and I plan to flash some small
image on my targets to see if libc is broken in runtime as well or only when
running inside qemu-arm.

Is anyone else seeing this as well?

Regards,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  parent reply	other threads:[~2019-03-27 16:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 15:26 State of OE World, 2019-03-16 Khem Raj
2019-03-17 16:46 ` akuster808
2019-03-17 19:56   ` Khem Raj
2019-03-27 16:17 ` Martin Jansa [this message]
2019-03-27 16:35   ` Martin Jansa
2019-03-27 20:39     ` Martin Jansa
2019-03-27 22:32       ` glibc broken when linked with gold Was: " Martin Jansa
2019-03-27 22:32         ` glibc broken when linked with gold Was: [oe] " Martin Jansa
2019-03-28  5:08         ` glibc broken when linked with gold Was: " Khem Raj
2019-03-28  5:08           ` glibc broken when linked with gold Was: [oe] " Khem Raj
2019-03-28 14:40           ` glibc broken when linked with gold Was: " Martin Jansa
2019-03-28 14:40             ` glibc broken when linked with gold Was: [oe] " Martin Jansa
2019-03-29 11:37             ` [OE-core] glibc broken when linked with gold Was: " Trevor Woerner
2019-03-29 11:37               ` glibc broken when linked with gold Was: [oe] " Trevor Woerner
2019-03-29 14:14               ` [OE-core] glibc broken when linked with gold Was: " Trevor Woerner
2019-03-29 14:14                 ` glibc broken when linked with gold Was: [oe] " Trevor Woerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190327161754.GD1598@jama \
    --to=martin.jansa@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.