From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external/CodeSourcery MIPS: available only for R2
Date: Sat, 17 Oct 2015 16:21:55 +0200 [thread overview]
Message-ID: <20151017162155.097e9f42@free-electrons.com> (raw)
In-Reply-To: <1445011202-47571-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 16 Oct 2015 17:00:01 +0100, Vicente Olivert Riera wrote:
> Currently the CodeSourcery toolchains for MIPS can be selected to build
> mips32 (revision level 1) targets, but the resulting binaries are built
> for mips32r2 instead. This is because these toolchains don't have
> library support other than mips32r2, so there is no point to allow the
> selection of a mips32 variant with a CodeSourcery MIPS toolchain, since
> everything will be built for mips32r2 instead.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> toolchain/toolchain-external/Config.in | 9 +++------
> 1 files changed, 3 insertions(+), 6 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-17 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:00 [Buildroot] [PATCH] toolchain-external/CodeSourcery MIPS: available only for R2 Vicente Olivert Riera
2015-10-16 16:00 ` [Buildroot] [PATCH buildroot-test] Update CodeSourcery MIPS toolchains config files Vicente Olivert Riera
2015-10-17 14:18 ` Thomas Petazzoni
2015-10-17 14:21 ` 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=20151017162155.097e9f42@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