Page 1 of 1

pico max / How to include libpthread.so into buildroot image ?

Posted: 2025-01-23 8:49
by simonsayz
./buildroot.sh buildrootconfig
-> include minicom -> build image ok (exists minicom in result image )
-> tool chain -> external toolchaing c lib (glibc) -> (fail / not found in /usr/lib )

How to include libpthread.so in /usr/lib/libpthread.so ?

Which buildrootconfig option is including libpthread.so in result image ?

My test program is running in ubuntu (sd image), but can't run in buildroot. (flash)

Please, Know me the right options in buildrootconfig.
Thanks you.

Re: pico max / How to include libpthread.so into buildroot image ?

Posted: 2025-01-24 8:08
by Ryand
You need to cross compile the uclibc version of libpthread.so, transfer the file to/usr/lib on the buildroot system, and do not need to modify the c lib supported by the system.

Re: pico max / How to include libpthread.so into buildroot image ?

Posted: 2025-02-01 17:54
by simonsayz
Thanks you for fast reply.

Can I rebuild glibc build root image ? (Pico Max + nand image )
Because My compiler (FPC : Free Pascal Compiler ) thread model support pthread & glibc only.

I try build image with glibc option. but fail to build.

my test
-------------------------------------------------------
#1 ./build.sh lunch
#2 ./build.sh
#3 compling...
#4 ./build.sh buildrootconfig
#5 disable python 3 option (Target packages -> Interpereter languages and scripting -> pythone3)

-------------------------------------------------------
Case 1. Toolchain (External toolchain /Default ) -> External toolchain C library ( uClibc -> glibc )
./build.sh clean
./build.sh
-> incorrect selection of the C library
Running build_rootfs failed

Case 2. Toolchain (Buildroot toolchan )
build & image ok -> but can't be bootable

How to get build root image with glibc version ?

Thanks a lot.

Re: pico max / How to include libpthread.so into buildroot image ?

Posted: 2025-02-05 8:27
by Ryand
I have not tested using glibc to build buildroot. As it is a customized SDK, many things need to be reset after using glibc, and the SDK needs to be greatly modified. There are currently no relevant plans. Suggest pulling the buildrooot repository again and building it outside of the SDK.