From: Graham Newton <gnewton@peavey-eu.com>
To: buildroot@busybox.net
Subject: [Buildroot] support/download/wrapper expects file output in temp directory but support/wrapper/git produces output.gz
Date: Wed, 06 Aug 2014 16:29:48 +0100 [thread overview]
Message-ID: <53E249EC.9040805@peavey-eu.com> (raw)
In-Reply-To: <CAAXf6LWBScdsOP=E0wC_CGE63R=dq5g21rqaUsWhtfijmU20Wg@mail.gmail.com>
Running support/download/wrapper git fails because the final instruction
of support/download/git gzips the output file creating output.gz which
wrapper isn't expecting.
Example:
gnewton at ey-debx64-vm01 ~/Working/LinuxBuild $ support/download/wrapper
git /home/gnewton/Working/LinuxBuild/dl/linux-ti816x_graham_dev.tar.gz
gitolite at ey-ubsx64-svr02:LinuxKernel ti816x_graham_dev
linux-ti816x_graham_dev
Doing shallow clone
Cloning into bare repository 'linux-ti816x_graham_dev'...
remote: Counting objects: 48600, done.
remote: Compressing objects: 100% (46466/46466), done.
Receiving objects: 100% (48600/48600), 143.16 MiB | 13.99 MiB/s, done.
remote: Total 48600 (delta 3863), reused 25085 (delta 1546)
Resolving deltas: 100% (3863/3863), done.
Checking connectivity... done.
cat:
/home/gnewton/Working/LinuxBuild/output/build/.linux-ti816x_graham_dev.tar.gz.MX7pH9/output:
No such file or directory
Build root pulled from git://git.busybox.net/buildroot master today
(06/08/2014)
I assume the fix would be to either
i) in wrapper cat output.gz in the case of git
ii) copy output.gz to output after the gzip in support/download/git
next prev parent reply other threads:[~2014-08-06 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 22:19 [Buildroot] [git commit] arch: pass cpu option instead of tune option on ARM Thomas Petazzoni
2014-01-23 15:31 ` Jonas Jensen
2014-01-23 18:15 ` Yann E. MORIN
2014-08-04 14:45 ` Thomas De Schampheleire
2014-08-06 15:29 ` Graham Newton [this message]
2014-08-06 16:29 ` [Buildroot] support/download/wrapper expects file output in temp directory but support/wrapper/git produces output.gz Yann E. MORIN
2014-08-06 16:55 ` Thomas De Schampheleire
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=53E249EC.9040805@peavey-eu.com \
--to=gnewton@peavey-eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.