From: oulijun <oulijun@huawei.com>
To: Doug Ledford <dledford@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 【build error report for for next branch】
Date: Wed, 18 Oct 2017 14:21:32 +0800 [thread overview]
Message-ID: <e6b315b2-7e38-c401-97f0-06bb0fafa11e@huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
Hi, Doug Ledford
I am use the for-next branch for building and the result is fail.
Is the branch a bug or my buidl way incorrectly?
My build way as follows:
1. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig
2. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j16
o00290482@linux-ioko:~/for-1/rdma> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j16
arch/arm64/Makefile:23: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
arch/arm64/Makefile:44: Detected assembler with broken .inst; disassembly will be unreliable
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/utsrelease.h
CHK include/generated/timeconst.h
CHK include/generated/bounds.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
CC [M] drivers/gpu/drm/tegra/trace.o
In file included from drivers/gpu/drm/tegra/trace.h:68:0,
from drivers/gpu/drm/tegra/trace.c:2:
./include/trace/define_trace.h:88:43: fatal error: ./trace.h: No such file or directory
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
^
compilation terminated.
make[4]: *** [drivers/gpu/drm/tegra/trace.o] Error 1
make[3]: *** [drivers/gpu/drm/tegra] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [drivers/gpu/drm] Error 2
make[1]: *** [drivers/gpu] Error 2
make: *** [drivers] Error 2
[-- Attachment #2: .config --]
[-- Type: application/xml, Size: 160419 bytes --]
next reply other threads:[~2017-10-18 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 6:21 oulijun [this message]
2017-10-23 15:24 ` Doug Ledford
2017-10-24 1:55 ` oulijun
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=e6b315b2-7e38-c401-97f0-06bb0fafa11e@huawei.com \
--to=oulijun@huawei.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®