[yocto] [meta-gplv2][PATCH] gmp_4.2.1: prevent calls to mpn_add_nc() if HAVE_NATIVE_mpn_sub_nc is false

When building for aarch64 (ie relying only on generic C code rather than asm) libgmp.so contains undefined references to __gmpn_add_nc and __gmpn_sub_nc which causes attempts to link with -lgmp to fail: | .../usr/lib/libgmp.so: undefined reference to `__gmpn_sub_nc' | .../usr/lib/libgmp.so: unde

Re: [yocto] Problems building U-Boot for x86_64

Op Fri, 25 Aug 2017 21:22:40 +0200, schreef Ferry Toth: > Khem Raj wrote: > > >> >> >> On 8/23/17 3:40 PM, Ferry Toth wrote: >>> Op Wed, 23 Aug 2017 14:51:55 -0700, schreef Khem Raj: >>> On 8/23/17 2:29 PM, Ferry Toth wrote: > Ferry Toth wrote: > >> Khem Raj wrote: >> >>>

Re: [yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

okay. I will try. 2017-08-25 17:51 GMT+09:00 Paul Barker : > On Thu, Aug 24, 2017 at 1:05 PM, Yusuke Mitsuki > wrote: > > hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not > found. > > > > Paches that in order to use bluetooth with BCM43430 are not enabled. > > Functions are on

[yocto] [layerindex-web][PATCH v2] docker : update dockerfile to start celery worker

Related to bug 11197 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11197) this WIP patch updates the Dockerfile to start a Celery worker alongside the Gunicorn daemon. These changes allow the Docker image to leverage the asynchronous task execution framework established in a prior patch. I do

Re: [yocto] Problems building U-Boot for x86_64

Khem Raj wrote: > > > > On 8/23/17 3:40 PM, Ferry Toth wrote: >> Op Wed, 23 Aug 2017 14:51:55 -0700, schreef Khem Raj: >> >>> On 8/23/17 2:29 PM, Ferry Toth wrote: Ferry Toth wrote: > Khem Raj wrote: > >> On 8/22/17 11:41 PM, Ferry Toth wrote: >>> I am having trouble

[yocto] [layerindex-web][PATCH] docker : update dockerfile to start celery worker

Related to bug 11195 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11195) this WIP patch updates the Dockerfile to start a Celery worker alongside the Gunicorn daemon. These changes allow the Docker image to leverage the asynchronous task execution framework established in a prior patch. I do

Re: [yocto] raspberrypi3-64 target not booting

On Fri, Aug 25, 2017 at 10:14 AM, Bill Jenkins wrote: > > On Aug 25, 2017, at 9:42 AM, Khem Raj wrote: > > > On Fri, Aug 25, 2017 at 9:39 AM Bill Jenkins wrote: >> >> I am trying to just get the simple 64-bit rpi-basic-image to work, but the >> Raspberry Pi 3 seems to hang with the rainbow scree

Re: [yocto] raspberrypi3-64 target not booting

On Fri, Aug 25, 2017 at 9:39 AM Bill Jenkins wrote: > I am trying to just get the simple 64-bit rpi-basic-image to work, but the > Raspberry Pi 3 seems to hang with the rainbow screen at startup. > Can you plugin a serial cable and see if that worked or try to add ssh daemon on target and try to

[yocto] raspberrypi3-64 target not booting

I am trying to just get the simple 64-bit rpi-basic-image to work, but the Raspberry Pi 3 seems to hang with the rainbow screen at startup. If I build with MACHINE ?= raspberrypi3, the 32-bit image works just fine. Is there something special that needs to be set in order for the "MACHINE ?= raspb

Re: [yocto] Pyro's uninative and libstdc++ symbols

Hi, You could try to build your own uninative: bitbake uninative-tarball and use your own uninative: update: poky/meta/conf/distro/include/yocto-uninative.inc Or stop using uninative. But I'm also curios why native built with newer gcc is not using glibc from uninative (older glibc than gcc 7

Re: [yocto] [meta-qt4][PATCH RESEND][pyro] qt4-native: depend on icu-native to fix build on systems with icu <=58

On 08/25/2017 04:17 PM, Ioan-Adrian Ratiu wrote: From: Cody P Schafer Previously, qt4-native would use the system icu to build. Trying to build against a system ICU 59, however, fails with this root error: | In file included from /usr/include/unicode/uversion.h:30:0, | from t

[yocto] [meta-qt4][PATCH RESEND][pyro] qt4-native: depend on icu-native to fix build on systems with icu <=58

From: Cody P Schafer Previously, qt4-native would use the system icu to build. Trying to build against a system ICU 59, however, fails with this root error: | In file included from /usr/include/unicode/uversion.h:30:0, | from tools/qlocale_icu.cpp:46: | /usr/include/unicode/uma

[yocto] Pyro's uninative and libstdc++ symbols

I've recently updated my host system to Fedora 26, which has GCC 7. This seems to be causing some issues on Pyro, where I have a -native recipe that is built with my system's g++ and ends up generating a binary with the following symbol: DF *UND* GLIBC

[yocto] ERROR: Unable to connect to bitbake server, or start one

I figured out that the new function findTopdir (Submitted on July 18, 2017) does not handle the errors of the absence of the BBPATH variable and path to the conf/bblayers.conf in BBATH. It just returns None. On Thu, 2017-08-24 at 18:24 +0300, Gera Pesikoff wrote: > Hi > I started to study bitb

Re: [yocto] [meta-raspberrypi][PATCH] bluez5: add functions for raspberrypi0-wifi

On Thu, Aug 24, 2017 at 1:05 PM, Yusuke Mitsuki wrote: > hciattach on raspberrypi0-wifi failed because BCM43430A1.hcd is not found. > > Paches that in order to use bluetooth with BCM43430 are not enabled. > Functions are only enabled with raspberrypi3 in bluez5_%.bbappend like as > follows: > > -

Re: [yocto] Problems building U-Boot for x86_64

Op Thu, 24 Aug 2017 21:34:56 +, schreef Ferry Toth: > Op Thu, 24 Aug 2017 16:35:05 +, schreef Ferry Toth: > >> Op Thu, 24 Aug 2017 17:48:55 +0200, schreef Stefano Babic: >> >>> Hi Ferry, >>> >>> On 24/08/2017 15:09, Ferry Toth wrote: Op Thu, 24 Aug 2017 12:40:57 +0200, schreef Stef

Re: [yocto] Yocto plug-in not running cmake

My _guess_ is that Cmake is not installed on the host? or you do not have the SDK populated? Please look at https://wiki.yoctoproject.org/wiki/TipsAndTricks/Cmake,Eclipse,_and_SDKS and let us know if that helps. > On Aug 24, 2017, at 4:46 PM, Paul D. DeRocco wrote: > > Yocto 2.2.1, standard S