strongswan Dependency cycle
Open
Nobody has claimed this yet.
stale
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
tmp/.config-package.in:130024: symbol PACKAGE_strongswan-mod-kdf depends on PACKAGE_strongswan
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:130200:error: recursive dependency detected!
tmp/.config-package.in:130200: symbol PACKAGE_strongswan-mod-openssl is selected by PACKAGE_strongswan-mod-openssl
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
`````
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dependency errors in tmp/.config-package.in and read the referenced “Kconfig recursive dependency limitations” section in Documentation/kbuild/kconfig-language.rst. Determine which strongswan package relationships create the recursive dependencies; done means the package configuration no longer reports these cycles.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100