[OpenWrt-Devel] Phase2 packages buildbot has failed since the kconfig changes
cotequeiroz at gmail.com
Sat Apr 11 15:21:34 EDT 2020
It would be easier if I could reproduce the bug locally.
I would like to take a look at the failed 'Config-build.in' (haven't
seen this file ever), and 'tmp/.config-package.in'.
Meanwhile, I will try my luck with the SDK, which I don't do very often myself.
Do the phase1 bots have the feeds enabled? Perhaps something in the
packages feed generates the unmet direct dependency. I recall python
bluetooth module picking up kmod-bluetooth without checking one of its
dependencies (USB_SUPPORT, perhaps). Anyway, I hope I can find out
something by looking at the config.in sources.
On Sat, Apr 11, 2020 at 1:17 PM Hannu Nyman <hannu.nyman at iki.fi> wrote:
> Hannu Nyman kirjoitti 11.4.2020 klo 17.07:
> > But most errors seem to be related to recursive errors inside the rather
> > complex mac80211 wifi driver collection. I have a hunch that for buildbot
> > the "treat recursive dependencies as warnings instead of errors" option
> > (from 3204430e3 ) should be activated in the config binary, or
> > alternatively some major work for re-organising the mac80211 submodule
> > dependencies needs to be done.
> One interesting aspect:
> The kmod related errors surface in the phase2 buildbot that uses SDK to
> compile non-kernel packages. The kernel and related packages are built by the
> phase1 images buildbot that also builds the SDK, so this phase2 packages
> buildbot should not even touch the kmods. But still the recursive config
> error realted to them apparently break the buildbot run.
> That makes me wonder if the current settings have wider impact on SDK usage.
> Possibly the SDK reacts badly to the current config logic. (Personally I only
> compile with the full toolchain, so I have no experience with the SDK.)
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel