How to replace the default uclibc based compiler with musleabihf or gnu compiler when using this board as a regular embedded version without the need for video training programs in the oem directory?
Replace arm lockchip830 Linux uclibcgnueabihf with https://musl.cc/armv7l-linux-musleabihf-cross.tgz (for Alpine) or https://developer.arm.com/-/media/Files ... ihf.tar.xz (for Ubuntu)
How to replace the default uclibc based compiler with musleabihf or gnu compiler when using this board as a regular embe
peterwillcn wrote: ↑2024-05-19 14:17 How to replace the default uclibc based compiler with musleabihf or gnu compiler when using this board as a regular embedded version without the need for video training programs in the oem directory?
Replace arm lockchip830 Linux uclibcgnueabihf with https://musl.cc/armv7l-linux-musleabihf-cross.tgz (for Alpine) or https://developer.arm.com/-/media/Files ... ihf.tar.xz (for Ubuntu)
Hello, currently, the feasibility of replacing Alpine or Ubuntu with native arm-lockchip830-Linux-uclibcgnueabihf is low. Neither Ubuntu's apt repositories nor Alpine's software repositories have corresponding uClibc versions. Additionally, many native software packages from alpine of ubuntu (such as bluetoothctl)require glibc and musl, but due to uClibc's limitations, it cannot fully support them. Therefore, a more feasible solution might be to use Docker containers to achieve compatibility. A significant obstacle is that the Rockchip kernel has poor support for Docker, and we will attempt to address this.
If the Docker container is used, it will lose the flexibility of GPIO hardware operation. Changing the compiler to musl or glib may be better, but port testing is also very troublesome. You can refer to the construction of the OpenWrt system, Openwrt uses the Musl compilation library
I'm sorry, I misunderstood your requirements earlier. I incorrectly assumed you needed to replace the compilation tools on Ubuntu or Alpine with the Rockchip arm-rockchip830-linux-uclibcgnueabihf- tool (enabling full functionality of Luckfox-pico in the presence of a package manager), which is a common topic of discussion in forums.peterwillcn wrote: ↑2024-05-23 4:04 If the Docker container is used, it will lose the flexibility of GPIO hardware operation. Changing the compiler to musl or glib may be better, but port testing is also very troublesome. You can refer to the construction of the OpenWrt system, Openwrt uses the Musl compilation library
So, are you referring to replacing the cross-compilation toolchain in Buildroot from uClibc to either glibc or Musl? Or is this for a different scenario? Generally, for a specific compilation tool (glibc or musl), it's more convenient to choose the corresponding system. This is usually easier than replacing the cross-compilation toolchain in Buildroot.
Yes, I am researching https://github.com/LuckfoxTECH/luckfox-pico Replace uclibc with musl to adapt to Alpine, please provide some guidance. Thank you.