From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 206907] New: backport_iwlwifi 8324 Can't be compiled after make clean
Date: Sun, 22 Mar 2020 02:41:49 +0000 [thread overview]
Message-ID: <bug-206907-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206907
Bug ID: 206907
Summary: backport_iwlwifi 8324 Can't be compiled after make
clean
Product: Backports project
Version: unspecified
Kernel Version: 4.19
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Backports
Assignee: backports@vger.kernel.org
Reporter: realasking@outlook.com
Regression: No
Hi all.
I failed to make the intel backport_iwlwifi driver for ax200 (version 8324)
after I make clean when I had update my kernel from 4.19.109 manjaro to
4.19.112 manjaro.
It reported that:
cc -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer -c
-o conf.o conf.c
make[5]: *** 没有规则可制作目标“zconf.tab.o”，由“conf” 需求。 停止。
make[5]: *** 正在等待未完成的任务....
make[4]: *** [Makefile.real:39：oldconfig] 错误 2
make[3]: *** [Makefile:43：oldconfig] 错误 2
make[2]: *** [Makefile.real:73：backport-include/backport/autoconf.h] 错误 2
make[1]: *** [Makefile:43：modules] 错误 2
make: *** [Makefile:30：default] 错误 2
After comparing originally downloaded folder and my compilation folder, I found
that the two source files zconf.tab.c and zconf.lex.c in the kconf folder were
deleted when make clean was executed. If which were copied, the modules could
be successfully produced again.
But this would cause dkms compilation falls. Could you make a fix for it?
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe backports" in
reply other threads:[~2020-03-22 2:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-206907-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@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;
as well as URLs for NNTP newsgroup(s).