Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] m68k: enable internal toolchain
Date: Sun, 20 Mar 2016 15:29:27 +0100	[thread overview]
Message-ID: <20160320152927.0630a80a@free-electrons.com> (raw)
In-Reply-To: <20160319190410.GA1018@waldemar-brodkorb.de>

Hello,

On Sat, 19 Mar 2016 20:04:10 +0100, Waldemar Brodkorb wrote:
> This allows to build a m68k toolchain.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1 -> v2:
>   reduce CPU variants to 68040, suggested by Thomas Petazzoni,
>   more CPU's will be added later. Qemu Q800 is 68040 only so
>   this is okay
> ---
>  arch/Config.in                               |  1 -
>  arch/Config.in.m68k                          | 20 ++++++++++++++------
>  package/gcc/4.8.5/890-fix-m68k-compile.patch | 15 +++++++++++++++
>  package/gcc/4.9.3/890-fix-m68k-compile.patch | 15 +++++++++++++++
>  package/gcc/5.3.0/890-fix-m68k-compile.patch | 15 +++++++++++++++
>  5 files changed, 59 insertions(+), 7 deletions(-)
>  create mode 100644 package/gcc/4.8.5/890-fix-m68k-compile.patch
>  create mode 100644 package/gcc/4.9.3/890-fix-m68k-compile.patch
>  create mode 100644 package/gcc/5.3.0/890-fix-m68k-compile.patch

I've applied, after slightly tweaking the commit title/log.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-03-20 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-19 19:04 [Buildroot] [PATCH v2 1/2] m68k: enable internal toolchain Waldemar Brodkorb
2016-03-20 14:29 ` 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=20160320152927.0630a80a@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