On 12/30/17 5:11 PM, cc_Smart wrote:
Greetings all.

Beating my own expectations it seems i got past the compile step for pylonGPS.

However, now i get an error that seems to indicate linking to reach for host files instead of cross compiled. My understanding was that bitbake handles that... what do i have to look for ?

Thanks for your support...


see -L/usr/lib/x86_64-linux-gnu in you commandline there, thats a problem you need to look into. Its possible that pylongps's own build system hardcodes it into linker flags, which is a problem for cross compiling.


| [ 90%] Linking CXX shared library lib/libpylongps.so
| /workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_link_script CMakeFiles/pylongps.dir/link.txt --verbose=1 | /workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ -fPIC  -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0=/usr/src/debug/pylongps/0.1.0-r0 -fdebug-prefix-map=/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot-native= -fdebug-prefix-map=/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot= -fvisibility-inlines-hidden  -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -shared -Wl,-soname,libpylongps.so -o lib/libpylongps.so CMakeFiles/pylongps.dir/src/library/NMEAGGASentence.cpp.o CMakeFiles/pylongps.dir/src/library/SOMException.cpp.o CMakeFiles/pylongps.dir/src/library/SOMScopeGuard.cpp.o CMakeFiles/pylongps.dir/src/library/caster.cpp.o CMakeFiles/pylongps.dir/src/library/casterDataSender.cpp.o CMakeFiles/pylongps.dir/src/library/commandLineArgumentParser.cpp.o CMakeFiles/pylongps.dir/src/library/connectionStatus.cpp.o CMakeFiles/pylongps.dir/src/library/event.cpp.o CMakeFiles/pylongps.dir/src/library/fileDataReceiver.cpp.o CMakeFiles/pylongps.dir/src/library/fileDataSender.cpp.o CMakeFiles/pylongps.dir/src/library/messageDatabaseDefinition.cpp.o CMakeFiles/pylongps.dir/src/library/randomStringGenerator.cpp.o CMakeFiles/pylongps.dir/src/library/subMessageDatabaseDefinition.cpp.o CMakeFiles/pylongps.dir/src/library/tcpDataReceiver.cpp.o CMakeFiles/pylongps.dir/src/library/tcpDataSender.cpp.o CMakeFiles/pylongps.dir/src/library/tranceiver.cpp.o CMakeFiles/pylongps.dir/src/library/utilityFunctions.cpp.o CMakeFiles/pylongps.dir/src/library/zmqDataReceiver.cpp.o CMakeFiles/pylongps.dir/src/library/zmqDataSender.cpp.o CMakeFiles/pylongps.dir/jsoncpp/jsoncpp.cpp.o -L/usr/lib/x86_64-linux-gnu -L/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/git/lib -L/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/git/./messages -Wl,-rpath,/usr/lib/x86_64-linux-gnu:/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/git/lib:/workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/git/./messages -ldl -lPocoFoundation -lPocoNet -lPocoUtil -lsqlite3 lib/libpylonGPSMessages.a -lzmq -lprotobuf -lpthread -lsodium | /workdir/dev/rpi3/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/pylongps/0.1.0-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/7.2.0/ld: warning: library search path "/usr/lib/x86_64-linux-gnu" is unsafe for cross-compilation | /usr/lib/x86_64-linux-gnu/libdl.so: file not recognized: File format not recognized
| collect2: error: ld returned 1 exit status

--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to