Figured I'd stop by to check on the merge status, seems like it's still some way off sadly.
When building from commit 097e9bf9d842dc20932e85e38f9034ab58f499d9 I eventually run into what appears to be a conflict between different TLS/SSL libraries. Has something about the build procedure changed? I've simply tried doing this again since it seemed to work for people.
Collected errors:
* check_data_file_clashes: Package libustream-wolfssl20201210 wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib/libustream-ssl.so
But that file is already provided by package * libustream-mbedtls20201210
* opkg_install_cmd: Cannot install package libustream-wolfssl20201210.
* check_data_file_clashes: Package px5g-wolfssl wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/usr/sbin/px5g
But that file is already provided by package * px5g-mbedtls
* opkg_install_cmd: Cannot install package px5g-wolfssl.
make[1]: *** [package/Makefile:70: package/install] Error 255
make[1]: Leaving directory '/home/pngu/src/github.com/boretom/openwrt-fork'
make: *** [/home/pngu/src/github.com/boretom/openwrt-fork/include/toplevel.mk:231: package/install] Error 2
Normally I'd just dig in and figure out how to resolve the conflict, but given that it's not just one, but 3 cryptographic libraries causing trouble on a flavor of Linux I'm not terribly familiar with tells me I should rather ask for help 