From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [arm64:for-next/core 52/52] arch/arm64/include/asm/probes.h:18:25: fatal error: asm/opcodes.h: No such file or directory
Date: Sat, 3 Dec 2016 14:08:30 +0000 [thread overview]
Message-ID: <20161203140830.4c94ac49@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <86h96lmh5p.fsf@arm.com>
On Sat, 03 Dec 2016 10:38:26 +0000
Marc Zyngier <marc.zyngier@arm.com> wrote:
> On Fri, Dec 02 2016 at 10:05:27 PM, kbuild test robot <fengguang.wu@intel.com> wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> > head: bca8f17f57bd76ddf2bbd2527eb890d6f588853e
> > commit: bca8f17f57bd76ddf2bbd2527eb890d6f588853e [52/52] arm64: Get rid of asm/opcodes.h
> > config: arm64-allmodconfig (attached as .config)
> > compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> > reproduce:
> > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > git checkout bca8f17f57bd76ddf2bbd2527eb890d6f588853e
> > # save the attached .config to linux build tree
> > make.cross ARCH=arm64
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from arch/arm64/include/asm/uprobes.h:14:0,
> > from include/linux/uprobes.h:61,
> > from include/linux/mm_types.h:13,
> > from include/linux/sched.h:27,
> > from arch/arm64/kernel/asm-offsets.c:21:
> >>> arch/arm64/include/asm/probes.h:18:25: fatal error: asm/opcodes.h: No such file or directory
> > #include <asm/opcodes.h>
> > ^
> > compilation terminated.
> > make[2]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
> > make[2]: Target '__build' not remade because of errors.
> > make[1]: *** [prepare0] Error 2
> > make[1]: Target 'prepare' not remade because of errors.
> > make: *** [sub-make] Error 2
>
> Blah. Bloody uprobes. Just deleting this line should be enough, as I
> can't see anything that actually depends on what is in the 32bit
> asm/opcodes.h.
>
> I can submit a patch if needed.
Well, another (slightly more serious) bug has cropped up, so I just sent
a small patch series that addresses both.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2016-12-03 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:05 [arm64:for-next/core 52/52] arch/arm64/include/asm/probes.h:18:25: fatal error: asm/opcodes.h: No such file or directory kbuild test robot
2016-12-03 10:38 ` Marc Zyngier
2016-12-03 14:08 ` Marc Zyngier [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=20161203140830.4c94ac49@why.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--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