**** BEGIN LOGGING AT Wed Oct 03 03:00:01 2018 Oct 03 08:08:27 Hello All Oct 03 08:08:55 LetoThe2nd, I got an error while running "bitbake core-image-minimal -c populate_sdk" Oct 03 08:09:47 https://pastebin.com/azZV10pb Oct 03 09:06:45 Hi, I'm getting some failures while executing Poco package unittests/testsuite on imx board. Oct 03 09:06:55 those failed testcases are testLaunch, testLaunchRedirectIn, testLaunchRedirectOut, testLaunchEnv Oct 03 09:07:39 I raised bug on github also but found that somebody had same issue 2 years back and still no response. Oct 03 09:07:58 I raise a query on stack-overflow but no response there also. Oct 03 09:08:01 Need some help to investigate those failures. Oct 03 13:32:46 khem, this build is w/out security flags. Linker is always bfd for klibc Oct 03 13:33:43 ( a52f2cb2e93e klibc: Fix linking by using bfd linker when default linker is gold ) Oct 03 13:34:09 the build with security flags was already tested. I'll redo Oct 03 15:30:27 ant_home: you need to build with sec flags to see the problem I am seeing Oct 03 15:30:40 I think we need to pass -fno-PIE to cflags/ldflags Oct 03 19:22:48 riddle me this, I am trying to create a recipe to build sip with python3, the recipe ahs: Oct 03 19:22:57 [balister@prague build]$ bitbake -e sip3 | grep ^DEPENDS Oct 03 19:22:57 DEPENDS="virtual/x86_64-oe-linux-gcc virtual/x86_64-oe-linux-compilerlibs virtual/libc python3 python3-native " Oct 03 19:23:00 but Oct 03 19:23:36 [balister@prague build]$ find ./tmp-glibc/work/core2-64-oe-linux/sip/4.19.13-r0/ -name Python.h Oct 03 19:23:37 ./tmp-glibc/work/core2-64-oe-linux/sip/4.19.13-r0/recipe-sysroot-native/usr/include/python2.7/Python.h Oct 03 19:23:37 ./tmp-glibc/work/core2-64-oe-linux/sip/4.19.13-r0/recipe-sysroot-native/usr/include/python3.5m/Python.h Oct 03 19:23:37 ./tmp-glibc/work/core2-64-oe-linux/sip/4.19.13-r0/recipe-sysroot/usr/include/python2.7/Python.h Oct 03 19:23:52 is in the sysroot directories Oct 03 19:24:07 WHy do I get python2? Why isn;t python three in the sysroot? Oct 03 19:25:58 because sip != sip3? Oct 03 19:26:39 lol Oct 03 19:26:44 I am blind Oct 03 19:26:59 or drunk @prague :) Oct 03 19:27:06 * JaMa approves! Oct 03 19:27:16 [balister@prague build]$ find ./tmp-glibc/work/core2-64-oe-linux/sip3/4.19.13-r0/ -name Python.h Oct 03 19:27:16 ./tmp-glibc/work/core2-64-oe-linux/sip3/4.19.13-r0/recipe-sysroot-native/usr/include/python3.5m/Python.h Oct 03 19:27:16 ./tmp-glibc/work/core2-64-oe-linux/sip3/4.19.13-r0/recipe-sysroot/usr/include/python3.5m/Python.h Oct 03 19:27:32 haha bought the machine around that time, so named after city of ELCE Oct 03 19:27:36 and I liek the name Oct 03 19:28:51 ok, o not the m in usr inclue Python. h path, yet compileing with Oct 03 19:29:01 -I/home/balister/opensdr/sdr-build-master-qemu/build/tmp-glibc/work/core2-64-oe-linux/sip3/4.19.13-r0/recipe-sysroot//usr/include/python3.5 Oct 03 19:29:12 where is the m coming from? Oct 03 19:42:45 prague.. I barely remember Prague Oct 03 19:42:55 I love Prague Oct 03 19:43:30 Especially the cart racing Oct 03 19:57:28 no clues why I ahve a funny path for my sysroot? Oct 03 20:09:59 Crofton, some of us had to work :/ Oct 03 20:48:10 so this PYTHON_ABI in the path is screwing something up, I think Oct 03 20:48:41 [balister@prague build]$ bitbake -e sip3 | grep ^PYTHON_ Oct 03 20:48:41 PYTHON_ABI="m" Oct 03 20:48:41 PYTHON_BASEVERSION="3.5" Oct 03 20:48:41 PYTHON_DIR="python3.5" Oct 03 20:48:41 PYTHON_PN="python3" Oct 03 20:48:42 PYTHON_SITEPACKAGES_DIR="/usr/lib/python3.5/site-packages" Oct 03 20:49:22 but site-packages includes the m Oct 03 20:49:29 /usr/lib/python3.5m/site-packages/PyQt5_sip-4.19.13.dist-info Oct 03 23:14:48 * armpit work makes my brain hurt **** ENDING LOGGING AT Thu Oct 04 03:00:02 2018