From: Sam Ravnborg <sam@ravnborg.org>
To: Mart?n Chikilian <slack@efn.uncor.edu>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: Weird problem when compiling kernel
Date: Fri, 3 Sep 2004 21:28:53 +0200 [thread overview]
Message-ID: <20040903192853.GA15783@mars.ravnborg.org> (raw)
In-Reply-To: <4138727D.8040602@efn.uncor.edu>
On Fri, Sep 03, 2004 at 10:32:45AM -0300, Mart?n Chikilian wrote:
>
> >
> rm -rf .tmp_versions
> mkdir -p .tmp_versions
> make -f scripts/Makefile.build obj=scripts/basic
> make -f scripts/Makefile.build obj=scripts
> make -f scripts/Makefile.build obj=arch/i386/kernel
> arch/i386/kernel/asm-offsets.s
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> make -f scripts/Makefile.build obj=init
> make -f scripts/Makefile.build obj=usr
> gcc -Wp,-MD,usr/.gen_init_cpio.d -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -o usr/gen_init_cpio usr/gen_init_cpio.c
> ./usr/gen_init_cpio > usr/initramfs_data.cpio
Here I expected gzip to be called???
> gcc -Wp,-MD,usr/.initramfs_data.o.d -nostdinc -iwithprefix include
> -D__KERNEL__ -Iinclude -D__ASSEMBLY__
> -Iinclude/asm-i386/mach-default -c -o usr/initramfs_data.o
> usr/initramfs_data.S
> ld -m elf_i386 -r -o usr/built-in.o
And this looks pretty veird to me also. I should have one inputfile listed.
> ld: no input files
> scripts/Makefile.build:229: *** [usr/built-in.o] Error 1
> Makefile:600: *** [usr] Error 2
>
Plase apply following patch and post output of:
rm usr/*o
make V=1
Apply patch using:
$ patch -p1 < my_patch
when current directory is root of kernel tree.
Sam
===== usr/Makefile 1.10 vs edited =====
--- 1.10/usr/Makefile 2004-08-10 21:42:40 +02:00
+++ edited/usr/Makefile 2004-09-03 21:22:16 +02:00
@@ -18,15 +18,20 @@
# Commented out for now
# initramfs-y := $(obj)/root/hello
+$(warning obj-y=$(obj-y))
+$(warning obj=$(obj))
+
quiet_cmd_cpio = CPIO $@
cmd_cpio = ./$< > $@
$(obj)/initramfs_data.cpio: $(obj)/gen_init_cpio $(initramfs-y) FORCE
+ @echo cpio: $@ - $^ - $?
$(call if_changed,cpio)
targets += initramfs_data.cpio
$(obj)/initramfs_data.cpio.gz: $(obj)/initramfs_data.cpio FORCE
+ @echo gzip: $@ - $^ - $?
$(call if_changed,gzip)
targets += initramfs_data.cpio.gz
prev parent reply other threads:[~2004-09-03 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 12:50 Martín Chikilian
2004-09-02 20:19 ` Sam Ravnborg
2004-09-03 13:32 ` Martín Chikilian
2004-09-03 19:28 ` Sam Ravnborg [this message]
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=20040903192853.GA15783@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slack@efn.uncor.edu \
/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