qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: linux-user static build broken
Date: Wed, 26 Aug 2020 09:44:42 +0100	[thread overview]
Message-ID: <20200826084442.GH168515@redhat.com> (raw)
In-Reply-To: <40710b94-094f-f91a-6ddb-94e51199a8c3@vivier.eu>

On Tue, Aug 25, 2020 at 10:36:13PM +0200, Laurent Vivier wrote:
> Hi,
> 
> since we have switched to meson, the statically linked binaries of qemu
> linux-user are broken:
> 
> cd $OBJ
> $SRC/configure --static --target-list=m68k-linux-user
> make
> ./qemu-m68k
> Segmentation fault (core dumped)
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7bd6833 in __dcigettext ()
> (gdb) bt
> #0  0x00007ffff7bd6833 in __dcigettext ()
> #1  0x00007ffff7bd5352 in __assert_fail ()
> #2  0x00007ffff7c4d74c in _dl_relocate_static_pie ()
> #3  0x00007ffff7bc713e in __libc_start_main ()
> #4  0x00007ffff7a0029e in _start ()
> 
> If I build with --disable-pie it works again.
> 
> Any idea?

I'd suggest checking the compiler args used with v5.1.0 vs git master
and see if any flags related to PIE or similar changed. I already found
one bug wrt PIE on Windows builds this way.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2020-08-26  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 20:36 linux-user static build broken Laurent Vivier
2020-08-25 21:22 ` Peter Maydell
2020-08-26  8:44 ` Daniel P. Berrangé [this message]
2020-08-26  8:51   ` Laurent Vivier
2020-08-26  9:08     ` Paolo Bonzini
2020-08-26 10:53       ` Laurent Vivier
2020-08-26 11:35         ` Paolo Bonzini

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=20200826084442.GH168515@redhat.com \
    --to=berrange@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).