Buildroot sdk

2025-01-13 9:36

Hi! I've been using your buildroot sdk for a couple of months to customize my linux image for personal needs. Now i'm wondering, can i use original buildroot repository instead of your local tarball? They seem to be pretty similar to each other at first glance, but maybe there is some hidden features that i should to know about? Thank you in advance!

2025-01-14 6:49

The SDK has been localized and configured. If you need to use the original version, you need to port it yourself, and we do not provide additional assistance.

2025-01-18 10:36

Thank you! I've managed to reconfigure original buildroot to build rootfs for luckfox, but i found a really weird problem, that also arises in your buildroot tarball:
When buildroot generates host part of output directory, it creates toolchainfile.cmake for convenient cross-compilation process of user-space applications. In this toolchainfile.cmake C and C++ compilers are set as symbolic links to binary called toolchain-wrapper, that, according to buildroot documentation (https://buildroot.org/downloads/manual/ ... _toolchain) transparently adds proper arguments to call original external toolchain compilers. However, using this toolchainfile.cmake and toolchain-wrapper as C++ comiler ruins linkage to libsample_comm.a with several errors:

Code: Select all

libsample_comm.a(sample_comm_isp.o): relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC

Code: Select all

ibsample_comm.a(sample_comm_isp.o)(.text+0xc8): unresolvable R_ARM_CALL relocation against symbol `printf'

Code: Select all

final link failed: nonrepresentable section on output

Adding -fPIC as linker option doesn't help there, but what helps is changing C++ compiler location from that toolchain-wrapper symbolic link to original toolchain compiler path. To reproduce this bug you can use buildroot's toolchainfile.cmake and build any application that is being linked to libsample_comm.a.
Calling these toolchain-wrapper symbolic links (arm-rockchip830-linux-uclibcgnueabihf-gcc and arm-rockchip830-linux-uclibcgnueabihf-g++), that are located at buildroot/output/host/bin/ directory, in terminal causes these errors:

2025-01-18 10:41

Just use our SDK directly. We do not provide technical support for porting buildroot after modification. We generally limit it to product use. Thank you for your understanding and support!

2025-01-21 12:57

Sorry for bothering you, problem disappeared after catching up with your sdk. Seems like it was problem between versions of media libraries)