From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10726] Current libglib2.mk creates broken libglib2 binary when using glibc 2.26
Date: Mon, 05 Feb 2018 10:24:48 +0000 [thread overview]
Message-ID: <bug-10726-163-z3LC4wxpli@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10726-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10726
--- Comment #1 from Matthias <porto.rio@gmx.net> ---
Please find attached a buildroot-config for a minimal qemu image which
reproduces the problem.
It was created and tested with the sequence below.
> cd tmp/
> tar xvf ../dl/buildroot-2017.11.2.tar.bz2
> make qemu_arm_versatile_defconfig
> make menuconfig
[activate eudev, glibc and udisks]
> make
> qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user
# /usr/libexec/udisks-daemon
Invalid byte sequence in conversion input
(udisks-daemon:112): GLib-CRITICAL **: g_error_new_literal: assertion 'message
!= NULL' failed
Segmentation fault
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-02-05 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 10:44 [Buildroot] [Bug 10726] New: Current libglib2.mk creates broken libglib2 binary when using glibc 2.26 bugzilla at busybox.net
2018-02-05 10:24 ` bugzilla at busybox.net [this message]
2018-02-05 10:38 ` [Buildroot] [Bug 10726] " bugzilla at busybox.net
2018-02-05 16:40 ` bugzilla at busybox.net
2018-02-25 21:36 ` bugzilla at busybox.net
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=bug-10726-163-z3LC4wxpli@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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