update to Openwrt 19.07.4

[SvenRoederer]

update master to just released openwrt-19.07.3 openwrt-19.07.4, and update to HEAD of our packages feed.
We should merge even it will cause Issue #801, but what options do we have than fixing our wizard-code.

runtime-tested on ramips-mt76x8, ramips-mt7620 (ath79-generic)

EDIT: updated to OpenWrt-19.07.4, which has been released in the mean time.

[everloop2]

System: Linux 5.7.14-1-MANJARO (x86_64)

tried to compile and run into:

1. seems build doesnt like multithreading - various build breaks: make -j1 does help

2. Failed to build miniperl. Please run make minitest.

seems to be fixed in openwrt/packages#12391

The perl Configure file was matching GCC 10 against "1*" and treating it
as GCC 1, causing ABI breakage and segfaults.

Cherry-pick the upstream patch which fixes it to check against (e.g)
"1.*" instead, which will make it work for hundreds more GCC versions
to come.

Perl/perl5@6bd6308

[SvenRoederer]

@everloop2 seems you are always using to beeding edge OS.
Luckily the patch you mentioned was backported from master (openwrt/packages@65578a4) to openwrt-1907 (openwrt/packages@445c3d8). So as it fails to compile because of the seen failure, even the targeted release 19.07.3 is too old to include this fix.
I assume using SvenRoederer@7bf4963 (monthly rollup up to end of July 2020) will build.

Anyway, I in favor of forgetting of OpenWrt-19.07 and to jump to upcoming OpenWrt-20.x directly (#834).

[SvenRoederer]

Just rebased on master and updated to fresh OpenWrt-19.07.4.

I assume it has still the Web-UI issue #801, mentioned in the PR-message, but at least brings additional security-updates. It will probably also fix the build-issue mentioned by @everloop2 in #802 (comment)

[everloop2]

System: Linux 5.8.6-1-MANJARO (x86_64)

-> builds flawless - multithreading enabled:

make -j4 V=s TARGET=lantiq-xrx200 PACKAGES_LIST_DEFAULT=notunnel_xDSL

-> runtime tested: FritzBox7360 (mesh only)

some additons for Fritzbox support in future:

notunnel_xDSL.txt:

# SMP -> add /firmware/configs/lantiq-xrx200.config -> CONFIG_PACKAGE_irqbalance=m
irqbalance

# xDSL - prevents Luci WAN no protokoll bug (for DSL port boxes) -> add -> /firmware/configs/lantiq-xrx200.config -> CONFIG_PACKAGE_luci-proto-ipv6=m
luci-proto-ppp
luci-proto-ipv6

had to manually add luci-proto-ppp and luci-proto-ipv6 packages - without WAN port can not be edited due "protokoll missing" f.e. as LAN1 -> WAN uplink

[SvenRoederer]

Thanks for checking.
Do we have a lantiq-xrx200 target already?

Regading luci-proto-ppp and irqbalance:

• since some time I've this patch included SvenRoederer@b78f362 to build irqbalance.
• luci-proto-ppp is required for the DSL-port, which is WAN?
• both packages seem hardware-related (per board), which can not be well mapped in our build-system. To also enable board-specific packages I had adapted the Gluon-build-system. This offers a way to implement this. See implement Gluon build-framework #765 (see "packages =" of https://github.com/freifunk-berlin/firmware/blob/gluon-scripts/targets/ath79-generic)

[everloop2]

Thanks for checking.
Do we have a lantiq-xrx200 target already?

yes: Fritzbox 7360(sl)(V2) and have a FritzBox3370 runnig

Regading luci-proto-ppp and irqbalance:

• since some time I've this patch included SvenRoederer@b78f362 to build irqbalance.

-> fix irqbalance directory not created -> openwrt/packages#12377 -> "fixed" by: openwrt/packages@4f0c847, somehow "irqbalance" directory is not created :/
workaround: firmware/openwrt/package/base-files/files/etc/init.d/boot -> add "mkdir -p /var/run/irqbalance"
-> add irqbalance autostart -> /firmware/openwrt/package/base-files/files/etc/rc.local -> /usr/sbin/irqbalance
-> to check if interrupts are distributed to 2nd core: cat /proc/interrupts -> never seen irqbalance distribute interrupts other then CPUcore ones o.O

• luci-proto-ppp is required for the DSL-port, which is WAN?

yes: without WAN is not editable - if firmware is a default "freifunk" build missing packages can be installed via opkg (for my builds i include them manually for now)

• both packages seem hardware-related (per board), which can not be well mapped in our build-system. To also enable board-specific packages I had adapted the Gluon-build-system. This offers a way to implement this. See implement Gluon build-framework #765 (see "packages =" of https://github.com/freifunk-berlin/firmware/blob/gluon-scripts/targets/ath79-generic)

This will do the trick ;)

[SvenRoederer]

regarding luci-proto-wan and irqbalance: I'm not sure if we should add this into the generic packagelists, as both are more board-specific.
Can you open a new issue about handling such packages? So we can find a solution for this and don't have to kidnap this one here.

[SvenRoederer]

System: Linux 5.8.6-1-MANJARO (x86_64)

-> builds flawless - multithreading enabled:

@everloop2 Do you have permissions to merge? (I assume you have) So will you do the merge if it's looks good for you?

[everloop2]

System: Linux 5.8.6-1-MANJARO (x86_64)
-> builds flawless - multithreading enabled:

@everloop2 Do you have permissions to merge? (I assume you have) So will you do the merge if it's looks good for you?

Yes it shows Squash and merge - did not do it cause its not my pull request and so: "nobody can blame me" xP

regarding luci-proto-wan and irqbalance: I'm not sure if we should add this into the generic packagelists, as both are more board-specific.
Can you open a new issue about handling such packages? So we can find a solution for this and don't have to kidnap this one here.

Yep, will open issue for WAN_DSL boxes like Fritzboxes.

[SvenRoederer]

Yep, will open issue for WAN_DSL boxes like Fritzboxes.

--> #838