11104 2017-02-24 09:46:41 +0000 boost libboost_python3.so.1.62.1 links incorrectly against Python 2 C API 2017-03-30 13:00:23 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium+ normal 2.3 M4 1 ismo.puustinen ross.burton lukas.bulwahn meta.mr.watcher meta.watcher --- --- Don't know oldest_to_newest 70927 0 ismo.puustinen 2017-02-24 09:46:41 +0000 Using libboost_python3 from any project fails with an "undefined reference" linking problem, because libboost_python3.so.1.62.0 appears to be built incorrectly against Python 2 includes and uses symbols which are not present in Python 3 C library. libboost_python.so (Python 2) uses PyClass_Type, which is fine: nm -D tmp-glibc/work/corei7-64-refkit-linux/boost/1.62.0-r1/sysroot-destdir/usr/lib/libboost_python.so.1.62.0 | grep PyClass_Type U PyClass_Type However, libboost_python3.so also uses the same symbol, which is not fine: nm -D tmp-glibc/work/corei7-64-refkit-linux/boost/1.62.0-r1/sysroot-destdir/usr/lib/libboost_python3.so.1.62.0 | grep PyClass_Type U PyClass_Type Looking at the Python C libraries we can see that the symbol is prsent only in Python 2: nm -D tmp-glibc/work/corei7-64-refkit-linux/boost/1.62.0-r1/recipe-sysroot/usr/lib/libpython3.5m.so | grep PyClass_Type nm -D tmp-glibc/work/corei7-64-refkit-linux/boost/1.62.0-r1/recipe-sysroot/usr/lib/libpython2.7.so | grep PyClass_Type 000000000038e420 D PyClass_Type There's some discussion about the issue here: http://stackoverflow.com/questions/25188861/libboost-python3-so-1-56-0-undefined-symbol-pyclass-type 71704 1 ross.burton 2017-03-24 16:08:26 +0000 I'm sending a patch to port boost from py2 to py3, so if Python is enabled in boost it only builds against Py3. 71707 2 ross.burton 2017-03-24 16:15:46 +0000 *** Bug 11152 has been marked as a duplicate of this bug. *** 71902 3 ross.burton 2017-03-30 13:00:23 +0000 Fixed in oe-core 0f5418eb0ce12811b16d2e3c28c28140a509f685.