Mkdir / DIR_TO_CHROOT/lib # create lib and lib64 folders
create lib and lib64 to host these dependencies.You need to copy those libraries into your DIR_TO_CHROOTĬp /bin/bash / DIR_TO_CHROOT/bin # copy bash Since the root has been changed the relative links to bash and other libraries no longer work. In my case, since ARM processors need many libraries, I copied my entire arm-linux-gnueabihf folder into my lib folder, allowing me to access my chroot.
#Q dir 6.57 full
I am using the full path to raspberry pi's libm.so.6 as an example : file /chroot/lib/arm-linux-gnueabihf/libm.so.6
To discover whether this is the case you can use the file tool. These may in turn depend on other libraries. You can use the ldd tool as directed in other answers on your static busybox binary to discover whether this is the case. Note that you may still need to copy your c library (libc.so.6), core math library (libm.so.6), namespace resolution library (libresolv.so.2), and kernel library (in my case, since I am using a raspberry pi, ld-linux-armhf.so.3). you'd need most of this disk space to store what you're locating with ldd anyway. This does increase the size of the binaries, but. This will build all necessary libraries into your binaries. When you build busybox it respects LDFLAGS=-static per their FAQ. Something no one has mentioned yet, if the goal is not to keep copies of libraries you locate with ldd.
0 kommentar(er)
