"crosslinking " - different architecture libraries - is is possible?
-
Update I linked only part of the /lib folder , my mistake. Still like to know if my original question - linking to network resource is feasible. This is basically result of my inability to ".configure" for non - native architecture. The "configure" kept asking for dependency after dependency. So I ended up running .configure on required architecture. After a detour I am back to tying to implement / crosscompile C++ code. I can option a prefix for desired architecture , but still having an issue linking to specific desired architecture libraries. I was unable to use ".configure " to create correct foreign architecture library on "local" architecture. I did a hack by copying an entire "foreign" folder to local device and was partially successful linking to it. Still missing some library and could do same hack. Is there a more "elegant" way to accomplish that? Here is what is still failing to link correctly. Sorry for the mess.
gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)
COMPILER_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/bin/
LIBRARY_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/:/lib/../lib/:/usr/lib/../lib/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-L/media/z/KINGSTON/BULEZ_LIB_RPI' '-L/usr/arm-linux-gnueabihf/lib' '-L/media/z/DEV/BLUEZ/BLUEZ_LIB' '-v' '-o' 'VNAR_1971_JULY' '-shared-libgcc' '-march=armv7-a' '-mfloat-abi=hard' '-mfpu=vfpv3-d16' '-mthumb' '-mtls-dialect=gnu'
/usr/lib/gcc-cross/arm-linux-gnueabihf/5/collect2 -plugin /usr/lib/gcc-cross/arm-linux-gnueabihf/5/liblto_plugin.so -plugin-opt=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/lto-wrapper -plugin-opt=-fresolution=/tmp/ccUbRWT4.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu --as-needed -m armelf_linux_eabi -z relro -o VNAR_1971_JULY /usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/crt1.o /usr/lib/gcc-cross/arm-linux-g -
Update I linked only part of the /lib folder , my mistake. Still like to know if my original question - linking to network resource is feasible. This is basically result of my inability to ".configure" for non - native architecture. The "configure" kept asking for dependency after dependency. So I ended up running .configure on required architecture. After a detour I am back to tying to implement / crosscompile C++ code. I can option a prefix for desired architecture , but still having an issue linking to specific desired architecture libraries. I was unable to use ".configure " to create correct foreign architecture library on "local" architecture. I did a hack by copying an entire "foreign" folder to local device and was partially successful linking to it. Still missing some library and could do same hack. Is there a more "elegant" way to accomplish that? Here is what is still failing to link correctly. Sorry for the mess.
gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)
COMPILER_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/bin/
LIBRARY_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/:/lib/../lib/:/usr/lib/../lib/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-L/media/z/KINGSTON/BULEZ_LIB_RPI' '-L/usr/arm-linux-gnueabihf/lib' '-L/media/z/DEV/BLUEZ/BLUEZ_LIB' '-v' '-o' 'VNAR_1971_JULY' '-shared-libgcc' '-march=armv7-a' '-mfloat-abi=hard' '-mfpu=vfpv3-d16' '-mthumb' '-mtls-dialect=gnu'
/usr/lib/gcc-cross/arm-linux-gnueabihf/5/collect2 -plugin /usr/lib/gcc-cross/arm-linux-gnueabihf/5/liblto_plugin.so -plugin-opt=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/lto-wrapper -plugin-opt=-fresolution=/tmp/ccUbRWT4.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu --as-needed -m armelf_linux_eabi -z relro -o VNAR_1971_JULY /usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/crt1.o /usr/lib/gcc-cross/arm-linux-g -
Update I linked only part of the /lib folder , my mistake. Still like to know if my original question - linking to network resource is feasible. This is basically result of my inability to ".configure" for non - native architecture. The "configure" kept asking for dependency after dependency. So I ended up running .configure on required architecture. After a detour I am back to tying to implement / crosscompile C++ code. I can option a prefix for desired architecture , but still having an issue linking to specific desired architecture libraries. I was unable to use ".configure " to create correct foreign architecture library on "local" architecture. I did a hack by copying an entire "foreign" folder to local device and was partially successful linking to it. Still missing some library and could do same hack. Is there a more "elegant" way to accomplish that? Here is what is still failing to link correctly. Sorry for the mess.
gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)
COMPILER_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/bin/
LIBRARY_PATH=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/:/lib/../lib/:/usr/lib/../lib/:/usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-L/media/z/KINGSTON/BULEZ_LIB_RPI' '-L/usr/arm-linux-gnueabihf/lib' '-L/media/z/DEV/BLUEZ/BLUEZ_LIB' '-v' '-o' 'VNAR_1971_JULY' '-shared-libgcc' '-march=armv7-a' '-mfloat-abi=hard' '-mfpu=vfpv3-d16' '-mthumb' '-mtls-dialect=gnu'
/usr/lib/gcc-cross/arm-linux-gnueabihf/5/collect2 -plugin /usr/lib/gcc-cross/arm-linux-gnueabihf/5/liblto_plugin.so -plugin-opt=/usr/lib/gcc-cross/arm-linux-gnueabihf/5/lto-wrapper -plugin-opt=-fresolution=/tmp/ccUbRWT4.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -dynamic-linker /lib/ld-linux-armhf.so.3 -X --hash-style=gnu --as-needed -m armelf_linux_eabi -z relro -o VNAR_1971_JULY /usr/lib/gcc-cross/arm-linux-gnueabihf/5/../../../../arm-linux-gnueabihf/lib/../lib/crt1.o /usr/lib/gcc-cross/arm-linux-gDo your standard apt-get update and install on libc somethings missing.
In vino veritas