From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kvm list <kvm@vger.kernel.org>,
lkft-triage@lists.linaro.org, kvmarm@lists.cs.columbia.edu,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>, James Morse <james.morse@arm.com>,
julien.thierry.kdev@gmail.com, suzuki.poulose@arm.com,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: arm64: gen-hyprel.c:40:10: fatal error: generated/autoconf.h: No such file or directory
Date: Mon, 01 Feb 2021 13:45:53 +0000 [thread overview]
Message-ID: <5f072f84c7c9b03ded810e56687935b2@kernel.org> (raw)
In-Reply-To: <CA+G9fYvzh5GEssPJHM=r2TVUKOhsFJ8jqrY+pP4t7+jF8ctz9A@mail.gmail.com>
On 2021-02-01 13:38, Naresh Kamboju wrote:
> Linux next 20210201 tag arm64 builds failed.
> kernel config attached to this email.
>
> BAD: next-20210201
> GOOD: next-20210129
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> arch/arm64/kvm/hyp/nvhe/gen-hyprel.c:40:10: fatal error:
> generated/autoconf.h: No such file or directory
> 40 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Could you please check with the fix suggested at [1]?
Thanks,
M.
[1] https://lore.kernel.org/r/20210201104251.5foc64qq3ewgnhuz@google.com
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2021-02-01 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 13:38 arm64: gen-hyprel.c:40:10: fatal error: generated/autoconf.h: No such file or directory Naresh Kamboju
2021-02-01 13:45 ` Marc Zyngier [this message]
2021-02-01 15:01 ` Naresh Kamboju
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=5f072f84c7c9b03ded810e56687935b2@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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).