W dniu 2016-12-20 o 10:46, Mateusz Orzoł pisze: > > > > W dniu 2016-12-20 o 00:43, Khem Raj pisze: >> >> >> On Mon, Dec 19, 2016 at 1:46 PM, Mateusz Orzoł >> <mateusz.or...@3cityelectronics.com >> <mailto:mateusz.or...@3cityelectronics.com>> wrote: >> >> Hi everyone, >> >> I am migrating my old Yocto image from kernel 3.8 to 4.1 on the >> Intel Quark based platform. After dealing with some SPI driver >> issues now I've encountered some strange bitbake behaviour. My >> web application requires UltraJson , LMDB and Netifaces modules. >> After running bitbake I am getting a lot of undefined reference >> errors. In all three cases pretty similar. Exemplary log for >> python-ujson is here: http://pastebin.com/8ms9PgnY . It seems >> like the python environment wasn't linked properly but many other >> python recipes have no problem with compiling. >> >> The python-ujson recipe comes from here >> https://layers.openembedded.org/layerindex/recipe/49510/ >> <https://layers.openembedded.org/layerindex/recipe/49510/>. In >> previous distribution with kernel 3.8 it was working without any >> problem. >> >> Have you got any idea what could be wrong or what should I check >> first? >> >> >> The error seems to have nothing to do with kernel version. Are you >> upgrading the whole of yocto framework from one release to another ? >> and if yes from which version to which new version. >> >> > I am upgrading from 1.4.2 Dylan version to Krogoth. Firstly I've > prepared clean Krogoth image which worked fine. Now I am adding > necessary recipes and packages one by one and currently the only > problem I've encountered is the mentioned one. Hi, W have found found quick fix for this. The errors disappeared when all the build flags were cleared in mentioned python modules recipes. It means TARGET_CFLAGS = "" LDFLAGS = "" CFLAGS = "" in module .bb file. It was checked on the device that modules are visible in python and they work. I don't know why this helped and also what was causing the issue. Do you have any clues what was wrong and how to fix it in proper way? >> >> Thank you for your help in advance, >> >> Mateusz >> >> >> -- >> >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> >> https://lists.yoctoproject.org/listinfo/yocto >> <https://lists.yoctoproject.org/listinfo/yocto> >> >> > > -- >
--
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
