From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/2] toolchain: add sparc64 architecture support
Date: Sat, 10 Oct 2015 19:35:09 +0200 [thread overview]
Message-ID: <20151010193509.058edf01@free-electrons.com> (raw)
In-Reply-To: <20150829075733.GA19454@waldemar-brodkorb.de>
Waldemar,
On Sat, 29 Aug 2015 09:57:33 +0200, Waldemar Brodkorb wrote:
> Introduce sparc64 architecture to buildroot.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> - Changes v1 -> v2:
> only allow useful architecture variants suggested by Thomas Petazzoni
> ---
> arch/Config.in | 12 +++++++++++-
> arch/Config.in.sparc | 12 ++++++++++--
> toolchain/toolchain-buildroot/Config.in | 3 ++-
> 3 files changed, 23 insertions(+), 4 deletions(-)
I tried to build a toolchain with this, and it fails for me, during the
host-gcc-final build step, with the following error message:
In file included from ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:17:0:
../../../../libsanitizer/sanitizer_common/sanitizer_internal_defs.h:257:72: error: size of array 'assertion_failed__869' is negative
typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
I have built the following configuration:
BR2_sparc64=y
BR2_KERNEL_HEADERS_4_1=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_INIT_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
# BR2_TARGET_ROOTFS_TAR is not set
Could you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-10 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 7:57 [Buildroot] [PATCHv2 1/2] toolchain: add sparc64 architecture support Waldemar Brodkorb
2015-10-08 14:06 ` Gustavo Zacarias
2015-10-10 10:54 ` Thomas Petazzoni
2015-10-10 17:35 ` 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=20151010193509.058edf01@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