cc-tool
cc-tool copied to clipboard
Static configuration / compilation not working?
Configuring with ./configure --enable-static --enable-static-boost --disable-shared
and building on the Pi still seems to result in the following:
$ ldd cc-tool
linux-vdso.so.1 (0xbef9c000)
/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f1a000)
libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0xb6ef5000)
libboost_filesystem.so.1.67.0 => /usr/lib/arm-linux-gnueabihf/libboost_filesystem.so.1.67.0 (0xb6ece000)
libboost_regex.so.1.67.0 => /usr/lib/arm-linux-gnueabihf/libboost_regex.so.1.67.0 (0xb6dd7000)
libboost_system.so.1.67.0 => /usr/lib/arm-linux-gnueabihf/libboost_system.so.1.67.0 (0xb6dc3000)
libboost_program_options.so.1.67.0 => /usr/lib/arm-linux-gnueabihf/libboost_program_options.so.1.67.0 (0xb6d42000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb6bfb000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6b79000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb6b4c000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb69fe000)
libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 (0xb69ce000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb69a4000)
/lib/ld-linux-armhf.so.3 (0xb6f2f000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb698d000)
libicudata.so.63 => /usr/lib/arm-linux-gnueabihf/libicudata.so.63 (0xb4f8f000)
libicui18n.so.63 => /usr/lib/arm-linux-gnueabihf/libicui18n.so.63 (0xb4d41000)
libicuuc.so.63 => /usr/lib/arm-linux-gnueabihf/libicuuc.so.63 (0xb4bbb000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb4ba8000)
Is a fully static build possible?
There was recently a PR merged. I think you still need to pass some libraries manually to the configure script. As mentioned in that PR (e.g. LIBS="-latomic").