From: free.amit.kumar@gmail.com (Amit Kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kconfig recursion error
Date: Tue, 22 Nov 2016 11:30:06 +0000 [thread overview]
Message-ID: <CAPTh4Ov34xY2Oe3EKNzGvoYJ3dw=fv1ugOe6Q+jePDQG-hqFqQ@mail.gmail.com> (raw)
In-Reply-To: <CAPTh4Ov2kHYnBxKzSs4WP8voK3RMUzi=RSN=mgou0mdz1LOoeQ@mail.gmail.com>
On Tue, Nov 22, 2016 at 4:51 PM Amit Kumar <free.amit.kumar@gmail.com>
wrote:
> Hi,
> When I configure kernel like,
> CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm make omap2plus_defconfig
> I get error as follows,
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/kconfig/conf.o
> SHIPPED scripts/kconfig/zconf.tab.c
> SHIPPED scripts/kconfig/zconf.lex.c
> SHIPPED scripts/kconfig/zconf.hash.c
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/conf
> drivers/remoteproc/Kconfig:3:error: recursive dependency detected!
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/remoteproc/Kconfig:3: symbol REMOTEPROC is selected by
> QCOM_ADSP_PIL
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
> drivers/remoteproc/Kconfig:81: symbol QCOM_ADSP_PIL depends on REMOTEPROC
> #
> # configuration written to .config
> #
> I think Documentation/kbuild/Kconfig.recursion-issue-02 is applicable,
> because REMOTEPROC is mentioned in depends on and select at different
> places.
>
> I am using a branch based on next-20161117.
> Regards,
> Amit Kumar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161122/13fbcb75/attachment.html
next prev parent reply other threads:[~2016-11-22 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 11:21 Kconfig recursion error Amit Kumar
2016-11-22 11:30 ` Amit Kumar [this message]
2016-11-22 17:02 ` Blatinox
2016-11-23 4:36 ` Amit Kumar
2016-11-23 6:57 ` Greg KH
2016-11-23 7:54 ` Amit Kumar
2016-11-23 8:51 ` Greg KH
2016-11-23 9:51 ` Amit Kumar
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='CAPTh4Ov34xY2Oe3EKNzGvoYJ3dw=fv1ugOe6Q+jePDQG-hqFqQ@mail.gmail.com' \
--to=free.amit.kumar@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).