[yocto] Basehash value changed issue

[techi eth]

Hi,

I am facing issue with basehash value changed while building image on one
of my test board (Ref of beagle bone) on morty branch.

Error :
gateway.bb.do_rootfs, the basehash value changed from
e685a429b8df6dcff60063f087d425ee to 3f98a102f48ea8722835ad0d65bfbc1f. The
metadata is not deterministic and this needs to be fixed

When i run bitbake-diffsigs -t gateway do_rootfs
I found below O/P.
basehash changed from 8e6b9498c9704590bd016491efcbf9f9 to
3f98a102f48ea8722835ad0d65bfbc1f
Variable TIME value changed from '112854' to '115745'

After googling I found that TIME need's to be added in vardepsexclude list.
I added below in conf/distro/machine.conf but error persist.
do_rootfs[vardepsexclude] = "TIME DATE DATETIME"

Please suggest me where & what has to be added to come out of issue.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-cloud-services] spice: remove spice receipe from meta-cloud-services

[Bruce Ashfield]

On 06/21/2018 02:11 AM, Changqing Li wrote:

spice have been export to meta-openembedded/meta-networking,
and have newer version. spice under this layer now have
compile error, but spice under networking layer don't.
Maybe we should not maintain 2 same spices, so delete it.


I'm going to hold onto this one a bit longer. We have specific
version requirements and will revisit when the next openstack
uprev is done.

Cheers,

Bruce



Signed-off-by: Changqing Li 
---
  ...ros-in-printf-to-keep-compatibility-betwe.patch |  72 ---
  ...xl-Fix-BITMAP_FMT_IS_RGB-defined-but-not-.patch |  29 --
  recipes-support/spice/files/CVE-2017-7506-1.patch  |  81 -
  recipes-support/spice/files/CVE-2017-7506-2.patch  |  37 
  recipes-support/spice/files/CVE-2017-7506-3.patch  |  54 ---
  .../spice/files/Fix-build-issues-with-gcc-7.patch  |  59 
  .../build-allow-separated-src-and-build-dirs.patch |  62 -
  ...ac-add-subdir-objects-to-AM_INIT_AUTOMAKE.patch |  29 --
  .../spice/files/spice-fix-CVE-2013-4282.patch  | 100 -
  recipes-support/spice/spice_git.bb |  79 
  10 files changed, 602 deletions(-)
  delete mode 100644 
recipes-support/spice/files/0001-Use-PRI-macros-in-printf-to-keep-compatibility-betwe.patch
  delete mode 100644 
recipes-support/spice/files/0001-red_parse_qxl-Fix-BITMAP_FMT_IS_RGB-defined-but-not-.patch
  delete mode 100644 recipes-support/spice/files/CVE-2017-7506-1.patch
  delete mode 100644 recipes-support/spice/files/CVE-2017-7506-2.patch
  delete mode 100644 recipes-support/spice/files/CVE-2017-7506-3.patch
  delete mode 100644 
recipes-support/spice/files/Fix-build-issues-with-gcc-7.patch
  delete mode 100644 
recipes-support/spice/files/build-allow-separated-src-and-build-dirs.patch
  delete mode 100644 
recipes-support/spice/files/configure.ac-add-subdir-objects-to-AM_INIT_AUTOMAKE.patch
  delete mode 100644 recipes-support/spice/files/spice-fix-CVE-2013-4282.patch
  delete mode 100644 recipes-support/spice/spice_git.bb

diff --git 
a/recipes-support/spice/files/0001-Use-PRI-macros-in-printf-to-keep-compatibility-betwe.patch
 
b/recipes-support/spice/files/0001-Use-PRI-macros-in-printf-to-keep-compatibility-betwe.patch
deleted file mode 100644
index 18fa8fa..000
--- 
a/recipes-support/spice/files/0001-Use-PRI-macros-in-printf-to-keep-compatibility-betwe.patch
+++ /dev/null
@@ -1,72 +0,0 @@
-From 3cb746329ea4846bd9c65e0198e69423379b6f62 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?=EC=86=8C=EB=B3=91=EC=B2=A0?= 
-Date: Thu, 24 Apr 2014 12:26:32 +
-Subject: [PATCH] Use PRI macros in printf to keep compatibility between
- 32/64bit system
-
-gcc's some integer type definitions are different between 32/64bit system.
-This causes platform dependency problem with printf function. However,
-we can avoid this problem by using PRI macros that supports platform
-independent printf.

- server/mjpeg_encoder.c | 7 ---
- server/red_worker.c| 4 ++--
- 2 files changed, 6 insertions(+), 5 deletions(-)
-
-diff --git a/server/mjpeg_encoder.c b/server/mjpeg_encoder.c
-index aea4964..f465d88 100644
 a/server/mjpeg_encoder.c
-+++ b/server/mjpeg_encoder.c
-@@ -23,6 +23,7 @@
- #include "mjpeg_encoder.h"
- #include 
- #include 
-+#include 
-
- #define MJPEG_MAX_FPS 25
- #define MJPEG_MIN_FPS 1
-@@ -66,7 +67,7 @@ static const int 
mjpeg_quality_samples[MJPEG_QUALITY_SAMPLE_NUM] = {20, 30, 40,
-  * are not necessarily related to mis-estimation of the bit rate, and we would
-  * like to wait till the stream stabilizes.
-  */
--#define MJPEG_WARMUP_TIME 3000L // 3 sec
-+#define MJPEG_WARMUP_TIME 3000LL // 3 sec
-
- enum {
- MJPEG_QUALITY_EVAL_TYPE_SET,
-@@ -638,7 +639,7 @@ static void 
mjpeg_encoder_adjust_params_to_bit_rate(MJpegEncoder *encoder)
-
- spice_debug("cur-fps=%u new-fps=%u (new/old=%.2f) |"
- "bit-rate=%.2f (Mbps) latency=%u (ms) quality=%d |"
--" new-size-avg %lu , base-size %lu, (new/old=%.2f) ",
-+" new-size-avg %"PRIu64" , base-size %"PRIu64", (new/old=%.2f) 
",
- rate_control->fps, new_fps, 
((double)new_fps)/rate_control->fps,
- ((double)rate_control->byte_rate*8)/1024/1024,
- latency,
-@@ -703,7 +704,7 @@ static void mjpeg_encoder_adjust_fps(MJpegEncoder 
*encoder, uint64_t now)
-
- avg_fps = ((double)rate_control->adjusted_fps_num_frames*1000) /
-   adjusted_fps_time_passed;
--spice_debug("#frames-adjust=%lu #adjust-time=%lu avg-fps=%.2f",
-+spice_debug("#frames-adjust=%"PRIu64" #adjust-time=%"PRIu64" 
avg-fps=%.2f",
- rate_control->adjusted_fps_num_frames, 
adjusted_fps_time_passed, avg_fps);
- spice_debug("defined=%u old-adjusted=%.2f", rate_control->fps, 
rate_control->adjusted_fps);
- fps_ratio = avg_fps / rate_control->fps;
-diff --git a/server/red_worker.c b/server/red_wor

Re: [yocto] porting gRPC into Yocto

[Simon Chamlian]

Hi,

I just started using Yocto.

Is there a detailed procedure on how I can port gRPC (for C or C++) into a
Yocto project?

Thanks,

S
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] porting gRPC into Yocto

[Burton, Ross]

There's a grpc recipe in meta-oe:
http://layers.openembedded.org/layerindex/recipe/72419/

Ross

On 21 June 2018 at 19:15, Simon Chamlian  wrote:
> Hi,
>
> I just started using Yocto.
>
> Is there a detailed procedure on how I can port gRPC (for C or C++) into a
> Yocto project?
>
> Thanks,
>
> S
>
>
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] porting gRPC into Yocto

[Rudolf J Streif]

Hi Simon,

Thank you for using the Yocto Project and reaching out.

For any open-source component that you would like to add to the Yocto
Project I recommend that you first have a look at
http://layers.openembedded.org/layerindex/branch/master/recipes/ and
enter the name of the component. Chances are that somebody already did
the work. This is indeed the case with gRPC:
http://layers.openembedded.org/layerindex/recipe/72419/.

If you cannot find a recipe for the component then you should look at
how the component is built. Most C/C++ components use some sort of a
build system such as GNU Autotools or CMake. The Yocto Project
documentation has sections for the common build systems.

I hope this answers your question.

Rudi


On 06/21/2018 11:15 AM, Simon Chamlian wrote:
> Hi,
>
> I just started using Yocto.
>
> Is there a detailed procedure on how I can port gRPC (for C or C++)
> into a Yocto project?
>
> Thanks,
>
> S
>
>
>
>
>
>
>
>
-- 
Rudolf J Streif



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] porting gRPC into Yocto

[Simon Chamlian]

Thank you everyone for such a prompt response.

What do I do with the grpc_1.8.5.bb

recipe file (sorry for my ignorance, it has been 1 day I am using Yocto)?

Simon




On Thu, Jun 21, 2018 at 2:29 PM, Rudolf J Streif 
wrote:

> Hi Simon,
>
> Thank you for using the Yocto Project and reaching out.
>
> For any open-source component that you would like to add to the Yocto
> Project I recommend that you first have a look at
> http://layers.openembedded.org/layerindex/branch/master/recipes/ and
> enter the name of the component. Chances are that somebody already did the
> work. This is indeed the case with gRPC: http://layers.openembedded.
> org/layerindex/recipe/72419/.
>
> If you cannot find a recipe for the component then you should look at how
> the component is built. Most C/C++ components use some sort of a build
> system such as GNU Autotools or CMake. The Yocto Project documentation has
> sections for the common build systems.
>
> I hope this answers your question.
>
> Rudi
>
> On 06/21/2018 11:15 AM, Simon Chamlian wrote:
>
> Hi,
>
> I just started using Yocto.
>
> Is there a detailed procedure on how I can port gRPC (for C or C++) into a
> Yocto project?
>
> Thanks,
>
> S
>
>
>
>
>
>
>
>
> --
> Rudolf J Streif
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] porting gRPC into Yocto

