From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain/gcc: the ARC version of gcc needs host-flex/host-bison
Date: Mon, 13 May 2013 23:40:59 +0200 [thread overview]
Message-ID: <20130513234059.740a720e@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D6339FF18A@de02wembxa.internal.synopsys.com>
Dear Mischa Jonker,
On Fri, 10 May 2013 14:47:56 +0000, Mischa Jonker wrote:
> Thank you for fixing this. Is there any way I can sort the autobuilder results so that I can see specific build problems for ARC?
Build failures on the ARC architecture:
* On the rt-tests package. See
http://autobuild.buildroot.org/results/bfb/bfbd82224a80f4446c5f9c1a37b95e910c9f181a//
for details. Looks like rt-tests want a NPTL toolchain.
* On the OpenOCD package. See
http://autobuild.buildroot.org/results/e18/e185b1ef573ddeca51ceb1d30298e611c6879b42//
for details. It seems to be a toolchain problem: "{standard
input}:449: Error: operand out of range (-514 is not between -512
and 511)".
I've just put online a new version of http://autobuild.buildroot.org/,
which now uses a database. If you're interested, I can send you every
day a mail with the ARC build failures (and only the ARC ones), if any.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-13 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 15:53 [Buildroot] [PATCH 1/2] toolchain/gcc: make sure to pass $(HOST_DIR)/usr/bin in the PATH Thomas Petazzoni
2013-05-09 15:53 ` [Buildroot] [PATCH 2/2] toolchain/gcc: the ARC version of gcc needs host-flex/host-bison Thomas Petazzoni
2013-05-10 14:47 ` Mischa Jonker
2013-05-10 15:53 ` Thomas Petazzoni
2013-05-13 21:40 ` Thomas Petazzoni [this message]
2013-05-12 20:22 ` [Buildroot] [PATCH 1/2] toolchain/gcc: make sure to pass $(HOST_DIR)/usr/bin in the PATH Peter Korsgaard
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=20130513234059.740a720e@skate \
--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