From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9 v2] toolchain/external: use generic extract commands (branch yem/extract-cmds)
Date: Sat, 24 Oct 2015 14:48:49 +0200 [thread overview]
Message-ID: <cover.1445690712.git.yann.morin.1998@free.fr> (raw)
Hello All!
This series is an attempt at simplifying the way external toolchains are
extracted.
Currently, external toolchains use custom extract commands, because they
want to exclude a bunch of files during extraction, so as to save a bit
of space (locales in some toolchains can account for up to 80% of the
size of the toolchain as a whole).
And it turns out, gcc also wants to exclude a bunch of files (java and
go, testsuites).
Using custom extract commands means that those packages (and critical
ones, at that) can not benefit from the enhancements and fixes made to
the generic commands, like the automatic striping of components.
In this series:
- we first introduce the support for the exclusion list;
- we drop the hard-link dereference option to tar, it's useless when
extracting;
- we make gcc use the exclusion list;
- we then make the external toolchains use it (in two passes: one for
the non-Blackfin case, one for it, as it is 'seecial');
- we allow users to specify an exlcusion list for custom toolchains;
- finaly, we introduce the Codescape MTI and IMG toolchains from
Vincent.
Changes RFC -> v2:
- allow user to exclude files for custom toolchain (Romain)
- don't force --hard-dereference, it's useless; instead, drop it
- add the IMG toolchain
- use appropriate toolchain on x86 and x86_64
- rebase on top of master
Regards,
Yann E. MORIN.
The following changes since commit b4660601cdcf9b66b167a08ec2a19e8e4564c7d6:
linux: bump default version to 4.2.4 (2015-10-23 09:27:04 +0200)
are available in the git repository at:
git://git.busybox.net/~ymorin/git/buildroot yem/extract-cmds
for you to fetch changes up to d81c191c32f761351ec9a907feedbd47968cd1ee:
toolchain/external: Codescape toolchains also exist for x86_64 (2015-10-24 14:44:42 +0200)
----------------------------------------------------------------
Vicente Olivert Riera (2):
toolchain/external: add MIPS Codescape MTI GNU Linux toolchain
toolchain/external: add MIPS Codescape IMG GNU Linux toolchain
Yann E. MORIN (7):
core/pkg-generic: allow packages to exclude files when extracting
toolchain-external/blacfin: always force keeping hardlinks from archives
package/gcc: use generic extract commands
toolchain/external: use generic extract commands (!blackfin case)
toolchain/external: use generic extract commands (blackfin case)
toolchain/external: allow user to exclude files from custom toolchains
toolchain/external: Codescape toolchains also exist for x86_64
docs/manual/adding-packages-generic.txt | 4 +
package/gcc/gcc-final/gcc-final.mk | 3 +-
package/gcc/gcc-initial/gcc-initial.mk | 3 +-
package/gcc/gcc.mk | 15 +--
package/pkg-generic.mk | 5 +-
toolchain/helpers.mk | 12 ++-
toolchain/toolchain-external/Config.in | 102 +++++++++++++++++++++
.../toolchain-external/toolchain-external.hash | 7 ++
toolchain/toolchain-external/toolchain-external.mk | 73 ++++++++++-----
9 files changed, 186 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. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2015-10-24 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 12:48 Yann E. MORIN [this message]
2015-10-24 12:48 ` [Buildroot] [PATCH 1/9 v2] core/pkg-generic: allow packages to exclude files when extracting Yann E. MORIN
2015-10-29 10:55 ` Vicente Olivert Riera
2015-10-29 11:13 ` Martin Bark
2015-10-24 12:48 ` [Buildroot] [PATCH 2/9 v2] toolchain-external/blacfin: always force keeping hardlinks from archives Yann E. MORIN
2015-10-30 10:51 ` Arnout Vandecappelle
2015-10-24 12:48 ` [Buildroot] [PATCH 3/9 v2] package/gcc: use generic extract commands Yann E. MORIN
2015-10-29 11:25 ` Vicente Olivert Riera
2015-10-24 12:48 ` [Buildroot] [PATCH 4/9 v2] toolchain/external: use generic extract commands (!blackfin case) Yann E. MORIN
2015-10-29 11:39 ` Vicente Olivert Riera
2015-10-24 12:48 ` [Buildroot] [PATCH 5/9 v2] toolchain/external: use generic extract commands (blackfin case) Yann E. MORIN
2015-10-24 12:48 ` [Buildroot] [PATCH 6/9 v2] toolchain/external: allow user to exclude files from custom toolchains Yann E. MORIN
2015-10-29 11:53 ` Vicente Olivert Riera
2015-10-24 12:48 ` [Buildroot] [PATCH 7/9 v2] toolchain/external: add MIPS Codescape MTI GNU Linux toolchain Yann E. MORIN
2015-10-24 12:49 ` [Buildroot] [PATCH 8/9 v2] toolchain/external: add MIPS Codescape IMG " Yann E. MORIN
2015-10-24 12:49 ` [Buildroot] [PATCH 9/9 v2] toolchain/external: Codescape toolchains also exist for x86_64 Yann E. MORIN
2015-10-29 12:10 ` Vicente Olivert Riera
2015-11-03 22:40 ` [Buildroot] [PATCH 0/9 v2] toolchain/external: use generic extract commands (branch yem/extract-cmds) 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.1445690712.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