Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with recent zcat changes
Date: Sun, 1 Oct 2006 20:37:36 +0200	[thread overview]
Message-ID: <20061001183736.GK17455@aon.at> (raw)
In-Reply-To: <452002A1.2020400@indianaheart.org>

On Sun, Oct 01, 2006 at 02:02:09PM -0400, Scott Reese wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>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
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.2.2 (GNU/Linux)
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
>iD8DBQFFIAJuS7FYdPX6+iYRAmcNAJ9IIC8f9tn1ObDR5soVsXVzCFRRPgCdHIxF
>hoYF5fYVStfctq4vxlQMUOQ=
>=uvcB
>-----END PGP SIGNATURE-----
>_______________________________________________
>buildroot mailing list
>buildroot at uclibc.org
>http://busybox.net/mailman/listinfo/buildroot
>

  reply	other threads:[~2006-10-01 18:37 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 [this message]
2006-10-01 19:00   ` Scott Reese

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=20061001183736.GK17455@aon.at \
    --to=rep.nop@aon.at \
    --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