diff options
author | Eneas U de Queiroz <cotequeiroz@gmail.com> | 2020-04-07 17:07:19 -0300 |
---|---|---|
committer | Petr Štetiar <ynezz@true.cz> | 2020-04-09 12:51:10 +0200 |
commit | 2e6b6f9fcaaea33b0b66026d9f40e775470c5ef4 (patch) | |
tree | 1d15f39ee11b2d0cf26f6bd297b667343a426db8 /package/utils | |
parent | 4627b5df69fac65e35429b3f876748a59c1bb47a (diff) | |
download | upstream-2e6b6f9fcaaea33b0b66026d9f40e775470c5ef4.tar.gz upstream-2e6b6f9fcaaea33b0b66026d9f40e775470c5ef4.tar.bz2 upstream-2e6b6f9fcaaea33b0b66026d9f40e775470c5ef4.zip |
kernel: add @IPV6 dependency to ipv6 modules
IPv6 modules should all depend on @IPV6, to avoid circular dependencies
problems, especially if they select a module that depends on IPV6 as
well. In theory, if a package A depends on IPV6, any package doing
'select A' (DEPENDS+= A) should also depend on IPV6; otherwise selecting
A will fail. Sometimes the build system is forgiving this, but
eventually, and unexpectedly, it may blow up on some other commit.
Alternatively one can conditionally add IPv6 dependencies only if
CONFIG_IPV6 is selected: (DEPENDS+= +IPV6:package6).
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Diffstat (limited to 'package/utils')
0 files changed, 0 insertions, 0 deletions