From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] qemu/mips64-malta: switch to eglibc
Date: Wed, 27 Nov 2013 14:03:43 +0100 [thread overview]
Message-ID: <20131127140343.46e5f0e0@skate> (raw)
In-Reply-To: <5295C431.2010807@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 27 Nov 2013 07:06:41 -0300, Gustavo Zacarias wrote:
> On 11/27/2013 05:24 AM, Thomas Petazzoni wrote:
>
> > I think the broken dynamic loader for mips64 in uClibc is now fixed
> > by package/uclibc/0.9.33.2/uclibc-0009-mips64-fix-n64-interp.patch.
>
> Probably, but besides that it's generally unstable with uClibc (you
> almost certainly can't login properly) where with eglibc it just
> works(tm). Though maybe it just needs a little kick like the recent
> SIGBUS mips64 patch from the uclibc mailing list.
Ok. Then, should we make (e)glibc the default C library for mips64, so
that users will not have a non-working system if they simply build a
basic default configuration for mips64 (which will use uClibc) ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-27 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 0:51 [Buildroot] [PATCH 1/2] eglibc: add security patch for CVE-2013-4788 Gustavo Zacarias
2013-11-27 0:51 ` [Buildroot] [PATCH 2/2] qemu/mips64-malta: switch to eglibc Gustavo Zacarias
2013-11-27 8:24 ` Thomas Petazzoni
2013-11-27 10:06 ` Gustavo Zacarias
2013-11-27 13:03 ` Thomas Petazzoni [this message]
2013-11-27 13:10 ` Gustavo Zacarias
2013-11-27 10:15 ` Markos Chandras
2013-11-28 13:46 ` [Buildroot] [PATCH 1/2] eglibc: add security patch for CVE-2013-4788 Peter Korsgaard
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=20131127140343.46e5f0e0@skate \
--to=thomas.petazzoni@free-electrons.com \
--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