From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libsigsegv: unavailable for powerpc with uclibc
Date: Sat, 18 Jul 2015 23:53:42 +0200 [thread overview]
Message-ID: <20150718235342.6de37530@free-electrons.com> (raw)
In-Reply-To: <55A6527C.8000206@zacarias.com.ar>
Gustavo,
On Wed, 15 Jul 2015 09:30:52 -0300, Gustavo Zacarias wrote:
> There's a whole set of different arch combinations for musl that don't
> seem to build, it needs a whole lot of build testing to get an accurate
> list.
Ok, so let's wait to handle the musl situation. I'm waiting for the ARM
musl and x86-64 musl configurations to stabilize a bit in the
autobuilders before adding more musl toolchains.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-18 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:01 [Buildroot] [PATCH] libsigsegv: unavailable for powerpc with uclibc Gustavo Zacarias
2015-07-06 15:38 ` Thomas Petazzoni
2015-07-15 9:01 ` Thomas Petazzoni
2015-07-15 12:30 ` Gustavo Zacarias
2015-07-18 21:53 ` Thomas Petazzoni [this message]
2015-07-18 21:52 ` Thomas Petazzoni
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=20150718235342.6de37530@free-electrons.com \
--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