From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: fix sparc compile
Date: Mon, 16 Nov 2015 21:43:32 +0100 [thread overview]
Message-ID: <564A3FF4.2030707@mind.be> (raw)
In-Reply-To: <20151116214000.3f33b341@free-electrons.com>
On 16-11-15 21:40, 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 ?
>
> Also, Boost on Sparc still doesn't build properly for me in certain
> configurations. For example:
>
> BR2_sparc=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
> BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-sparc-glibc-2015.08-647-gc356fb2.tar.bz2"
> BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
> BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_2=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
> BR2_TOOLCHAIN_EXTERNAL_CXX=y
> BR2_INIT_NONE=y
> BR2_SYSTEM_BIN_SH_NONE=y
> # BR2_PACKAGE_BUSYBOX is not set
> BR2_PACKAGE_BOOST=y
> BR2_PACKAGE_BOOST_ATOMIC=y
> BR2_PACKAGE_BOOST_CHRONO=y
> BR2_PACKAGE_BOOST_CONTAINER=y
> BR2_PACKAGE_BOOST_CONTEXT=y
Quoting Waldemar:
boost::context still does not compile. Don't know why it is
disabled for sparc/sparc64 as it contains the needed code.
Need to check on my sparc systems before enabling via a patch.
But for the release we probably want to disable it in Config.in.
Regards,
Arnout
> BR2_PACKAGE_BOOST_COROUTINE=y
> BR2_PACKAGE_BOOST_DATE_TIME=y
> BR2_PACKAGE_BOOST_EXCEPTION=y
> BR2_PACKAGE_BOOST_FILESYSTEM=y
> BR2_PACKAGE_BOOST_GRAPH=y
> BR2_PACKAGE_BOOST_GRAPH_PARALLEL=y
> BR2_PACKAGE_BOOST_IOSTREAMS=y
> BR2_PACKAGE_BOOST_LOCALE=y
> BR2_PACKAGE_BOOST_LOG=y
> BR2_PACKAGE_BOOST_MATH=y
> BR2_PACKAGE_BOOST_MPI=y
> BR2_PACKAGE_BOOST_PROGRAM_OPTIONS=y
> BR2_PACKAGE_BOOST_RANDOM=y
> BR2_PACKAGE_BOOST_REGEX=y
> BR2_PACKAGE_BOOST_SERIALIZATION=y
> BR2_PACKAGE_BOOST_SIGNALS=y
> BR2_PACKAGE_BOOST_SYSTEM=y
> BR2_PACKAGE_BOOST_TEST=y
> BR2_PACKAGE_BOOST_TIMER=y
> BR2_PACKAGE_BOOST_WAVE=y
> # BR2_TARGET_ROOTFS_TAR is not set
>
> 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"
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-16 20:43 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 [this message]
2015-11-16 20:52 ` Thomas Petazzoni
2015-11-16 21:07 ` Waldemar Brodkorb
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=564A3FF4.2030707@mind.be \
--to=arnout@mind.be \
--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