[SOLVED] Kconfig recursive dependencies - +strongswan

For Developers
1

Hi all,
I'm working on building a package for which I want to pull strongswan in as a dependency. For reference, I'm working on 18.06 branch.

As part of doing this, I'm trying things very similar to:

DEPENDS:=+strongswan-minimal +strongswan-ipsec +strongswan-mod-pem...

The issue is that I'm getting Kconfig recursive dependencies errors and I'm unable to break the cycles. The smallest amount of errors that I can end up with is something like:

tmp/.config-package.in:51319:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:51319:   symbol PACKAGE_strongswan is selected by PACKAGE_my_package
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:7870:    symbol PACKAGE_my_package depends on PACKAGE_kmod-ipsec
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:12459:   symbol PACKAGE_kmod-ipsec is selected by PACKAGE_strongswan

What is the correct way for me to be able to bring in strongswan as a dependency?

Also, if I need to modify the strongswan Makefile to get there, that's fine. I don't know where to start though. I'll happily take links to how this has been addressed on other packages.

Thanks for your time and help!
Vincent

2
1 Like
3

Thanks @slh for the working example!

It turns out with your helps, I was able to figure out that the issue came by adding one more dependency that I had omitted as not relevant in the ... part of my initial question (+vtiv4).
It was also able to solve my original issue by adding an explicit dependency to kmod-ipsec (not sure if that's the cleanest way to do it but it does the job for now).

So for people in doubt when they get something like the circular dependency that I met above, consider adding a direct dependency to one of the listed elements in the circular list. I feel it's got a good chance to break the circle. My feeling is that these things derived from strange formats down the line in other Makefiles, but a workaround is better than nothing!

4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.