Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/9 v2] toolchain/external: use generic extract commands (!blackfin case)
Date: Thu, 29 Oct 2015 11:39:19 +0000	[thread overview]
Message-ID: <56320567.6080303@imgtec.com> (raw)
In-Reply-To: <4dfbf001b46ffeddf9c4fb300967473a3860b200.1445690712.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On 10/24/2015 01:48 PM, Yann E. MORIN wrote:
> Now that packages can provide a list of files to be excluded when
> extracting their archive, downloaded external toolchains are no longer
> special in this respect.
> 
> Still, those toolchains are currently extracted directly into their
> final location, $(HOST_DIR)/opt/ext-toolchain/ which means we still
> need a custom extract command.
> 
> Except, we don't really need it: we can just move the toolchain, after
> it's been extracted by the generic extract command, with a post-extract
> hook.
> 
> This means that:
> 
>   - we now extract the toolchain with the generic extract command,
> 
>   - the toolchain is thus extracted into $(@D) ,
> 
>   - fixup commands are run against $(@D), as a post-extract hook,
>     instead of against $(HOST_DIR)/opt/ext-toolchain ,
> 
>   - once this is done, we move $(@D)/* into the final location with a
>     new post-extract hook.
> 
> Note: the blackfin case is special, and will be handled in a follow-up
> patch.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

After applying this patch (and the previous ones) I have built a rootfs
for MIPS architecture using the latest Codesourcery external toolchain.

Regards,

Vincent.

  reply	other threads:[~2015-10-29 11:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 12:48 [Buildroot] [PATCH 0/9 v2] toolchain/external: use generic extract commands (branch yem/extract-cmds) Yann E. MORIN
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 [this message]
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=56320567.6080303@imgtec.com \
    --to=vincent.riera@imgtec.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