From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mpd: enable package for external ARC toolchain
Date: Wed, 11 Oct 2017 23:19:16 +0200 [thread overview]
Message-ID: <20171011231916.1e88100d@windsurf.lan> (raw)
In-Reply-To: <528747de-6a5f-a011-4ec8-ac9141ce9bf2@mind.be>
Hello,
On Wed, 11 Oct 2017 22:14:38 +0200, Arnout Vandecappelle wrote:
> Hi Evgeny,
>
> On 11-10-17 14:16, Evgeniy Didin wrote:
> > Now using prebuilt arc-2017.09-rc1 toolchain it is possible to
> > build mpd package. The GCC patch solving the problem with pthread
> > support check now is the part of ARC toolchain.
> >
> > Note this patch has a prerequisite that updates ARC prebuilt toolchain,
> > http://patchwork.ozlabs.org/patch/824311/
The ARC prebuilt toolchain is not tested by our autobuilders. The two
ARC configurations that we have are:
support/config-fragments/autobuild/br-arc-full-internal.config
support/config-fragments/autobuild/br-arcle-hs38.config
The first is a Buildroot internal toolchain, the second is an external
toolchain, built with Buildroot.
So we are not testing the Synopsys-provided pre-built toolchain, and
therefore the build failures that were detected in mpd and vlc were not
caused by Synopsys pre-built toolchain.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-11 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 12:16 [Buildroot] [PATCH] mpd: enable package for external ARC toolchain Evgeniy Didin
2017-10-11 20:14 ` Arnout Vandecappelle
2017-10-11 21:19 ` Thomas Petazzoni [this message]
2017-10-11 21:30 ` Alexey Brodkin
2017-10-21 20:16 ` 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=20171011231916.1e88100d@windsurf.lan \
--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