public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: kai@germaschewski.name, Sam Larson <sam@ravnborg.org>,
	Andrew Morton <akpm@osdl.org>
Subject: 2.6.21-rc5-mm4 initramfs Make Error
Date: Thu, 05 Apr 2007 23:55:36 +0000	[thread overview]
Message-ID: <1175817336.7505.33.camel@localhost> (raw)

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

I built a version of 2.6.21-rc5-mm4 with an initramfs and it built OK
the first time.

Then I made changes (applied a Reiser4 patch) and rebuilt, and got the
following error:

zephyr linux # make
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  CALL    scripts/checksyscalls.sh
<stdin>:1356:2: warning: #warning syscall getcpu not implemented
<stdin>:1360:2: warning: #warning syscall epoll_pwait not implemented
<stdin>:1364:2: warning: #warning syscall lutimesat not implemented
<stdin>:1380:2: warning: #warning syscall revokeat not implemented
<stdin>:1384:2: warning: #warning syscall frevoke not implemented
  CHK     include/linux/compile.h
/usr/src/linux-2.6.21-rc5-mm4/usr/Makefile:41: *** target pattern contains no `%'.  Stop.
make: *** [usr] Error 2

I have this in the config:
CONFIG_INITRAMFS_SOURCE="/initramfs"

/initramfs is the directory where I build my initramfs, which is just a
busybox setup, very simple.

# rm usr/.initramfs_data.*
seems to make it go again.
-- 
Zan Lynx <zlynx@acm.org>

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

                 reply	other threads:[~2007-04-05 23:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1175817336.7505.33.camel@localhost \
    --to=zlynx@acm.org \
    --cc=akpm@osdl.org \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox