[yocto] Yocto and Google protobuffer

em in the image being generated ? A good example for that would be the protoc, the protocol buffer description file compiler. Thanks in advance, Pietro. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: >> Hi all, >> >> I am new to the Yocto building system and I could be talking nonsense. I >> used to work with buildroot time ago and I remember there is an area >> where compiled softwar

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote: >> Maciej Borzęcki >> writes: >> >>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: >>>> Hi all, >>>> >>>> I am new to the Yocto building system and I

Re: [yocto] Yocto and Google protobuffer

Jussi Kukkonen writes: > On 1 September 2016 at 13:21, Herman van Hazendonk > wrote: > > Hi Pietro, > > You can override the recipe by adding a recipe for version 3.0.0+ > in your own layer and making sure your layer has a higher priority > in bblaye

Re: [yocto] Yocto and Google protobuffer

Pietro writes: > Jussi Kukkonen > writes: > >> On 1 September 2016 at 13:21, Herman van Hazendonk >> wrote: >> >> Hi Pietro, >> >> You can override the recipe by adding a recipe for version 3.0.0+ >> in your own layer and mak

Re: [yocto] Yocto and Google protobuffer

Herman van Hazendonk writes: > Hi Pietro, > > You shouldn't need to specify a version. DEPENDS = "protobuf" or > DEPENDS = "protobuf-native" should do :) > > Herrie > > > Indeed my recipe gets built first and I can see do_protobuf_3.0.0[

Re: [yocto] Yocto and Google protobuffer

Herman van Hazendonk writes: > If it takes the wrong version, it could be your layers aren't in the > right order. That's the first thing to check. > > You might want to try to run bitbake with > > -f protobuf -c cleanall or -f protobuf-native -c cleanall > > This will remove all locally ;) > > T

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >> Herman van Hazendonk >> writes: >> >>> If it takes the wrong version, it could be your layers aren't in the >>> right order. That's the first thing to check. >>>

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >> Herman van Hazendonk >> writes: >> >>> If it takes the wrong version, it could be your layers aren't in the >>> right order. That's the first thing to check. >>>

[yocto] arm-*-linux-gnueabi : unrecognized option -Wl, -soname

Hi all, I want to cross compile the gRPC library for ARM and I am using the Yocto build system. The build fails for the following error, which I am suspicious has something to do with the compiler being used: [LD] Linking /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-p

Re: [yocto] arm-*-linux-gnueabi : unrecognized option -Wl, -soname

be a question for gRPC developers though "Daniel." writes: > I *guess* that it should be -Wl,-soname=libgpr.so.1 intead of > -Wl,-soname,libgpr.so.1. Now from where this flags are comming is a > good question.. > > 2016-09-05 9:17 GMT-03:00 Pietro : >> >> Hi a

Re: [yocto] arm-*-linux-gnueabi : unrecognized option -Wl, -soname

without using bitbake - from the build directory, the build log tells : + bbnote make -j 4 CC=arm-phytec-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 --sysroot=/export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/phycore-am335x-1 LDFL

Re: [yocto] arm-*-linux-gnueabi : unrecognized option -Wl, -soname

Maciej Borzęcki writes: > On Tue, Sep 6, 2016 at 12:05 PM, Pietro wrote: >> >> >> >> "Daniel." writes: >> >>> I *guess* that it should be -Wl,-soname=libgpr.so.1 intead of >>> -Wl,-soname,libgpr.so.1. Now from where this flags are

[yocto] [meta-java] openjdk-7-jre was skipped: missing required distro feature ['x11'] (not in DISTRO_FEATURES)

Hi Folks, I'm trying to compile java without x11 and unfortunately also without success.. I've added in my local.conf: DISTRO_FEATURES_remove = "x11" # Java build settings PREFERRED_PROVIDER_virtual/java-native = "jamvm-native" PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native" PREF

[yocto] [meta-java] can zero shark be enabled again?

Hi again, I saw that some JIT optimization for arm32 has been announcement in icedtea the announcement is available at http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-January/030392.html So I'm just wondering if anyone know if shark can be enabled again also in yocto recipes and can s

