From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: fix sparc compile
Date: Mon, 16 Nov 2015 22:07:22 +0100 [thread overview]
Message-ID: <20151116210722.GG19876@waldemar-brodkorb.de> (raw)
In-Reply-To: <20151116214000.3f33b341@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> Dear Waldemar Brodkorb,
>
> On Sun, 15 Nov 2015 13:24:55 +0100, Waldemar Brodkorb wrote:
> > Like for sparc64, set correct instruction set.
> > Patch is obsoleted by this changeset.
> >
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
>
> 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.
> Also, Boost on Sparc still doesn't build properly for me in certain
> configurations. For example:
>
> BR2_PACKAGE_BOOST_CONTEXT=y
> BR2_PACKAGE_BOOST_COROUTINE=y
>
> Fails with:
>
> ...failed gcc.compile.asm bin.v2/libs/context/build/gcc-4.9.3/release/threading-multi/asm/jump_sparc_sysv_elf_gas.o...
> gcc.compile.c++ bin.v2/libs/context/build/gcc-4.9.3/release/threading-multi/unsupported.o
> libs/context/src/unsupported.cpp:7:2: error: #error "platform not supported"
> #error "platform not supported"
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.
best regards
Waldemar
next prev parent reply other threads:[~2015-11-16 21:07 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 [this message]
2015-11-16 21:09 ` Thomas Petazzoni
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=20151116210722.GG19876@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.