Franz Hollerer created PROTON-2185:
--------------------------------------

             Summary: Cross compilation fails during linking codec_test
                 Key: PROTON-2185
                 URL: https://issues.apache.org/jira/browse/PROTON-2185
             Project: Qpid Proton
          Issue Type: Bug
            Reporter: Franz Hollerer


Target: NXP i.MX7D application processor

Build environment_ Yocto, arm-poky-linux-gnueabi-g++ v5.2.0

I tried to cross compile qpid-proton v0.30.0 and also the actual master branch. 
Unfortunately it fails during linking codec_test:
{quote}Scanning dependencies of target codec_test
[ 69%] Building CXX object cpp/CMakeFiles/codec_test.dir/src/codec_test.cpp.o
[ 69%] Linking CXX executable codec_test
/opt/b8mcu_sdk/0.0.1/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.2.0/real-ld:
 warning: libqpid-proton-proactor.so.1, needed by libqpid-proton-cpp.so.12.6.1, 
not found (try using -rpath or -rpath-link)
/opt/b8mcu_sdk/0.0.1/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.2.0/real-ld:
 warning: libqpid-proton-core.so.10, needed by libqpid-proton-cpp.so.12.6.1, 
not found (try using -rpath or -rpath-link)
libqpid-proton-cpp.so.12.6.1: undefined reference to `pn_data_put_described'
libqpid-proton-cpp.so.12.6.1: undefined reference to `pn_dtag'
libqpid-proton-cpp.so.12.6.1: undefined reference to `pn_message_set_reply_to'
{quote}
For details please see:
 * 
[http://qpid.2158936.n2.nabble.com/Cross-Compiling-qpid-proton-0-30-0-with-Yocto-SDK-tt7689081.html#a7689085]
 * [https://github.com/apache/qpid-proton/pull/187]

I also tried to build qpid-proton with BUILD_TESTING, FUZZ_LONG_TESTS and 
FUZZ_REGRESSION__TEST set to "NO". Therefore, I wonder why it tries to build 
codec_test at all.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to