From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.6.10-rc1 initramfs busted
Date: Sat, 23 Oct 2004 13:31:20 +0100 [thread overview]
Message-ID: <20041023133120.A28178@flint.arm.linux.org.uk> (raw)
A build using O= does this:
HOSTCC usr/gen_init_cpio
GEN_INITRAMFS_LIST usr/initramfs_list
Using shipped usr/initramfs_list
CPIO usr/initramfs_data.cpio
ERROR: unable to open 'usr/initramfs_list': No such file or directory
Usage:
./usr/gen_init_cpio <cpio_list>
<cpio_list> is a file containing newline separated entries that
describe the files to be included in the initramfs archive:
The source tree contains this in usr:
-rw-r--r-- 1 rmk rmk 1657 Oct 23 11:41 Makefile
-rw-r--r-- 1 rmk rmk 8335 Oct 23 11:41 gen_init_cpio.c
-rw-r--r-- 1 rmk rmk 1024 Aug 1 2003 initramfs_data.S
-rw-r--r-- 1 rmk rmk 146 Oct 23 11:41 initramfs_list
and the build tree usr contains:
-rwxr-xr-x 1 rmk rmk 10834 Oct 23 13:29 gen_init_cpio
-rw-r--r-- 1 rmk rmk 0 Oct 23 13:29 initramfs_data.cpio
Running with V=1 shows:
make -f /home/rmk/build/linux-v2.6-local/scripts/Makefile.build obj=usr
echo Using shipped usr/initramfs_list
Using shipped usr/initramfs_list
./usr/gen_init_cpio usr/initramfs_list > usr/initramfs_data.cpio
ERROR: unable to open 'usr/initramfs_list': No such file or directory
so it's referencing the wrong directory.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next reply other threads:[~2004-10-23 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 12:31 Russell King [this message]
2004-10-23 12:42 ` 2.6.10-rc1 initramfs busted [u] Martin Schlemmer [c]
2004-10-23 20:36 ` Russell King
2004-10-23 23:41 ` Martin Schlemmer [c]
2004-10-24 8:30 ` 2.6.10-rc1 initramfs busted Matthias Urlichs
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=20041023133120.A28178@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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.