From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/internal: not aailable for a few mips cores
Date: Tue, 29 Aug 2017 23:19:35 +0200 [thread overview]
Message-ID: <20170829231935.71e6bb85@windsurf.lan> (raw)
In-Reply-To: <20170817202647.26738-1-yann.morin.1998@free.fr>
Hello,
On Thu, 17 Aug 2017 22:26:47 +0200, Yann E. MORIN wrote:
> Commit 1b974425 (MIPS: add support for M6201 cores) xplained that the
> new core was not supported by upstream gcc, and as of gcc-8-trunk that's
> stil lthe case.
>
> Ditto for 3cfbeb83 (MIPS: add support for P6600 cores).
>
> This means that we currently elect to build an internal tolchain for
> those cores, yet we have no suitable gcc version.
>
> Disable the internal backend in this case.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> package/gcc/Config.in.host | 7 +------
> toolchain/Config.in | 2 ++
> 2 files changed, 3 insertions(+), 6 deletions(-)
Applied to master, after fixing a number of typos here and there :)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-29 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 20:26 [Buildroot] [PATCH] toolchain/internal: not aailable for a few mips cores Yann E. MORIN
2017-08-17 22:20 ` Arnout Vandecappelle
2017-08-18 15:42 ` Yann E. MORIN
2017-08-29 21:19 ` 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=20170829231935.71e6bb85@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