From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mono: fix undefined reference to tls
Date: Fri, 9 Sep 2016 09:26:57 +0200 [thread overview]
Message-ID: <20160909092657.133b1e06@free-electrons.com> (raw)
In-Reply-To: <CA+TH9Vm4Q=XVaNBMk77MTx4bSscrm4DxEVk3ek2_dbVX64tg=A@mail.gmail.com>
Hello,
On Fri, 9 Sep 2016 07:29:11 +0200, Angelo Compagnucci wrote:
> I tested both the pre-compiled musl external toolchain and a musl internal
> toolchain I compiled and I can confirm that it's working without this patch.
> So, probably simply rebuilding the autobuild toolchain should solve the
> problem.
Excellent, thanks! I'll kick a rebuild of the different Buildroot
toolchains soon, especially since we have move to a newer binutils
version, and have more recent version of gcc available as well.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-09 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 8:51 [Buildroot] [PATCH] package/mono: fix undefined reference to tls Angelo Compagnucci
2016-09-08 11:42 ` Thomas Petazzoni
2016-09-09 5:29 ` Angelo Compagnucci
2016-09-09 7:26 ` Thomas Petazzoni [this message]
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=20160909092657.133b1e06@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