From: free.amit.kumar@gmail.com (Amit Kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kconfig recursion error
Date: Wed, 23 Nov 2016 04:36:57 +0000 [thread overview]
Message-ID: <CAPTh4OsJ-LYWvx2HqmqWVsf_DDtoBrZJJ+zRK0u3c8CELjaGfg@mail.gmail.com> (raw)
In-Reply-To: <20161122120212.2e9953fe@blatinox-arch>
On Tue, Nov 22, 2016 at 10:32 PM Blatinox <blatinox@lse.epita.fr> wrote:
> Hi Amit,
>
> On Tue, 22 Nov 2016 11:30:06 +0000
> Amit Kumar <free.amit.kumar@gmail.com> wrote:
>
> > 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.
> >
> It has been fixed by commit cc7d54b05057 ("remoteproc: adsp-pil: fix
> recursive dependency") available since next-20161122.
>
> I am wondering one thing: is the dependency on REMOTEPROC necessary
> for QCOM_ADSP_PIL symbol (and other symbols in the same file) even if
> this symbol is defined inside an 'if REMOTEPROC' block ?
>
Yes it works in next-20161122. I'm in IST so I get next tree update the
next day. If I want to create a linux-next tree and publish it on github
publicly then what I need to do?
I think MAINTAINERS file may provide maintainers repos but there may be
certain tasks to be performed which I as a newbie don't know.
I also want to do this because as push, pulling don't require
authentication.
I'm obliged to mere guidance.
Currently I'm unable to discuss it in detail. As my knowledge of kernel
grows I will start discussing any issue in detail.
Regards,
Amit Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161123/8f7287f9/attachment-0001.html
next prev parent reply other threads:[~2016-11-23 4:36 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
2016-11-22 17:02 ` Blatinox
2016-11-23 4:36 ` Amit Kumar [this message]
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=CAPTh4OsJ-LYWvx2HqmqWVsf_DDtoBrZJJ+zRK0u3c8CELjaGfg@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).