From: Pavel Machek <pavel@ucw.cz>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Kernel build fails "cannot move ‘arch/arm/boot/compressed/.piggy.gzip.o.tmp" then succeeds
Date: Mon, 11 Jan 2016 10:57:59 +0100 [thread overview]
Message-ID: <20160111095758.GA22768@amd> (raw)
In-Reply-To: <569374A2.5050602@suse.cz>
On Mon 2016-01-11 10:23:46, Michal Marek wrote:
> On 2016-01-11 09:58, Pavel Machek wrote:
> > Second try:
> >
> > 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
>
> I guess you are missing 3939f3345050 ("ARM: 8418/1: add boot image
> dependencies to not generate invalid images"). Without this fix and with
> 'make uImage zImage', two make instances try to produce a zImage at the
> same time.
Since it is known, I have just updated my scripts not to trigger it in
4.0 kernel. I'll try to get this project to move to newer kerenl, but
it needs realtime extensions so I'm not sure if/when we can do that.
Thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-01-11 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 8:26 Kernel build fails "cannot move ‘arch/arm/boot/compressed/.piggy.gzip.o.tmp" then succeeds Pavel Machek
2016-01-11 8:58 ` Pavel Machek
2016-01-11 9:23 ` Michal Marek
2016-01-11 9:57 ` Pavel Machek [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=20160111095758.GA22768@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).