[yocto] uninative vs. BB_NO_NETWORK

Currently using Yocto 1.8, planning upgrade to 2.2 Per the Reference Manual, "The uninative class is now enabled by default in Poky. [...] With this class enabled, a tarball containing a pre-built C library is downloaded at the start of the build." We have to build with BB_NO_NETWORK = "1" How

Re: [yocto] undefined references to `__dso_handle'

Hi, Did you have multilib installed!? Regards, 2016-11-17 15:27 GMT-02:00 Elazar Leibovich : > As far as I know, no customization, I didn't even switch GCC's version. I > installed clang alongside gcc, but didn't change the default. > > Can you refer me to what you have in mind that might be c

Re: [yocto] uninative vs. BB_NO_NETWORK

On 18 November 2016 at 14:58, Vuille, Martin (Martin) wrote: > Currently using Yocto 1.8, planning upgrade to 2.2 > > Per the Reference Manual, "The uninative class is now enabled by default > in Poky. [...] > With this class enabled, a tarball containing a pre-built C library is > downloaded at

Re: [yocto] raspberry pi gtkmm_3.0.bb

x27;: >> > | >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi >> /libstdc++-v3/src/c++11/../../../../../../../../../../work- >> shared/gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++11/ &

Re: [yocto] raspberry pi gtkmm_3.0.bb

gt; | ../src/c++98/.libs/libc++98convenience.a(mt_allocator.o): In > function > >> > `get_freelist': > >> > | > >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky > >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi > &

[yocto] Yocto Project Status WW47

Current Dev Position: YP 2.3 M1 Next Deadline: YP 2.3 M1 by Dec. 12, 2016 SWAT team rotation: Leo -> Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *2.1.2 QA report is out and likely to be released imminently. *The QA report for 2.1

Re: [yocto] Yocto Project Status WW47

Stephen On 11/18/2016 08:35 AM, Jolley, Stephen K wrote: Current Dev Position: YP 2.3 M1 Next Deadline: YP 2.3 M1 by Dec. 12, 2016 SWAT team rotation: Leo -> Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: Thanks for the updates. ·2.1.2 QA rep

[yocto] devshell, KDE konsole & python3 TypeError

Hi, I'm on Morty and I hit the following bugs when trying to launch a devshell… I did a quick search and don't think they are solved. In poky/meta/lib/oe/terminal.py, the option "--nofork" doesn't exist in my konsole v16.08. I replaced it by option "--new-tab", which solved the problem. And

Re: [yocto] populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy

Paul, > From: "Paul Eggleton" > Sent: Friday, 18 November, 2016 2:46:07 AM > I think the issue is this hasn't really been tested with deb > packaging. You > have hit a genuine bug though - would you mind filing a bug at > http://bugzilla.yoctoproject.org? Thanks for your help. I'll file a bug

[yocto] [raspberrypi] raspi3 vs raspi2

Hi, I was wondering if there were any plans to create a MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it is instead of generating images that are backwards compatible with the CortexA7 that is the raspi2? Best regards, Trevor -- _

[yocto] uninative workflow

Hi, To be honest, I'm not entirely sure what the uninative stuff is (explanations or pointers to explanations appreciated!) but I'm trying to figure out how to work with it. Previously, generating an eSDK didn't require a uninative-tarball, but now, apparently, it does? Any idea why? So now, in