From: Scott Reese <sreese@indianaheart.org>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with recent zcat changes
Date: Sun, 01 Oct 2006 15:00:17 -0400 [thread overview]
Message-ID: <45201041.9050907@indianaheart.org> (raw)
In-Reply-To: <20061001183736.GK17455@aon.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bernhard Fischer wrote:
> On Sun, Oct 01, 2006 at 02:02:09PM -0400, Scott Reese wrote:
> Greetings:
>
> I think that the zcat changes over the last few days have caused some
> problems in the makefile. The newest buildroot fails to build the
> skeleton directories correctly.
>
>> No idea why that hunk wasn't checked in.
>
>> Added now as r16285, it looked like:
>> Index: package/Makefile.in
>> ===================================================================
>> --- package/Makefile.in (revision 16280)
>> +++ package/Makefile.in (working copy)
>> @@ -8,6 +8,8 @@
>> #"
>> SVN:=$(strip $(subst ",, $(BR2_SVN)))
>> #"
>> +ZCAT:=$(strip $(subst ",, $(BR2_ZCAT)))
>> +#"
>> TAR_OPTIONS=$(subst ",, $(BR2_TAR_OPTIONS)) -xf
>> #"
>
>> Ok now?
> The Makefile should be changed to reference BR2_ZCAT instead of ZCAT:
>
> 107c107
> < $(ZCAT) $(TARGET_SKELETON) | tar -C $(BUILD_DIR) -xf -; \
> ---
>>>> $(BR2_ZCAT) $(TARGET_SKELETON) | tar -C $(BUILD_DIR) -xf
> -; \
>
> -Scott
That seems to have fixed it. Thanks.
- -Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFFIBAGS7FYdPX6+iYRAr9mAJ9GhU4UKlMrrEC0hTPRMDn2pTYzmwCWIbWm
xpcHj7rGhUNQZiYRipQuUQ==
=YSWs
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-10-01 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 18:02 [Buildroot] Problems with recent zcat changes Scott Reese
2006-10-01 18:37 ` Bernhard Fischer
2006-10-01 19:00 ` Scott Reese [this message]
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=45201041.9050907@indianaheart.org \
--to=sreese@indianaheart.org \
--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.