On 2016-07-06 07:27, Daniel Curran-Dickinson wrote: > Hi Felix, > > I'd like clarification on > > https://git.lede-project.org/?p=source.git;a=commitdiff;h=71753a8286dcb > 4dedbb6d4792b0fd5dd305c3338 > > for two reasons: with a patch picking a default SSL provider, the two > packages in commit emitted a recursive dependency error. > > It made sense to me that it would be considered a recursive dependency > because the section ends up looking like: > > config PACKAGE_libustream-openssl > > .. > depends on libopenssl if PACKAGE_libustream-openssl > > which looks to me like a recursive dependency (certainly I've had > KConfig complain at me over that sort of construct, once you add in a > something a dependency or select on PACKAGE_libustream-openssl in some > other location. > > I'm confused about how this is not a recursive dependency? The issue is probably in the patch, or the patch triggers a bug in the metadata script. Without the patch, no recursive dependency is generated. This kind of syntax is frequently used to indicate that the corresponding build dependency should be conditional as well.
I will take another look at your patch to see if I can figure out what triggers the issue in your case. - Felix _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
