From: Pavel Machek <pavel@ucw.cz>
To: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Kernel build fails "cannot move ‘arch/arm/boot/compressed/.piggy.gzip.o.tmp" then succeeds
Date: Mon, 11 Jan 2016 09:26:03 +0100 [thread overview]
Message-ID: <20160111082603.GA24950@amd> (raw)
Hi!
Ok, I guess it is second time I see it.
This time it is while cross-compiling 4.0 kernel on 4.4-rc5. Failure
is:
AS arch/arm/boot/compressed/piggy.gzip.o
AS arch/arm/boot/compressed/piggy.gzip.o
mv: cannot move ‘arch/arm/boot/compressed/.piggy.gzip.o.tmp’ to ‘arch/arm/boot/compressed/.piggy.gzip.o.cmd’: No such file or directory
scripts/Makefile.build:294: recipe for target 'arch/arm/boot/compressed/piggy.gzip.o' failed
make[2]: *** [arch/arm/boot/compressed/piggy.gzip.o] Error 1
arch/arm/boot/Makefile:52: recipe for target 'arch/arm/boot/compressed/vmlinux' failed
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
arch/arm/Makefile:308: recipe for target 'zImage' failed
make: *** [zImage] Error 2
make: *** Waiting for unfinished jobs....
I'm building it like this...
eval ` eldk-switch.sh -r 5.4 armv7a`
ARCH=arm long make -j 3 zImage uImage LOADADDR=0x8000 && \
It builds ok after re-run. Is building zImage and uImage at the same
time bad idea?
pavel@duo:~/stahl/linux$ ./mkit
Setup for armv7a (using ELDK 5.4)
25205 (process ID) old priority 0, new priority 10
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
Kernel: arch/arm/boot/zImage is ready
Image arch/arm/boot/uImage is ready
make took 0 minutes 37 seconds
Any other ideas?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2016-01-11 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 8:26 Pavel Machek [this message]
2016-01-11 8:58 ` Kernel build fails "cannot move ‘arch/arm/boot/compressed/.piggy.gzip.o.tmp" then succeeds Pavel Machek
2016-01-11 9:23 ` Michal Marek
2016-01-11 9:57 ` Pavel Machek
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=20160111082603.GA24950@amd \
--to=pavel@ucw.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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.