TIP OpenWiFi compiles Edgecore EAP101 error

[tianshenxiafan]

Hello gurus,

I am using TIP OpenWiFi code to compile an AP for the edgecore_ eap101 model.

I followed the steps on the TIP OpenWiFi official website, https://github.com/Telecominfraproject/wlan-ap ，

When I reached the second step:./scripts/gen_config.py edgecore_eap101, an error occurs during the generation of. config. Below, I have shown some error logs.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

WARNING: Makefile 'package/utils/busybox/Makefile' has a dependency on 'libpam', which does not exist

WARNING: Makefile 'package/feeds/ipq807x/qca-nss-clients/Makefile' has a dependency on 'kmod-qca-nss-cfi-cryptoapi', which does not exist

tmp/.config-package.in:21609: symbol PACKAGE_kmod-cfg80211 is selected by PACKAGE_kmod-mac80211

tmp/.config-package.in:21636: symbol PACKAGE_kmod-mac80211 is selected by PACKAGE_ucode-mod-nl80211

For a resolution refer to Documentation/kbuild/kconfig-language.rst

subsection "Kconfig recursive dependency limitations"

tmp/.config-package.in:15761:error: recursive dependency detected!

tmp/.config-package.in:15761: symbol PACKAGE_kmod-bonding is selected by PACKAGE_kmod-qca-nss-drv-lag-mgr

tmp/.config-package.in:15040: symbol PACKAGE_kmod-qca-nss-drv-lag-mgr depends on PACKAGE_kmod-bonding

For a resolution refer to Documentation/kbuild/kconfig-language.rst

subsection "Kconfig recursive dependency limitations"

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The attachment is a detailed log of my operation process

I didn't encounter this issue when compiling with the same code a week ago. What is the reason for this error now? Please help me

Thank you in advance[file:///C:/Users/luzhe/Desktop/openwifi-setup.log](file:///C:/Users/luzhe/Desktop/openwifi-setup.log)

[frollic]

EAP101 isn't supported by OpenWRT, but you knew this already.

You need to ask the people who provided you with the code.

---

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.