From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3511] New: make busybox-menuconfig does not download busybox package
Date: Mon, 28 Mar 2011 12:16:13 +0000 (UTC) [thread overview]
Message-ID: <bug-3511-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3511
Summary: make busybox-menuconfig does not download busybox
package
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: dmitry at radiofid.ru
CC: buildroot at uclibc.org
Estimated Hours: 0.0
'make busybox-menuconfig' does not download busybox package, while 'make
linux26-menuconfig' and 'make uclibc-menuconfig' do. Workaround is to call
'make busybox' (which fails since no crosscompiler is available yet) and repeat
'make busybox-menuconfig'.
$ make busybox-menuconfig
>>> busybox 1.18.4 Extracting
bzcat: Can't open input file
/home/dimka/buildroot/router-irz-wimax-fw/dl/busybox-1.18.4.tar.bz2: No such
file or directory.
tar: ??? ?? ?????? ?? tar-?????
tar: ?????????? ?????? ? ?????????? ????????????? ? ??-?? ????????? ??????
make: ***
[/home/dimka/buildroot/router-irz-wimax-fw/output/build/busybox-1.18.4/.stamp_extracted]
?????? 2
(Sorry for russian text)
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-03-28 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 12:16 bugzilla at busybox.net [this message]
2011-03-28 14:33 ` [Buildroot] [Bug 3511] New: make busybox-menuconfig does not download busybox package Benoît Mauduit
2011-03-28 19:34 ` [Buildroot] [Bug 3511] " bugzilla at busybox.net
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=bug-3511-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.