mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc1 initramfs busted [u]
Date: Sat, 23 Oct 2004 14:42:08 +0200	[thread overview]
Message-ID: <1098535328.668.13.camel@nosferatu.lan> (raw)
In-Reply-To: <20041023133120.A28178@flint.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]

On Sat, 2004-10-23 at 13:31 +0100, Russell King wrote:
> 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.
> 

Yep.  Please see the

 [PATCH 2.6.9-bk7] Select cpio_list or source directory for initramfs image updates

thread for latest patch to fix this and other issues.  There are some
other patches floating around that is slightly smaller, but I would
appreciate testing and feedback.


Cheers,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-23 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 12:31 2.6.10-rc1 initramfs busted Russell King
2004-10-23 12:42 ` Martin Schlemmer [c] [this message]
2004-10-23 20:36   ` 2.6.10-rc1 initramfs busted [u] 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=1098535328.668.13.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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

Powered by JetHome