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 16:40:26 +0000 [thread overview]
Message-ID: <bug-10726-163-hAPykNIL4s@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 #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for your well-documented bug report!
I think all those pre-seeded cache variables in LIBGLIB2_CONF_ENV are just
crap. They have been there since the glib2 package was introduced back in
January 2007, and the vast majority of them are useless, and potentially
harmful (as you have discovered). So the fix is most likely to remove almost
all of them, the key being to identify which ones we need to keep.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-02-05 16:40 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 ` [Buildroot] [Bug 10726] " bugzilla at busybox.net
2018-02-05 10:38 ` bugzilla at busybox.net
2018-02-05 16:40 ` bugzilla at busybox.net [this message]
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-hAPykNIL4s@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