[Stephen Lawrence]

>From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
>On Behalf Of Simon Chamlian
>Sent: 21 June 2018 19:50
>To: Rudolf J Streif 
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] porting gRPC into Yocto
>
>Thank you everyone for such a prompt response.
>
>What do I do with the 
>http://cgit.openembedded.org/meta-openembedded/tree/meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb?h=master
> recipe file (sorry >for my ignorance, it has been 1 day I am using Yocto)?
>
>Simon

Hi Simon,

The Yocto Project online documentation set [1] contains some useful development 
manuals that guide you through some
common use cases for using Yocto. Such as adding a package to an existing image.

There have also been some good books written on embedded development with 
Yocto. A more recent one is 
"Embedded Linux Systems with the Yocto Project" by Rudolf J. Streif from 
Prentice Hall. You'll easily get a return on the
investment.

[1] https://www.yoctoproject.org/docs/

Regards

Steve
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Adding GCC to system root image

[Krishna Priya]

Hello all,

I am trying to add gcc to the system image by modifying the following
files.
poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc

+ IMAGE_INSTALL +="opkg"
+ IMAGE_INSTALL +="packagegroup-core-buildessential"

poky/build/conf/local.conf
+ EXTRA_IMAGE_FEATURES = "tools-sdk dev-pkgs"

When I build the whole image, I get the following errors :
update-alternatives: Error: cannot register alternative cmp to /bin/cmp
since it is already registered to /usr/bin/cmp
update-alternatives: Error: cannot register alternative diff to /bin/diff
since it is already registered to /usr/bin/diff
update-alternatives: Error: cannot register alternative cmp to /bin/cmp
since it is already registered to /usr/bin/cmp
update-alternatives: Error: cannot register alternative diff to /bin/diff
since it is already registered to /usr/bin/diff
update-alternatives: Error: cannot register alternative ar to /usr/bin/ar
since it is already registered to /bin/ar
update-alternatives: Error: cannot register alternative strings to
/usr/bin/strings since it is already registered to /bin/strings
.
.
.
.
.
ERROR: Multilib check error: duplicate files
poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h
poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h
is not the same
ERROR: Multilib check error: duplicate files
poky/build/tmp-glibc/work/XX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h
poky/build/tmp-glibc/work/apq8096-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h
is not the same
ERROR: Function failed: do_rootfs

Please let me know the workaround to solve this error. Thanks.
Regards,
-Priya.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding GCC to system root image

[Khem Raj]

On Thu, Jun 21, 2018 at 4:02 PM Krishna Priya
 wrote:
>
> Hello all,
>
> I am trying to add gcc to the system image by modifying the following files.
> poky/meta-qti-bsp/recipies-products/images/ BASE_IMAGE.inc
>
> + IMAGE_INSTALL +="opkg"
> + IMAGE_INSTALL +="packagegroup-core-buildessential"
>
> poky/build/conf/local.conf
> + EXTRA_IMAGE_FEATURES = "tools-sdk dev-pkgs"
>
> When I build the whole image, I get the following errors :
> update-alternatives: Error: cannot register alternative cmp to /bin/cmp since 
> it is already registered to /usr/bin/cmp
> update-alternatives: Error: cannot register alternative diff to /bin/diff 
> since it is already registered to /usr/bin/diff
> update-alternatives: Error: cannot register alternative cmp to /bin/cmp since 
> it is already registered to /usr/bin/cmp
> update-alternatives: Error: cannot register alternative diff to /bin/diff 
> since it is already registered to /usr/bin/diff
> update-alternatives: Error: cannot register alternative ar to /usr/bin/ar 
> since it is already registered to /bin/ar
> update-alternatives: Error: cannot register alternative strings to 
> /usr/bin/strings since it is already registered to /bin/strings
> .
> .
> .
> .
> .
> ERROR: Multilib check error: duplicate files 
> poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h
>  
> poky/build/tmp-glibc/work/XXX80XX-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h
>  is not the same
> ERROR: Multilib check error: duplicate files 
> poky/build/tmp-glibc/work/XX80XX-oe-linux/machine-drone-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h
>  
> poky/build/tmp-glibc/work/apq8096-oe-linux/machine-drone-image/1.0-r0/rootfs/usr/include/fpu_control.h
>  is not the same
> ERROR: Function failed: do_rootfs
>
> Please let me know the workaround to solve this error. Thanks.

perhaps providing more information about which target arch and which
release etc. would be helpful.
If you post Build Configuration thats emitted by bitbake at beginning
of build, it provides good information on baseline.

> Regards,
> -Priya.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] openssl does not support building for SDK_MACHINE x86_64-mingw32

[Jaewon Lee]

Hi all,


Since December, glib is pulling python3 for codegen, which because of 
BBCLASSEXTENDS, tries to build nativesdk-python3 which in turn tries to build 
nativesdk-openssl, and it looks like openssl does not support it  
SDK_MACHINE=x86_64-mingw32

There is a do_configure error and I get

| DEBUG: Executing shell function do_configure
| Usage: Configure [no- ...] [enable- ...] 
[experimental- ...] [-Dxxx] [-lxxx] [-Lxxx] [-fxxx] [-Kxxx] 
[no-hw-xxx|no-hw] [[no-]threads] [[no-]shared] [[no-]zlib|zlib-dynamic] 
[no-asm] [no-dso] [no-krb5] [sctp] [386] [--prefix=DIR] 
[--openssldir=OPENSSLDIR] [--with-xxx[=vvv]] [--test-sanity] os/compiler[:flags]

| pick os/compiler from:
| BC-32 BS2000-OSD BSD-generic32 BSD-generic64 BSD-ia64 BSD-sparc64 BSD-sparcv8
| BSD-x86 BSD-x86-elf BSD-x86_64 Cygwin Cygwin-x86_64 DJGPP MPE/iX-gcc OS2-EMX
| OS390-Unix QNX6 QNX6-i386 ReliantUNIX SINIX SINIX-N UWIN VC-CE VC-WIN32
...
And there is a long list of available options. I see mingw and mingw64 in this 
list but no mingw32

I do see a patch from Juro in meta-mingw-contrib:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-mingw-contrib/commit/?h=juro/jethro/openssl&id=9060e6feb38bddf0e130dedf5666b3b7492246f1
which seems to be what I need, but with this applied,  I get nativesdk-gdbm 
compile failures saying it cant find header files


| ../../gdbm-1.13/src/gdbmdump.c:20:11: fatal error: pwd.h: No such file or 
directory
|  # include 
|^~~
| compilation terminated.

| ../../gdbm-1.13/src/gdbmimp.c:21:11: fatal error: arpa/inet.h: No such file 
or directory
|  # include 
|^
| compilation terminated.

Any ideas/pointers?


Thanks,
Jaewon

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto