From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: fix sparc compile
Date: Mon, 16 Nov 2015 22:09:44 +0100 [thread overview]
Message-ID: <20151116220944.54bd039c@free-electrons.com> (raw)
In-Reply-To: <20151116210722.GG19876@waldemar-brodkorb.de>
Hello,
On Mon, 16 Nov 2015 22:07:22 +0100, Waldemar Brodkorb wrote:
> > Is this fixing an actual issue / build failure, or just making the
> > Sparc fix nicer ?
>
> It makes the sparc fix nicer, no patch required to disable c3 and
> it will use sparcv8 instead sparcv7, which matches more your
> targeting sparc systems.
Ok, so it's more material for next than for master.
> As mentioned in my comment, context/coroutine are not yet supported.
> Will need to do some testing and then I will try to get the fixes to
> enable it upstream.
Ok, no problem. Note that from the Buildroot point of view, enabling
Boost context is not really important. Nothing requires it, so having
it supported only on certain architectures is not a problem. So only do
the sparc support if you have some other interest in it.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-16 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 12:24 [Buildroot] [PATCH] boost: fix sparc compile Waldemar Brodkorb
2015-11-16 20:40 ` Thomas Petazzoni
2015-11-16 20:43 ` Arnout Vandecappelle
2015-11-16 20:52 ` Thomas Petazzoni
2015-11-16 21:07 ` Waldemar Brodkorb
2015-11-16 21:09 ` Thomas Petazzoni [this message]
2015-11-17 21:18 ` 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=20151116220944.54bd039c@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