Recent build issues on master (r7500v2 kernel 4.19 - but I think this is unrelated)

3 issues. A separate post for each in this thread.

EDIT: I've stripped down my (diff) config, made a change to the r7500v2 makefile dep to workaround the ath10k-ct issue, and that works around these issues.

Thanks to @slh for the example minimal diffconfig on irc (and for confirming the change to target/linux/ipq806x/image/Makefile).

my patch looks like:

--- a/target/linux/ipq806x/image/Makefile
+++ b/target/linux/ipq806x/image/Makefile
@@ -184,7 +184,7 @@ define Device/netgear_r7500v2
 	PAGESIZE := 2048
 	BOARD_NAME := r7500v2
-	DEVICE_PACKAGES := ath10k-firmware-qca99x0-ct ath10k-firmware-qca988x-ct
+	DEVICE_PACKAGES := ath10k-firmware-qca99x0-ct-htt
 TARGET_DEVICES += netgear_r7500v2

Building for r7500v2 ipq806x (kernel 4.19 - but none of these issues were a problem ~ 1 month ago).

All occurred after updating my git tree (08.30.2019) and make distclean:

Issue 1 the build stops with

.config:4002:warning: symbol value 'm' invalid for NF_NAT_REDIRECT
* Restart config...
* MultiProtocol Label Switching
MultiProtocol Label Switching (MPLS) [Y/?] y
  MPLS: GSO support (NET_MPLS_GSO) [M/y/?] m
  MPLS: routing support (MPLS_ROUTING) [N/m/?] (NEW) 

If I choose m for MPLS: routing support (MPLS_ROUTING) [N/m/?] (NEW) the build continues

Issue 2:

EDIT: make menuconfig shows what I want which is:

compiling for ath10k-firmware-qca99x0-ct-htt installed in image and ath10k-firmware-qca99x0-ct as module.

and my .config looks like:

cat .confing | grep ath10k
# ath10k Board-Specific Overrides
# CONFIG_PACKAGE_ath10k-firmware-qca4019 is not set
# CONFIG_PACKAGE_ath10k-firmware-qca4019-ct is not set
# CONFIG_PACKAGE_ath10k-firmware-qca4019-ct-htt is not set
# CONFIG_PACKAGE_ath10k-firmware-qca6174 is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9887 is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9887-ct is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9887-ct-htt is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9888 is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9888-ct is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9888-ct-htt is not set
# CONFIG_PACKAGE_ath10k-firmware-qca988x is not set
# CONFIG_PACKAGE_ath10k-firmware-qca988x-ct-htt is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9984 is not set
# CONFIG_PACKAGE_ath10k-firmware-qca9984-ct-htt is not set
# CONFIG_PACKAGE_ath10k-firmware-qca99x0 is not set

I (now) get the error:

Collected errors:                                                               
 * check_data_file_clashes: Package ath10k-firmware-qca99x0-ct wants to install\
 file /home/n/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linu\
        But that file is already provided by package  * ath10k-firmware-qca99x0\
 * check_data_file_clashes: Package ath10k-firmware-qca99x0-ct wants to install\
 file /home/n/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linu\
        But that file is already provided by package  * ath10k-firmware-qca99x0\
 * opkg_install_cmd: Cannot install package ath10k-firmware-qca99x0-ct.         
Installing ath10k-firmware-qca99x0-ct (2019-06-28-7651f5bb-1) to root...        
/home/n/openwrt/include/ recipe for target 'target-dir-261ef631' f\
make[5]: *** [target-dir-261ef631] Error 255                                    
make[5]: *** Waiting for unfinished jobs....
Installing ath10k-firmware-qca988x-ct (2019-06-28-7651f5bb-1) to root...
Configuring ath10k-firmware-qca988x-ct.

did something change?

If the maintainer happens to see this... please remove the dependency on ath10k-firmware-qca988x-ct as there is no hardware on the r7500v2 that uses this firmware - I've been running both 2.4 and 5 GHz off the 99x0 firmware without issue for over a year now.

Issue 3:

Apologies, I seem to have deleted the build log for this one but the build fails on kmod-pf-ring.

changing the config to:

cat .config | grep pf-ring
# CONFIG_PACKAGE_kmod-pf-ring is not set

works around this for now (I don't use it).

Solutions (more workarounds) are in the first post.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.