Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v3] toolchain/external: add Linaro 2014.11 for ARMv7 BE/LE EABIhf and AArch64 (branch yem/toolchain-linaro-2014.11)
Date: Mon,  7 Sep 2015 23:09:54 +0200	[thread overview]
Message-ID: <cover.1441660041.git.yann.morin.1998@free.fr> (raw)

Hello All!

This series introduces the Linaro 2014.11 toolchains, for ARM (LE and
BE) and AArch64.

See the commit log of patch 1 for the gory details... :-/

ARM (LE) toolchain was tested with a minimalist setup, based on
qemu_arm_vexpress_defconfig, with just a switch to use EABIhf and this
toolchain (rather than the default EABI and internal toolchain), while
the AArch64 toolchain was tested in a similar way, based on
qemu_aarch64_virt_defconfig.

Notes: I haven't had the opportunity to report the issues to Linaro for
now. :-/ I'll try to do that soon...


Changes v2 -> v3:
  - fix comments about secondary tarball  (Thomas)
  - expand comments about post-extract hooks  (Thomas)
  - fix typoes  (Thomas)

Changes v1 -> v2:
  - remove stray backup file


Regards,
Yann E. MORIN.


The following changes since commit 3cd209bfaf4c7af47ce9ddfe1fd2b0d82d30909d:

  docs: website: update for 2015.08.1 (2015-09-06 23:09:12 +0200)

are available in the git repository at:

  git://git.busybox.net/~ymorin/git/buildroot yem/toolchain-linaro-2014.11

for you to fetch changes up to 7d7abe73fcf0fc9420ba27ec0b069ad97f747b63:

  toolchain/external: add Linaro AArch64 2014.11 (2015-09-06 23:11:37 +0200)

----------------------------------------------------------------
Yann E. MORIN (3):
      toolchain/external: add Linaro ARM 2014.11 ARMv7 EABIhf
      toolchain/external: add Linaro ARM BE 2014.11 ARMv7 EABIhf
      toolchain/external: add Linaro AArch64 2014.11

 toolchain/toolchain-external/Config.in             | 63 +++++++++++++++-----
 .../toolchain-external/toolchain-external.hash     |  6 ++
 toolchain/toolchain-external/toolchain-external.mk | 69 ++++++++++++++--------
 3 files changed, 100 insertions(+), 38 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

             reply	other threads:[~2015-09-07 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 21:09 Yann E. MORIN [this message]
2015-09-07 21:09 ` [Buildroot] [PATCH 1/3 v3] toolchain/external: add Linaro ARM 2014.11 ARMv7 EABIhf Yann E. MORIN
2015-09-07 21:52   ` Arnout Vandecappelle
2015-09-07 21:09 ` [Buildroot] [PATCH 2/3 v3] toolchain/external: add Linaro ARM BE " Yann E. MORIN
2015-09-07 21:09 ` [Buildroot] [PATCH 3/3 v3] toolchain/external: add Linaro AArch64 2014.11 Yann E. MORIN
2015-09-20 13:00 ` [Buildroot] [PATCH 0/3 v3] toolchain/external: add Linaro 2014.11 for ARMv7 BE/LE EABIhf and AArch64 (branch yem/toolchain-linaro-2014.11) 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=cover.1441660041.git.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --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