From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] -lsof was unable to patch Makefile.skel due to bad file permissions. Adding chmod solves it. (openSUSE)
Date: Thu, 20 Oct 2011 14:48:52 +0200 [thread overview]
Message-ID: <201110201448.53060.arnout@mind.be> (raw)
In-Reply-To: <201110201322.13259.yann.morin.1998@anciens.enib.fr>
On Thursday 20 October 2011 13:22:13, Yann E. MORIN wrote:
> > LSOF_EXTRACT_CMDS = \
> > $(INFLATE.bz2) $(DL_DIR)/$(LSOF_SOURCE) | \
> > $(TAR) -O $(TAR_OPTIONS) - lsof_$(LSOF_VERSION)/lsof_$(LSOF_VERSION)_src.tar | \
> > $(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(LSOF_DIR) $(TAR_OPTIONS) -)
>
> That would not work, because the first $(TAR) will extract actual files
> to the disk, and does not send the extracted files to the stdio, so the
> second $(TAR) will get nothing on its stdin (at best), or only get
> garbage (at worst).
Oh, is -O not a universally accepted tar option?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-10-20 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 20:55 [Buildroot] [PATCH] -lsof was unable to patch Makefile.skel due to bad file permissions. Adding chmod solves it. (openSUSE) Damian Kaczmarek
2011-10-19 21:27 ` Yann E. MORIN
2011-10-19 22:46 ` Arnout Vandecappelle
2011-10-20 11:22 ` Yann E. MORIN
2011-10-20 12:48 ` Arnout Vandecappelle [this message]
2011-10-20 19:45 ` Yann E. MORIN
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=201110201448.53060.arnout@mind.be \
--to=arnout@mind.be \
--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.