From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: Intermittent efi libstub build errors on arm64
Date: Fri, 6 Mar 2015 10:34:29 +0000 [thread overview]
Message-ID: <20150306103428.GA8045@linaro.org> (raw)
Hi,
I've run into some strange build errors with 3.19.
If I set a high number of parallel jobs, I sometimes get build errors
such as:
mv: cannot stat ?drivers/firmware/efi/libstub/.fdt.o.tmp?: No such file or directory
AR drivers/firmware/efi/libstub/lib.a
scripts/Makefile.build:257: recipe for target 'drivers/firmware/efi/libstub/fdt.o' failed
make[1]: *** [drivers/firmware/efi/libstub/fdt.o] Error 1
Makefile:939: recipe for target 'drivers/firmware/efi/libstub' failed
make: *** [drivers/firmware/efi/libstub] Error 2
and,
fixdep: error opening depfile: drivers/firmware/efi/libstub/.efi-stub-helper.o.d: No such file or directory
scripts/Makefile.build:257: recipe for target 'drivers/firmware/efi/libstub/efi-stub-helper.o' failed
make[1]: *** [drivers/firmware/efi/libstub/efi-stub-helper.o] Error 2
Makefile:939: recipe for target 'drivers/firmware/efi/libstub' failed
make: *** [drivers/firmware/efi/libstub] Error 2
make: *** Waiting for unfinished jobs....
I think some dependency information/header includes may need tweaking
somewhere. Has anyone else come across this, or know more?
Cheers,
--
Steve
next reply other threads:[~2015-03-06 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:34 Steve Capper [this message]
2015-03-06 11:09 ` Intermittent efi libstub build errors on arm64 Steve Capper
2015-03-06 12:11 ` Ard Biesheuvel
2015-03-06 12:17 ` Steve Capper
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=20150306103428.GA8045@linaro.org \
--to=steve.capper@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).