From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 637] New: Kernel .config copy fail
Date: Thu, 1 Oct 2009 04:57:09 +0000 (UTC) [thread overview]
Message-ID: <bug-637-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=637
Summary: Kernel .config copy fail
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: hokanson at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
The latest snapshot (Oct 1st), and the several I tried before that, die when it
comes time to compile the Kernel. I receive the following error:
rm -rf /home/eric/buildroot/output/build/linux-2.6.31.1
*** Unpacking kernel source
bzcat ./dl/linux-2.6.31.1.tar.bz2 | tar -C /home/eric/buildroot/output/build
-xf -
touch /home/eric/buildroot/output/build/linux-2.6.31.1/.unpacked
toolchain/patch-kernel.sh /home/eric/buildroot/output/build/linux-2.6.31.1
toolchain/kernel-headers \
linux-2.6.31.1-\*.patch{,.gz,.bz2}
touch /home/eric/buildroot/output/build/linux-2.6.31.1/.patched
cp -dpf /home/eric/buildroot/output/build/linux-2.6.31.1/.config
cp: missing destination file operand after
`/home/eric/buildroot/output/build/linux-2.6.31.1/.config'
Try `cp --help' for more information.
make: *** [/home/eric/buildroot/output/build/linux-2.6.31.1/.configured] Error
1
--
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:[~2009-10-01 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 4:57 bugzilla at busybox.net [this message]
2009-12-02 1:25 ` [Buildroot] [Bug 637] Kernel .config copy fail 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-637-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.