From: Doug Ledford <dledford@redhat.com>
To: oulijun <oulijun@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 【build error report for for next branch】
Date: Mon, 23 Oct 2017 11:24:39 -0400 [thread overview]
Message-ID: <1508772279.3325.6.camel@redhat.com> (raw)
In-Reply-To: <e6b315b2-7e38-c401-97f0-06bb0fafa11e@huawei.com>
On Wed, 2017-10-18 at 14:21 +0800, oulijun wrote:
> 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?
[ snip ]
> 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
You've probably got a bad .config for your cross build. I doubt it's
related to my tree since I have done any patches to the tracing
subsytem and that's what's failing.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
next prev parent reply other threads:[~2017-10-23 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 6:21 【build error report for for next branch】 oulijun
2017-10-23 15:24 ` Doug Ledford [this message]
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=1508772279.3325.6.camel@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oulijun@huawei.com \
/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