From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2251] New: directory output/build after make *_defconfig not found
Date: Tue, 20 Jul 2010 07:09:17 +0000 (UTC) [thread overview]
Message-ID: <bug-2251-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2251
Summary: directory output/build after make *_defconfig not
found
Product: buildroot
Version: 2010.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mensch0815 at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
when you build a defconfig with make something_defconfig and afterwards want to
edit the linux kernel configuration (make linux26-menuconfig), then buildroot
can't chdir in the output/build directory, because it is not yet created.
some output (sorry error message is in german):
bzcat /home/ich/buildroot-2010.02/dl/linux-2.6.32.9.tar.bz2 | tar -C
/home/ich/buildroot-2010.02/output/build -xf -
tar: /home/ich/buildroot-2010.02/output/build: Kann chdir nicht ausf?hren:
Datei oder Verzeichnis nicht gefunden
when you create the output/build folder by your own, it works.
--
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:[~2010-07-20 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 7:09 bugzilla at busybox.net [this message]
2010-07-20 7:09 ` [Buildroot] [Bug 2251] directory output/build after make *_defconfig not found bugzilla at busybox.net
2010-07-20 7:19 ` 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-2251-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.