Re: [yocto] [meta-java] openjdk-7-jre was skipped: missing required distro feature ['x11'] (not in DISTRO_FEATURES)

2015-10-16 16:09 GMT+01:00, Jens Rehsack : > >> Am 16.10.2015 um 15:35 schrieb Federico Pietro Briata >> : >> >> Hi Folks, >> I'm trying to compile java without x11 and unfortunately also without >> success.. >> >> I've added in my loc

Re: [yocto] [meta-java] can zero shark be enabled again?

2015-10-16 16:14 GMT+01:00, Jens Rehsack : > > I fear you mix between ARMJIT provided by IceadTea and ZeroShark provided by > OpenJDK. Ops > While IcedTea maintains the ARMJIT within hotspot ported from OpenJDK6, > ZeroShark uses LLVM's JIT. I thought ARMJIT was part of Shark and provided with h

Re: [yocto] [meta-java] can zero shark be enabled again?

2015-10-16 17:14 GMT+02:00 Jens Rehsack : > > While IcedTea maintains the ARMJIT within hotspot ported from OpenJDK6, > ZeroShark uses LLVM's JIT. > > Since ARM support in LLVM's JIT was utterly broken, MCJIT support is > required for ZeroShark. > I was working on that but my ARMv7 and my ARMv5 ar

Re: [yocto] [meta-java] [PATCH] gnumail: Fix race condition in makefile fail to apply

Hi Maxin, thanks a lot, after a pull it's working but now I got a different issue.. :/ I'll send a separate email about the current trouble.. Thanks again Federico 2015-12-11 14:23 GMT+01:00 Maxin B. John : > Hi Federico, > > On Fri, Dec 11, 2015 at 12:45:18PM +0100, Fed

[yocto] [meta-java] openjdk-8 fail to build

Hi All, I'm trying to build openjdk-8 but I'm stuck. my current setup does not define anything for: #PREFERRED_PROVIDER_virtual/java-native #PREFERRED_PROVIDER_virtual/javac-native follow the log error ERROR: Function failed: do_configure (log file is located at /home/federico/yocto/imx6/R6.0/b

Re: [yocto] [meta-java] openjdk-8 fail to build

Hi Jens 2015-12-13 10:03 GMT+01:00 Jens Rehsack : > > > Am 11.12.2015 um 18:16 schrieb Federico Pietro Briata < > federicobri...@gmail.com>: > > > | ERROR: no configure script found at > /home/federico/yocto/imx6/R6.0/build-imx6-mx6quad/tmp/work/x86_64-linux/o

Re: [yocto] [meta-java] openjdk-8 fail to build

ile Summary: There was 1 ERROR message shown, returning a non-zero exit code. thanks and regards federico 2015-12-19 10:38 GMT+01:00 Stef : > Federico Pietro Briata writes: > > > > > > > > > Hi All, > > I'm trying to build openjdk-8 but I'm stuck

Re: [yocto] [meta-java] openjdk-8 fail to build

-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile so the build stuck here in this loop I think. regards Federico 2016-01-12 17:41 GMT+01:00 Federico Pietro Briata : > Hi Stef, > Thanks, I've tried to apply that patch and al

Re: [yocto] [meta-java] openjdk-8 fail to build

Hi, What version of Yocto are you using? I'm using 1.7.1 version with only the patch i described in my previous answer. When using it on the master of meta-java i got it working without any issues.. You mentioned you use another patch as well? Regards 2016-01-13 18:46 GMT+01:00 Federico Pietro

[yocto] [meta-virtualization] [recipes-containers] criu version 2.12.1

Hi All, in attach my recipes for Criu 2.12.1. Best regards, Federico Briata --- recipes-containers/criu/criu-2.12.1+gitAUTOINC+14e0bf7baf/0002-criu-Skip-documentation-install.patch | 28 +++ recipes-containers/criu/criu-2.12.1+gitAUTOINC+14e0bf7baf/0001-criu-Fix-toolchain-hard