From: Trevor Woerner <twoerner@gmail.com>
To: "João Gonçalves" <joao.jfgoncalves@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: qemu segmentation fault on gobject-introspection
Date: Fri, 29 Mar 2019 07:51:38 -0400 [thread overview]
Message-ID: <20190329115138.GA8353@linux-uys3> (raw)
In-Reply-To: <CAHXEV+mfcxpGekquU2NFxLcmtw1gTAtp9eR3FYsXfdURW9YyfQ@mail.gmail.com>
On Wed 2019-02-20 @ 11:50:45 PM, João Gonçalves wrote:
> Hello,
> when trying to migrate my build to master branch of oe layers I got this
> qemu segmentation fault during gobject-introspection.
> Does anyone have any clue on this?
>
> Thank you,
> João Gonçalves
>
> | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> | Segmentation fault (core dumped)
> | If the above error message is about missing .so libraries, then setting
> up GIR_EXTRA_LIBS_PATH in the recipe should help.
> | (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
> | Command
> '['/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper',
> '/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/GLib-2.0',
> '--introspect-dump=/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/functions.txt,/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/dump.xml']'
> returned non-zero exit status 1.
> | ninja: build stopped: subcommand failed.
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at
> /home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/temp/log.do_compile.20894)
> ERROR: Task
> (/home/joao/poky_imx6/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile)
> failed with exit code '1'
Is it possible you're building your image with the gold linker? I.e.
DISTRO_FEATURES_append = " ld-is-gold"
It looks like there's a problem using the gold linker with 32-bit ARM targets.
Everything seems to work with the regular/default bfd linker is used instead.
Please see:
http://lists.openembedded.org/pipermail/openembedded-core/2019-March/280537.html
https://patchwork.openembedded.org/patch/159874/
Best regards,
Trevor
prev parent reply other threads:[~2019-03-29 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 23:50 qemu segmentation fault on gobject-introspection João Gonçalves
2019-02-21 1:47 ` Khem Raj
2019-03-29 11:51 ` Trevor Woerner [this message]
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=20190329115138.GA8353@linux-uys3 \
--to=twoerner@gmail.com \
--cc=joao.jfgoncalves@gmail.com \
--cc=yocto@yoctoproject.org \
/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.