Re: [OE-core] [meta][PATCH 1/2] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas PERROT
Hi,

I agree, so I cleaned up, split into several commits, then superseded this
one.

Best regards,
Thomas P.

On Wed, Oct 25, 2017 at 1:06 PM, André Draszik  wrote:

> On Wed, 2017-10-25 at 11:13 +0100, André Draszik wrote:
> > On Wed, 2017-10-25 at 09:32 +0200, Thomas Perrot wrote:
> > > - Bad image type replacement for aarch64
> > > - Fix DTB path in fitimage.its
> >
> > It doesn't look like the DTB bit is still relevant in this commit.
> >
> > > - Ignore fitImage type in do_bundle_initramfs task because the
> packaging
> > > is made by do_assemble_fitimage_initramfs
> > > - the images for arm64 are not compressed the linux_comp variable must
> > > therefore be none
> >
> > I think it would also make sense to split this into multiple commits, as
> > your aarch64 fixes and fitimage fixes aren't directly related.
>
> To be more clear, your fix to kernel.bbclass is independent of everything
> else and doesn't apply to aarch64 only, so it should be a separate commit.
>
>
> Cheers,
> Andre'
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] kernel-fitimage: add DTB_LOAD to set dtb address

2017-10-25 Thread Thomas PERROT
Hi,

it would seem that it is also necessary to add the entry field on some
targets.

I think the best would to be do as for UBOOT_RD_LOADADDRESS and
UBOOT_RD_ENTRYPOINT.

Best regards,
Thomas P.

On Wed, Oct 25, 2017 at 6:52 PM, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:

> On Wed, Oct 25, 2017 at 5:55 AM, Chunrong Guo 
> wrote:
> > From: Chunrong Guo 
> >
> > kernel-fitimage for arm64 and arm need dynamically sets dtb address,
> > thus we need a flexible way to load dtb address value.
> >
> > Signed-off-by: Chunrong Guo 
> > ---
> >  meta/classes/kernel-fitimage.bbclass | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/meta/classes/kernel-fitimage.bbclass b/meta/classes/kernel-
> fitimage.bbclass
> > index 179185b..479ffd4 100644
> > --- a/meta/classes/kernel-fitimage.bbclass
> > +++ b/meta/classes/kernel-fitimage.bbclass
> > @@ -36,6 +36,8 @@ python __anonymous () {
> >  # Options for the device tree compiler passed to mkimage '-D' feature:
> >  UBOOT_MKIMAGE_DTCOPTS ??= ""
> >
> > +# Options for load dtb address
> > +DTB_LOAD ??= ""
> >  #
> >  # Emit the fitImage ITS header
> >  #
> > @@ -137,6 +139,7 @@ fitimage_emit_section_dtb() {
> >  type = "flat_dt";
> >  arch = "${UBOOT_ARCH}";
> >  compression = "none";
> > +load = <${DTB_LOAD}>;
>
> What happens if it is empty?
>
>
> >  hash@1 {
> >  algo = "${dtb_csum}";
> >  };
> > --
> > 1.9.0
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] libpng: Upgrade 1.6.31 -> 1.6.32

2017-10-25 Thread youngseokyoon
From: youngseok 

Fixed a bug that leaked memory from the png_handle_eXIf pointer.
License file changes are due to updates in Version and Copyright date

Signed-off-by: youngseok 
---
 .../libpng/{libpng_1.6.31.bb => libpng_1.6.32.bb} | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)
 rename meta/recipes-multimedia/libpng/{libpng_1.6.31.bb => libpng_1.6.32.bb} 
(72%)

diff --git a/meta/recipes-multimedia/libpng/libpng_1.6.31.bb 
b/meta/recipes-multimedia/libpng/libpng_1.6.32.bb
similarity index 72%
rename from meta/recipes-multimedia/libpng/libpng_1.6.31.bb
rename to meta/recipes-multimedia/libpng/libpng_1.6.32.bb
index c96ea14..d93e72c 100644
--- a/meta/recipes-multimedia/libpng/libpng_1.6.31.bb
+++ b/meta/recipes-multimedia/libpng/libpng_1.6.32.bb
@@ -2,15 +2,15 @@ SUMMARY = "PNG image format decoding library"
 HOMEPAGE = "http://www.libpng.org/;
 SECTION = "libs"
 LICENSE = "Libpng"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=6f21e4e1f795810b5ea491b333bc6ea1 \
-
file://png.h;endline=144;md5=af300c419a45c53a8d2daa0b7d167a66"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=53f2df0e62ce82307cd1389a9f41e4cf \
+
file://png.h;endline=144;md5=591cf1f8d84a757af46e43c2b9b5ddd9"
 DEPENDS = "zlib"
 
 LIBV = "16"
 
 SRC_URI = 
"${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}${LIBV}/${PV}/${BP}.tar.xz"
-SRC_URI[md5sum] = "1b34eab440263e32cfa39d19413fad54"
-SRC_URI[sha256sum] = 
"232a602de04916b2b5ce6f901829caf419519e6a16cc9cd7c1c91187d3ee8b41"
+SRC_URI[md5sum] = "e01be057a9369183c959b793a685ad15"
+SRC_URI[sha256sum] = 
"c918c3113de74a692f0a1526ce881dc26067763eb3915c57ef3a0f7b6886f59b"
 
 MIRRORS += "${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}${LIBV}/${PV}/ 
${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}${LIBV}/older-releases/${PV}/"
 
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v8] kernel: Add support for multiple kernel packages

2017-10-25 Thread Haris Okanovic


On 10/23/2017 04:38 PM, Saul Wold wrote:


Haris,

We are really really close, one suggestion in the commit message and
linux-yocto-rt needs a fix similar to linux-yocto.inc (or maybe code
removed).

See below

Thanks so much for this work

Sau!

On Thu, 2017-10-19 at 14:19 -0500, Haris Okanovic wrote:

Some distros may want to provide alternate kernel "flavors" via feeds
or
within bootable images. For example, readily available builds which
provide certain diagnostic features can enable developers and testers
to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the
old
name of "kernel", but can be overridden by certain recipes providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel flavors
cannot be the "preferred provider" for virtual/kernel. This is
because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using
the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics --
build
in the old location and may be preferred provider -- while recipes
using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and
don't
provide "virtual/kernel".

Testing:
  1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
 linux-yocto-tiny_4.9.bb so that it may build alongside
 the main kernel.

I would also suggest using an example of KERNEL_PACKAGE_NAME_pn-linux-
yocto-tiny = "tiny-linux", this can be added to a conf file such as
local.conf file in order to allow for a kernel recipe to easily revert
back to being a possible PREFERRED_PROVIDER_virtual/kernel if a single
kernel is needed.

One additional code related comment at the very bottom.



Sure. Updated testing section and successfully re-ran all steps.


Sau!

  2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel
flavors.
  3. Verified image and modules IPKs exist for both:
 tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
 tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
  4. Verified linux-yocto is the "preferred provider", and was built
in
 shared directory: tmp-glibc/work-shared/qemux86/kernel-*
  5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
 core-image-base.bb to include both kernel flavors.
  6. `bitbake core-image-base` to build an image.
  7. Verified image contains two bzImage's under /boot/, with
 "yocto-standard" selected to boot via symlink.

Discussion threads:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openembedded.org_pipermail_openembedded-2Dcore_2015-2DDecemb=DwICaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=CELKDprUza4SWI1u2Fypwugx9Xc02d2vjiezk0izIEM=PTcNwBf0unLuyw5-OdgBzLd6vCdbGwGgr1r1TkqSb8c=
er/thread.html#114122
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openembedded.org_pipermail_openembedded-2Dcore_2017-2DJuly_t=DwICaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=CELKDprUza4SWI1u2Fypwugx9Xc02d2vjiezk0izIEM=sI-EDX5g0v_gF7fpvHRlgMvP6dtdT5Iw4aJAQoa8-AU=
hread.html#139130


Also, can you add the tag for tracking bug/features:
[YOCTO #11363]



Done.


Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to
the
"work" directory in alternate kernel builds, instead of "work-
shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the current
OE-core master. Changes:
  - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
kernel builds, since alternate kernels aren't the
PREFERRED_PROVIDER for virtual/kernel by definition.
  - Remove "virtual/kernel" from PROVIDES in alternate kernel builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.

[PATCH v5]
  - Warn when PN == KERNEL_PACKAGE_NAME (bug # 11905)
  - Add KERNEL_DEPLOYSUBDIR to avoid DEPLOYDIR collisions

[PATCH v6] Add KERNEL_PACKAGE_NAME to kernel-module-split.bbclass for
module recipes; fixes lttng-modules build.

[PATCH v7] Remove second definition of KERNEL_PACKAGE_NAME from
kernel-module-split.bbclass; apply a default in two places where
KERNEL_PACKAGE_NAME is referenced.

[PATCH v8] Rebase onto current master and more fixups.
  - kernel-devicetree.bbclass: Fixup package names
  - 

Re: [OE-core] [PATCH v8] kernel: Add support for multiple kernel packages

2017-10-25 Thread Haris Okanovic



On 10/25/2017 03:00 AM, Bruce Ashfield wrote:

On Thu, Oct 19, 2017 at 3:19 PM, Haris Okanovic  wrote:

Some distros may want to provide alternate kernel "flavors" via feeds or
within bootable images. For example, readily available builds which
provide certain diagnostic features can enable developers and testers to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the old
name of "kernel", but can be overridden by certain recipes providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel flavors
cannot be the "preferred provider" for virtual/kernel. This is because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics -- build
in the old location and may be preferred provider -- while recipes using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and don't
provide "virtual/kernel".

Testing:
  1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
 linux-yocto-tiny_4.9.bb so that it may build alongside
 the main kernel.
  2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel flavors.
  3. Verified image and modules IPKs exist for both:
 tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
 tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
  4. Verified linux-yocto is the "preferred provider", and was built in
 shared directory: tmp-glibc/work-shared/qemux86/kernel-*
  5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
 core-image-base.bb to include both kernel flavors.
  6. `bitbake core-image-base` to build an image.
  7. Verified image contains two bzImage's under /boot/, with
 "yocto-standard" selected to boot via symlink.

Discussion threads:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openembedded.org_pipermail_openembedded-2Dcore_2015-2DDecember_thread.html-23114122=DwIFaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=IQK-3FiOavEFVw7leFD0d4BvVhNPMEK_t-k_zxTTplY=Mi4q3g-xO_2-FIVwIT0ndJOC_NzE0e4Z_VZm4iIkI14=
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openembedded.org_pipermail_openembedded-2Dcore_2017-2DJuly_thread.html-23139130=DwIFaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=IQK-3FiOavEFVw7leFD0d4BvVhNPMEK_t-k_zxTTplY=-PHnINRO8z8mw3j15b6oAimJJFkMcyk_kr2c9mReYx0=

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to the
"work" directory in alternate kernel builds, instead of "work-shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the current
OE-core master. Changes:
  - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
kernel builds, since alternate kernels aren't the
PREFERRED_PROVIDER for virtual/kernel by definition.
  - Remove "virtual/kernel" from PROVIDES in alternate kernel builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.

[PATCH v5]
  - Warn when PN == KERNEL_PACKAGE_NAME (bug # 11905)
  - Add KERNEL_DEPLOYSUBDIR to avoid DEPLOYDIR collisions

[PATCH v6] Add KERNEL_PACKAGE_NAME to kernel-module-split.bbclass for
module recipes; fixes lttng-modules build.

[PATCH v7] Remove second definition of KERNEL_PACKAGE_NAME from
kernel-module-split.bbclass; apply a default in two places where
KERNEL_PACKAGE_NAME is referenced.

[PATCH v8] Rebase onto current master and more fixups.
  - kernel-devicetree.bbclass: Fixup package names
  - depmodwrapper-cross: don't error when called from alt kernel recipes
  - kernel.bbclass: Don't install /boot/image symlink in alt recipes

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_harisokanovic_openembedded-2Dcore_tree_dev_hokanovi_multi-2Dkernel-2Dpackages-2Dv8=DwIFaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=IQK-3FiOavEFVw7leFD0d4BvVhNPMEK_t-k_zxTTplY=WcRCf1pg_c3VTEyiF11sSomaRy_dFiFJE74X4QEFi80=
---
  meta/classes/kernel-devicetree.bbclass |   8 +-
  meta/classes/kernel-module-split.bbclass   |   9 +-
  meta/classes/kernel.bbclass| 114 +
  

[OE-core] [PATCH] wic: Subcommands now use a common verify_native_sysroot()

2017-10-25 Thread Saul Wold
Change the parsing order so that --vars and --native-sysroot can be
available to all subcommands, this also allows us to use a single
function to verify or build the wic-tools native-sysroot needed for
the commands, to ensure we don't use the possibly bad host commands.

[YOCTO #12173]

Signed-off-by: Saul Wold 
---
 scripts/wic | 51 ---
 1 file changed, 28 insertions(+), 23 deletions(-)

diff --git a/scripts/wic b/scripts/wic
index 097084a6033..3b4e2df86a5 100755
--- a/scripts/wic
+++ b/scripts/wic
@@ -105,6 +105,23 @@ class RootfsArgAction(argparse.Action):
 
 namespace.__dict__['rootfs_dir'][key] = rootfs_dir
 
+def verify_native_sysroot(options):
+if options.vars_dir:
+BB_VARS.vars_dir = options.vars_dir
+
+if options.native_sysroot:
+native_sysroot = options.native_sysroot
+else:
+native_sysroot = get_bitbake_var("RECIPE_SYSROOT_NATIVE", "wic-tools")
+
+if not native_sysroot or not os.path.isdir(native_sysroot):
+logger.info("Building wic-tools...\n")
+if bitbake_main(BitBakeConfigParameters("bitbake wic-tools".split()),
+cookerdata.CookerConfiguration()):
+raise WicError("bitbake wic-tools failed")
+
+if not native_sysroot:
+raise WicError("Unable to find the location of the native tools 
sysroot")
 
 def wic_create_subcommand(options, usage_str):
 """
@@ -164,15 +181,7 @@ def wic_create_subcommand(options, usage_str):
"(Use -e/--image-name to specify it)")
 native_sysroot = options.native_sysroot
 
-if not options.vars_dir and (not native_sysroot or not 
os.path.isdir(native_sysroot)):
-logger.info("Building wic-tools...\n")
-if bitbake_main(BitBakeConfigParameters("bitbake wic-tools".split()),
-cookerdata.CookerConfiguration()):
-raise WicError("bitbake wic-tools failed")
-native_sysroot = get_bitbake_var("RECIPE_SYSROOT_NATIVE", "wic-tools")
-
-if not native_sysroot:
-raise WicError("Unable to find the location of the native tools 
sysroot")
+verify_native_sysroot(options)
 
 wks_file = options.wks_file
 
@@ -241,6 +250,7 @@ def wic_ls_subcommand(args, usage_str):
 Command-line handling for list content of images.
 The real work is done by engine.wic_ls()
 """
+verify_native_sysroot(args)
 engine.wic_ls(args, args.native_sysroot)
 
 def wic_cp_subcommand(args, usage_str):
@@ -248,6 +258,7 @@ def wic_cp_subcommand(args, usage_str):
 Command-line handling for copying files/dirs to images.
 The real work is done by engine.wic_cp()
 """
+verify_native_sysroot(args)
 engine.wic_cp(args, args.native_sysroot)
 
 def wic_rm_subcommand(args, usage_str):
@@ -255,6 +266,7 @@ def wic_rm_subcommand(args, usage_str):
 Command-line handling for removing files/dirs from images.
 The real work is done by engine.wic_rm()
 """
+verify_native_sysroot(args)
 engine.wic_rm(args, args.native_sysroot)
 
 def wic_write_subcommand(args, usage_str):
@@ -262,6 +274,7 @@ def wic_write_subcommand(args, usage_str):
 Command-line handling for writing images.
 The real work is done by engine.wic_write()
 """
+verify_native_sysroot(args)
 engine.wic_write(args, args.native_sysroot)
 
 def wic_help_subcommand(args, usage_str):
@@ -332,9 +345,6 @@ def wic_init_parser_create(subparser):
 subparser.add_argument("-k", "--kernel-dir", dest="kernel_dir",
   help="path to the dir containing the kernel to use "
"in the .wks bootimg")
-subparser.add_argument("-n", "--native-sysroot", dest="native_sysroot",
-  help="path to the native sysroot containing the tools "
-   "to use to build the image")
 subparser.add_argument("-s", "--skip-build-check", dest="build_check",
   action="store_false", default=True, help="skip the build 
check")
 subparser.add_argument("-f", "--build-rootfs", action="store_true", 
help="build rootfs")
@@ -344,9 +354,6 @@ def wic_init_parser_create(subparser):
 subparser.add_argument("-m", "--bmap", action="store_true", help="generate 
.bmap")
 subparser.add_argument("--no-fstab-update" ,action="store_true",
   help="Do not change fstab file.")
-subparser.add_argument("-v", "--vars", dest='vars_dir',
-  help="directory with .env files that store "
-   "bitbake variables")
 subparser.add_argument("-D", "--debug", dest="debug", action="store_true",
   default=False, help="output debug information")
 return
@@ -386,8 +393,6 @@ def imgtype(arg):
 def wic_init_parser_ls(subparser):
 subparser.add_argument("path", type=imgtype,
 help="image spec: [:[]]")
-subparser.add_argument("-n", 

[OE-core] [PATCH] wic/misc: Use bitbake -e -b options for env generation

2017-10-25 Thread Saul Wold
The -e option generates the environment and the -b only select the
one recipe and suppresses the dependency generation as that is not
needed for environment generation.

Signed-off-by: Saul Wold 
---
 scripts/lib/wic/misc.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/wic/misc.py b/scripts/lib/wic/misc.py
index ee888b478cc..de0307844e7 100644
--- a/scripts/lib/wic/misc.py
+++ b/scripts/lib/wic/misc.py
@@ -222,7 +222,7 @@ class BitbakeVars(defaultdict):
 return
 else:
 # Get bitbake -e output
-cmd = "bitbake -e"
+cmd = "bitbake -e -b"
 if image:
 cmd += " %s" % image
 
-- 
2.13.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] e2fsprogs-ptest: improve reproducibility

2017-10-25 Thread Juro Bystricky
Remove several Makefiles containing build host references.
While at it, also remove some additional files not needed for
testing.

Signed-off-by: Juro Bystricky 
---
 meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb
index 7fba8eb..00093cc 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb
@@ -109,4 +109,9 @@ do_install_ptest() {
cp -R --no-dereference --preserve=mode,links -v ${B}/tests 
${D}${PTEST_PATH}/test
cp -R --no-dereference --preserve=mode,links -v ${S}/tests/* 
${D}${PTEST_PATH}/test
sed -e 's!../e2fsck/e2fsck!e2fsck!g' -i ${D}${PTEST_PATH}/test/*/expect*
+
+   # Remove various files
+   find "${D}${PTEST_PATH}" -type f \
+   \( -name 'Makefile' -o -name 'Makefile.in' -o -name '*.o' -o -name 
'*.c' -o -name '*.h' \)\
+   -exec  rm -f {} +
 }
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 0/2] version bump bc to 1.07.1

2017-10-25 Thread Josef Holzmayr

Hi Jose,

On 25.10.2017 17:16, Jose Lamego wrote:
A previous upgrade attempt [1] showed that bc version 1.07.1 not only 
needs ed in the host (a regression from 1.06) but also shows a Parallel 
Make Race that requires unsetting PARALLEL_MAKE variable. I contacted 
the upstream maintainer and he is aware of this situation and has 
developed and tested a version 1.07.2, (however is not available for 
download yet). The upgrade was delayed for this reason (more details in 
the patch comments thread).


Interesting, thanks for pointing that out!


That said, Is there any urgent need for the upgrade to 1.07.1?


Absolutely not. The story behind this upgrade is that at OEDEM, we 
discussed version bumps as a way for new contributors to get up to 
speed. So when the upgradeable recipes report came in shortly 
afterwards, I just picked something that looked innocent enough and gave 
it a try. I'm absolutely fine with ignoring this patchset for the given 
reasons.


On a side note, I believe bc 1.07.1 license should be GPLv3+ & LGPLv3 
only, unless I'm missing something.


Alex and I actually discussed that in the meantime and we concluded that 
given license notices in the source itself and the description on the 
home page that it actually is only "GPLv3+". But thats just a side notice.


Thanks for the heads up!

Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] ✗ patchtest: failure for "[meta] Fix some issues in the ..." and 2 more

2017-10-25 Thread Patchwork
== Series Details ==

Series: "[meta] Fix some issues in the ..." and 2 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9488/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch[meta,1/3] Fix some issues in the fitImage generation
 Issue Shortlog does not follow expected format 
[test_shortlog_format] 
  Suggested fixCommit shortlog (first line of commit message) should follow 
the format ": "



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

2017-10-25 Thread Slater, Joseph
I found that libn32-gobject-introspection would not compile without the remove, 
but I could check again.  Joe

-Original Message-
From: Andre McCurdy [mailto:armccu...@gmail.com] 
Sent: Wednesday, October 25, 2017 10:19 AM
To: Alexander Kanavin
Cc: Slater, Joseph; OE Core mailing list
Subject: Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

On Wed, Oct 25, 2017 at 4:14 AM, Alexander Kanavin 
 wrote:
> On 10/25/2017 02:43 AM, Andre McCurdy wrote:
>>
>> On Tue, Oct 24, 2017 at 4:23 PM, Joe Slater  wrote:
>>>
>>> qemu-usermode is only available for mips64 and o32 code.
>>
>> Isn't that already handled by 
>> meta/conf/machine/include/mips/arch-mips.inc
>>
>># user mode qemu doesn't support mips64 n32: "Invalid ELF image 
>> for this architecture"
>>MACHINE_FEATURES_BACKFILL_CONSIDERED_append = "
>> ${@bb.utils.contains('TUNE_FEATURES', 'n32', 'qemu-usermode', '', d)}"
>
> Yes, but this is really unreadable isn't it :) I don't see how anyone 
> could grasp that the above means "remove qemu-usermode from 
> MACHINE_FEATURES if
> n32 is in TUNE_FEATURES" (without diving into documentation).
>
> Any better way to express this would be appreciated.

Yes, BACKFILL_CONSIDERED always has been concept which baffles a lot of users - 
especially so since we quietly redefined it to mean not only "functionality 
which used to always be enabled but is now configurable" but now also 
"functionality which was not previously enabled but is now configurable and we 
want to enable by default and make it difficult for users to accidentally leave 
disabled".
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 3/3] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage
when UBOOT_SIGN_ENABLE is active:

Dependency loop #1 found:
  do_concat_dtb (dependent Tasks ['linux-yocto_4.10.bb:do_assemble_fitimage'])
  do_install (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot', 
'u-boot_2017.01.bb:do_compile', 'u-boot_2017.01.bb:do_concat_dtb'])
  do_deploy (dependent Tasks ['u-boot_2017.01.bb:do_deploy_dtb', 
'u-boot_2017.01.bb:do_install'])
  do_assemble_fitimage (dependent Tasks ['linux-yocto_4.10.bb:do_compile', 
'u-boot_2017.01.bb:do_deploy'])

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass |  2 +-
 meta/classes/uboot-sign.bbclass  | 21 +
 2 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 9baf399f2e..2779ce5226 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -33,7 +33,7 @@ python __anonymous () {
 # the fitImage:
 if d.getVar('UBOOT_SIGN_ENABLE') == "1":
 uboot_pn = d.getVar('PREFERRED_PROVIDER_u-boot') or 'u-boot'
-d.appendVarFlag('do_assemble_fitimage', 'depends', ' %s:do_deploy' 
% uboot_pn)
+d.appendVarFlag('do_assemble_fitimage', 'depends', ' 
%s:do_deploy_dtb' % uboot_pn)
 }
 
 # Options for the device tree compiler passed to mkimage '-D' feature:
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 8ee904e7df..2f616bf2a9 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -47,16 +47,14 @@ do_deploy_dtb () {
cd ${DEPLOYDIR}
 
if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
-   install ${B}/${UBOOT_DTB_BINARY} ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
-   rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
+   install ${B}/${UBOOT_DTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_BINARY}
fi
if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
-   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
-   rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
+   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_BINARY}
fi
 }
 
@@ -70,11 +68,10 @@ do_concat_dtb () {
oe_runmake EXT_DTB=${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
install ${B}/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
install ${B}/${UBOOT_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_IMAGE}
-   elif [ -e "${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOYDIR}/${UBOOT_DTB_IMAGE}" ]; then
-   cd ${DEPLOYDIR}
-   cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} | tee 
${B}/${UBOOT_BINARY} > ${UBOOT_IMAGE}
+   elif [ -e "${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}" ]; then
+   cat ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} | tee ${B}/${UBOOT_BINARY} > 
${UBOOT_IMAGE}
else
-   bbwarn "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
+   bbfatal "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
fi
fi
 }
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 1/3] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Bad image type replacement for aarch64

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 179185b6b2..9baf399f2e 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -7,9 +7,12 @@ python __anonymous () {
 depends = "%s u-boot-mkimage-native dtc-native" % depends
 d.setVar("DEPENDS", depends)
 
-if d.getVar("UBOOT_ARCH") == "mips":
+uarch = d.getVar("UBOOT_ARCH")
+if uarch == "arm64":
+replacementtype = "Image"
+elif uarch == "mips":
 replacementtype = "vmlinuz.bin"
-elif d.getVar("UBOOT_ARCH") == "x86":
+elif uarch == "x86":
 replacementtype = "bzImage"
 else:
 replacementtype = "zImage"
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 2/3] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Ignore fitImage type in do_bundle_initramfs task because the packaging is made 
by do_assemble_fitimage_initramfs

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel.bbclass | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 756707a3c2..7f8c8985f3 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -208,7 +208,9 @@ do_bundle_initramfs () {
# Backing up kernel image relies on its type(regular file or 
symbolic link)
tmp_path=""
for type in ${KERNEL_IMAGETYPES} ; do
-   if [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
+   if [ "$type" = "fitImage" ] ; then
+   continue
+   elif [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
linkpath=`readlink -n 
${KERNEL_OUTPUT_DIR}/$type`
realpath=`readlink -fn 
${KERNEL_OUTPUT_DIR}/$type`
mv -f $realpath $realpath.bak
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] ✗ patchtest: failure for "[meta] Fix some issues in the ..." and 3 more

2017-10-25 Thread Patchwork
== Series Details ==

Series: "[meta] Fix some issues in the ..." and 3 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9487/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch[meta,1/4] Fix some issues in the fitImage generation
 Issue Shortlog does not follow expected format 
[test_shortlog_format] 
  Suggested fixCommit shortlog (first line of commit message) should follow 
the format ": "



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 3/4] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage
when UBOOT_SIGN_ENABLE is active:

Dependency loop #1 found:
  do_concat_dtb (dependent Tasks ['linux-yocto_4.10.bb:do_assemble_fitimage'])
  do_install (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot', 
'u-boot_2017.01.bb:do_compile', 'u-boot_2017.01.bb:do_concat_dtb'])
  do_deploy (dependent Tasks ['u-boot_2017.01.bb:do_deploy_dtb', 
'u-boot_2017.01.bb:do_install'])
  do_assemble_fitimage (dependent Tasks ['linux-yocto_4.10.bb:do_compile', 
'u-boot_2017.01.bb:do_deploy'])

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass |  2 +-
 meta/classes/uboot-sign.bbclass  | 21 +
 2 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 9baf399f2e..2779ce5226 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -33,7 +33,7 @@ python __anonymous () {
 # the fitImage:
 if d.getVar('UBOOT_SIGN_ENABLE') == "1":
 uboot_pn = d.getVar('PREFERRED_PROVIDER_u-boot') or 'u-boot'
-d.appendVarFlag('do_assemble_fitimage', 'depends', ' %s:do_deploy' 
% uboot_pn)
+d.appendVarFlag('do_assemble_fitimage', 'depends', ' 
%s:do_deploy_dtb' % uboot_pn)
 }
 
 # Options for the device tree compiler passed to mkimage '-D' feature:
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 8ee904e7df..2f616bf2a9 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -47,16 +47,14 @@ do_deploy_dtb () {
cd ${DEPLOYDIR}
 
if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
-   install ${B}/${UBOOT_DTB_BINARY} ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
-   rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
+   install ${B}/${UBOOT_DTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_BINARY}
fi
if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
-   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
-   rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
+   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_BINARY}
fi
 }
 
@@ -70,11 +68,10 @@ do_concat_dtb () {
oe_runmake EXT_DTB=${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
install ${B}/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
install ${B}/${UBOOT_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_IMAGE}
-   elif [ -e "${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOYDIR}/${UBOOT_DTB_IMAGE}" ]; then
-   cd ${DEPLOYDIR}
-   cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} | tee 
${B}/${UBOOT_BINARY} > ${UBOOT_IMAGE}
+   elif [ -e "${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}" ]; then
+   cat ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} | tee ${B}/${UBOOT_BINARY} > 
${UBOOT_IMAGE}
else
-   bbwarn "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
+   bbfatal "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
fi
fi
 }
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 2/4] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Ignore fitImage type in do_bundle_initramfs task because the packaging is made 
by do_assemble_fitimage_initramfs

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel.bbclass | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 756707a3c2..7f8c8985f3 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -208,7 +208,9 @@ do_bundle_initramfs () {
# Backing up kernel image relies on its type(regular file or 
symbolic link)
tmp_path=""
for type in ${KERNEL_IMAGETYPES} ; do
-   if [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
+   if [ "$type" = "fitImage" ] ; then
+   continue
+   elif [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
linkpath=`readlink -n 
${KERNEL_OUTPUT_DIR}/$type`
realpath=`readlink -fn 
${KERNEL_OUTPUT_DIR}/$type`
mv -f $realpath $realpath.bak
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 4/4] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
aarch64 compression

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-uboot.bbclass | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/meta/classes/kernel-uboot.bbclass 
b/meta/classes/kernel-uboot.bbclass
index 87f02654fa..06d293039a 100644
--- a/meta/classes/kernel-uboot.bbclass
+++ b/meta/classes/kernel-uboot.bbclass
@@ -1,5 +1,5 @@
 uboot_prep_kimage() {
-   if [ -e arch/${ARCH}/boot/compressed/vmlinux ]; then
+   if [ -e arch/${ARCH}/boot/compressed/vmlinux ] ; then
vmlinux_path="arch/${ARCH}/boot/compressed/vmlinux"
linux_suffix=""
linux_comp="none"
@@ -11,8 +11,13 @@ uboot_prep_kimage() {
linux_comp="none"
else
vmlinux_path="vmlinux"
-   linux_suffix=".gz"
-   linux_comp="gzip"
+   if [ "${ARCH}" = "arm64" ] ; then
+   linux_suffix=""
+   linux_comp="none"
+   else
+   linux_suffix=".gz"
+   linux_comp="gzip"
+   fi
fi
 
[ -n "${vmlinux_path}" ] && ${OBJCOPY} -O binary -R .note -R .comment 
-S "${vmlinux_path}" linux.bin
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 1/4] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
Bad image type replacement for aarch64

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 179185b6b2..9baf399f2e 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -7,9 +7,12 @@ python __anonymous () {
 depends = "%s u-boot-mkimage-native dtc-native" % depends
 d.setVar("DEPENDS", depends)
 
-if d.getVar("UBOOT_ARCH") == "mips":
+uarch = d.getVar("UBOOT_ARCH")
+if uarch == "arm64":
+replacementtype = "Image"
+elif uarch == "mips":
 replacementtype = "vmlinuz.bin"
-elif d.getVar("UBOOT_ARCH") == "x86":
+elif uarch == "x86":
 replacementtype = "bzImage"
 else:
 replacementtype = "zImage"
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

2017-10-25 Thread Andre McCurdy
On Wed, Oct 25, 2017 at 4:14 AM, Alexander Kanavin
 wrote:
> On 10/25/2017 02:43 AM, Andre McCurdy wrote:
>>
>> On Tue, Oct 24, 2017 at 4:23 PM, Joe Slater  wrote:
>>>
>>> qemu-usermode is only available for mips64 and o32 code.
>>
>> Isn't that already handled by meta/conf/machine/include/mips/arch-mips.inc
>>
>># user mode qemu doesn't support mips64 n32: "Invalid ELF image for
>> this architecture"
>>MACHINE_FEATURES_BACKFILL_CONSIDERED_append = "
>> ${@bb.utils.contains('TUNE_FEATURES', 'n32', 'qemu-usermode', '', d)}"
>
> Yes, but this is really unreadable isn't it :) I don't see how anyone could
> grasp that the above means "remove qemu-usermode from MACHINE_FEATURES if
> n32 is in TUNE_FEATURES" (without diving into documentation).
>
> Any better way to express this would be appreciated.

Yes, BACKFILL_CONSIDERED always has been concept which baffles a lot
of users - especially so since we quietly redefined it to mean not
only "functionality which used to always be enabled but is now
configurable" but now also "functionality which was not previously
enabled but is now configurable and we want to enable by default and
make it difficult for users to accidentally leave disabled".
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] kernel-fitimage: add DTB_LOAD to set dtb address

2017-10-25 Thread Otavio Salvador
On Wed, Oct 25, 2017 at 5:55 AM, Chunrong Guo  wrote:
> From: Chunrong Guo 
>
> kernel-fitimage for arm64 and arm need dynamically sets dtb address,
> thus we need a flexible way to load dtb address value.
>
> Signed-off-by: Chunrong Guo 
> ---
>  meta/classes/kernel-fitimage.bbclass | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/kernel-fitimage.bbclass 
> b/meta/classes/kernel-fitimage.bbclass
> index 179185b..479ffd4 100644
> --- a/meta/classes/kernel-fitimage.bbclass
> +++ b/meta/classes/kernel-fitimage.bbclass
> @@ -36,6 +36,8 @@ python __anonymous () {
>  # Options for the device tree compiler passed to mkimage '-D' feature:
>  UBOOT_MKIMAGE_DTCOPTS ??= ""
>
> +# Options for load dtb address
> +DTB_LOAD ??= ""
>  #
>  # Emit the fitImage ITS header
>  #
> @@ -137,6 +139,7 @@ fitimage_emit_section_dtb() {
>  type = "flat_dt";
>  arch = "${UBOOT_ARCH}";
>  compression = "none";
> +load = <${DTB_LOAD}>;

What happens if it is empty?


>  hash@1 {
>  algo = "${dtb_csum}";
>  };
> --
> 1.9.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] ✗ patchtest: failure for dhcp: fix build issue with libxml2 support

2017-10-25 Thread Patchwork
== Series Details ==

Series: dhcp: fix build issue with libxml2 support
Revision: 1
URL   : https://patchwork.openembedded.org/series/9485/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence_format] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-connectivity/dhcp/dhcp/0012-dhcp-correct-the-intention-for-xml2-lib-search.patch
  Standard format  Upstream-Status: 
  Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], 
Submitted [where]



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] kernel-fitimage: add DTB_LOAD to set dtb address

2017-10-25 Thread Chunrong Guo
From: Chunrong Guo 

kernel-fitimage for arm64 and arm need dynamically sets dtb address,
thus we need a flexible way to load dtb address value.

Signed-off-by: Chunrong Guo 
---
 meta/classes/kernel-fitimage.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 179185b..479ffd4 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -36,6 +36,8 @@ python __anonymous () {
 # Options for the device tree compiler passed to mkimage '-D' feature:
 UBOOT_MKIMAGE_DTCOPTS ??= ""
 
+# Options for load dtb address
+DTB_LOAD ??= ""
 #
 # Emit the fitImage ITS header
 #
@@ -137,6 +139,7 @@ fitimage_emit_section_dtb() {
 type = "flat_dt";
 arch = "${UBOOT_ARCH}";
 compression = "none";
+load = <${DTB_LOAD}>;
 hash@1 {
 algo = "${dtb_csum}";
 };
-- 
1.9.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] dhcp: fix build issue with libxml2 support

2017-10-25 Thread Awais Belal
A missing case breaks the build when libxml2 is
required and found appropriately. The third argument
to the function AC_SEARCH_LIB is action-if-found which
was mistakenly been used for the case where the library
is not found and hence breaks the configure phase
where it shoud actually pass.
We now pass on silently when action-if-found is
executed.

Signed-off-by: Awais Belal 
---
 ...correct-the-intention-for-xml2-lib-search.patch | 35 ++
 meta/recipes-connectivity/dhcp/dhcp_4.3.6.bb   |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 
meta/recipes-connectivity/dhcp/dhcp/0012-dhcp-correct-the-intention-for-xml2-lib-search.patch

diff --git 
a/meta/recipes-connectivity/dhcp/dhcp/0012-dhcp-correct-the-intention-for-xml2-lib-search.patch
 
b/meta/recipes-connectivity/dhcp/dhcp/0012-dhcp-correct-the-intention-for-xml2-lib-search.patch
new file mode 100644
index 00..6ded764d0e
--- /dev/null
+++ 
b/meta/recipes-connectivity/dhcp/dhcp/0012-dhcp-correct-the-intention-for-xml2-lib-search.patch
@@ -0,0 +1,35 @@
+From 501543b3ef715488a142e3d301ff2733aa33eec7 Mon Sep 17 00:00:00 2001
+From: Awais Belal 
+Date: Wed, 25 Oct 2017 21:00:05 +0500
+Subject: [PATCH] dhcp: correct the intention for xml2 lib search
+
+A missing case breaks the build when libxml2 is
+required and found appropriately. The third argument
+to the function AC_SEARCH_LIB is action-if-found which
+was mistakenly been used for the case where the library
+is not found and hence breaks the configure phase
+where it shoud actually pass.
+We now pass on silently when action-if-found is
+executed.
+
+Signed-off-by: Awais Belal 
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index bfe988a..f0459e6 100644
+--- a/configure.ac
 b/configure.ac
+@@ -608,7 +608,7 @@ AC_ARG_WITH(libxml2,
+   with_libxml2="$withval", with_libxml2="no")
+ 
+ if test x$with_libxml2 != xno; then
+-  AC_SEARCH_LIBS(xmlTextWriterStartElement, [xml2],
++  AC_SEARCH_LIBS(xmlTextWriterStartElement, [xml2],,
+   [if test x$with_libxml2 != xauto; then
+   AC_MSG_FAILURE([*** Cannot find 
xmlTextWriterStartElement with -lxml2 and libxml2 was requested])
+   fi])
+-- 
+2.11.1
+
diff --git a/meta/recipes-connectivity/dhcp/dhcp_4.3.6.bb 
b/meta/recipes-connectivity/dhcp/dhcp_4.3.6.bb
index 4634a01b04..6615ae2555 100644
--- a/meta/recipes-connectivity/dhcp/dhcp_4.3.6.bb
+++ b/meta/recipes-connectivity/dhcp/dhcp_4.3.6.bb
@@ -11,6 +11,7 @@ SRC_URI += 
"file://0001-define-macro-_PATH_DHCPD_CONF-and-_PATH_DHCLIENT_CON.pat
 file://0009-remove-dhclient-script-bash-dependency.patch \
 file://0010-build-shared-libs.patch \
 
file://0011-Moved-the-call-to-isc_app_ctxstart-to-not-get-signal.patch \
+file://0012-dhcp-correct-the-intention-for-xml2-lib-search.patch \
"
 
 SRC_URI[md5sum] = "afa6e9b3eb7539ea048421a82c668adc"
-- 
2.11.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 0/2] version bump bc to 1.07.1

2017-10-25 Thread Jose Lamego

Josef,

A previous upgrade attempt [1] showed that bc version 1.07.1 not only 
needs ed in the host (a regression from 1.06) but also shows a Parallel 
Make Race that requires unsetting PARALLEL_MAKE variable. I contacted 
the upstream maintainer and he is aware of this situation and has 
developed and tested a version 1.07.2, (however is not available for 
download yet). The upgrade was delayed for this reason (more details in 
the patch comments thread).


That said, Is there any urgent need for the upgrade to 1.07.1?

On a side note, I believe bc 1.07.1 license should be GPLv3+ & LGPLv3 
only, unless I'm missing something.


Regards

Jose

References:

[1] https://patchwork.openembedded.org/series/6796/

[2] https://patchwork.openembedded.org/patch/140001/


On 25/10/17 07:34, Josef Holzmayr wrote:

This series bumps bc to version 1.07.1.

The changes include the needed:
- change of license to GPLv3 & LGPLv3 & GPLv2+
- removal of patch which has been upstreamed
- add native class to ed as it is now a build time dependency

Josef Holzmayr (2):
   ed: add native class
   bc: bump version to 1.07.1

  meta/recipes-extended/bc/bc_1.06.bb| 26 
  meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++
  .../bc/files/fix-segment-fault.patch   | 28 --
  meta/recipes-extended/ed/ed_1.14.2.bb  |  3 +++
  4 files changed, 28 insertions(+), 54 deletions(-)
  delete mode 100644 meta/recipes-extended/bc/bc_1.06.bb
  create mode 100644 meta/recipes-extended/bc/bc_1.07.1.bb
  delete mode 100644 meta/recipes-extended/bc/files/fix-segment-fault.patch





-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] Swig dependency error while building firmware with apparmor

2017-10-25 Thread shubhabrata sen
It works perfectly now. Thanks a lot !! Really appreciate the help.

On Wed, Oct 25, 2017 at 2:15 PM, Martin Jansa 
wrote:

> swig-native builds swig for your host system, so that it can be executed
> during the build. So your apparmor configure most likely searches for swig
> in PATH and swig-native dependency will make sure it's there.
>
> On Wed, Oct 25, 2017, 13:56 shubhabrata sen 
> wrote:
>
>> Hi Martin,
>>
>> Thank you for your reply. Could you please give a bit more details about
>> this ? I'm relatively new to the openembedded environment.
>>
>> On Wed, Oct 25, 2017 at 12:28 PM, Martin Jansa 
>> wrote:
>>
>>> you probably want swig-native dependency.
>>>
>>> On Wed, Oct 25, 2017, 11:09 shubhabrata sen 
>>> wrote:
>>>
 Hi,

 I'm trying to build a firmware with the apparmor recipe and I keep
 getting the following error

 *checking for swig... no*
 | checking whether the libapparmor debug output should be enabled... no
 | checking whether the libapparmor man pages should be generated... yes
 | checking for podchecker... podchecker
 | checking for pod2man... pod2man
 | checking whether python bindings are enabled... yes
 *| configure: error: swig is required when enabling python bindings*
 | WARNING: /home/shubhabs/dists/cvp/builds/p1367/tmp/work/
 cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/temp/run.do_configure.8464:1
 exit 1 from 'PERL="${PERL}" PYTHON="/home/shubhabs/dists/
 cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-
 gnueabi/apparmor/2.10.95-r0/recipe-sysroot-native/usr/bin/python-native/python"
 ./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi
 --target=arm-poky-linux-gnueabi --prefix=/usr --libdir=/usr/lib
 --mandir=/usr/share/man --includedir=/usr/include --with-perl 
 --with-python'

 I've included the SWIG recipe in the build and I can successfully build
 the firmware including swig with the bitbake command but somehow the
 apparmor recipe can't find the swig package. Any help regarding this would
 be appreciated.

 Thanks

 Shubh
 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-core

>>>
>>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [V2][PATCH 2/2] tzdata: update 2017c

2017-10-25 Thread Armin Kuster
LICENSE changed to to rewording
https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a

  Briefly:
  Northern Cyprus switches from +03 to +02/+03 on 2017-10-29.
  Fiji ends DST 2018-01-14, not 2018-01-21.
  Namibia switches from +01/+02 to +02 on 2018-04-01.
  Sudan switches from +03 to +02 on 2017-11-01.
  Tonga likely switches from +13/+14 to +13 on 2017-11-05.
  Turks & Caicos switches from -04 to -05/-04 on 2018-11-04.
  A new file tzdata.zi now holds a small text copy of all data.
  The zic input format has been regularized slightly.

  Changes to future time stamps

Northern Cyprus has decided to resume EU rules starting
2017-10-29, thus reinstituting winter time.

Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously
predicted.  (Thanks to Dominic Fok.)  Adjust future predictions
accordingly.

Namibia will switch from +01 with DST to +02 all year on
2017-09-03 at 02:00.  This affects UT offsets starting 2018-04-01
at 02:00.  (Thanks to Steffen Thorsen.)

Sudan will switch from +03 to +02 on 2017-11-01.  (Thanks to Ahmed
Atyya and Yahia Abdalla.)  South Sudan is not switching, so
Africa/Juba is no longer a link to Africa/Khartoum.

Tonga has likely ended its experiment with DST, and will not
adjust its clocks on 2017-11-05.  Although Tonga has not announced
whether it will continue to observe DST, the IATA is assuming that
it will not.  (Thanks to David Wade.)

Turks & Caicos will switch from -04 all year to -05 with US DST on
2018-03-11 at 03:00.  This affects UT offsets starting 2018-11-04
at 02:00.  (Thanks to Steffen Thorsen.)

  Changes to past time stamps

Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03.
(Thanks to Arthur David Olson.)

Detroit did not observe DST in 1967.

Use railway time for Asia/Kolkata before 1941, by switching to
Madras local time (UT +052110) in 1870, then to IST (UT +0530) in
1906.  Also, treat 1941-2's +0630 as DST, like 1942-5.

Europe/Dublin's 1946 and 1947 fallback transitions occurred at
02:00 standard time, not 02:00 DST.  (Thanks to Michael Deckers.)

Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to
American time in 1892, not 1879.  (Thanks to Michael Deckers.)

Adjust the 1867 transition in Alaska to better reflect the
historical record, by changing it to occur on 1867-10-18 at 15:30
Sitka time rather than at the start of 1867-10-17 local time.
Although strictly speaking this is accurate only for Sitka,
the rest of Alaska's blanks need to be filled in somehow.

Fix off-by-one errors in UT offsets for Adak and Nome before 1867.
(Thanks to Michael Deckers.)

Add 7 s to the UT offset in Asia/Yangon before 1920.

  Changes to zone names

Remove Canada/East-Saskatchewan from the 'backward' file, as it
exceeded the 14-character limit and was an unused misnomer anyway.

Signed-off-by: Armin Kuster 
---
 meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} (97%)

diff --git a/meta/recipes-extended/tzdata/tzdata_2017b.bb 
b/meta/recipes-extended/tzdata/tzdata_2017c.bb
similarity index 97%
rename from meta/recipes-extended/tzdata/tzdata_2017b.bb
rename to meta/recipes-extended/tzdata/tzdata_2017c.bb
index 55e8976..9e5b929 100644
--- a/meta/recipes-extended/tzdata/tzdata_2017b.bb
+++ b/meta/recipes-extended/tzdata/tzdata_2017c.bb
@@ -2,15 +2,15 @@ SUMMARY = "Timezone data"
 HOMEPAGE = "http://www.iana.org/time-zones;
 SECTION = "base"
 LICENSE = "PD & BSD & BSD-3-Clause"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ef1a352b901ee7b75a75df8171d6aca7"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
 DEPENDS = "tzcode-native"
 
 SRC_URI = 
"http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;
 UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
 
-SRC_URI[tzdata.md5sum] = "50dc0dc50c68644c1f70804f2e7a1625"
-SRC_URI[tzdata.sha256sum] = 
"f8242a522ea3496b0ce4ff4f2e75a049178da21001a08b8e666d8cbe07d18086"
+SRC_URI[tzdata.md5sum] = "1e751e7e08f8b68530674f04619d894d"
+SRC_URI[tzdata.sha256sum] = 
"d6543f92a929826318e2f44ff3a7611ce5f565a43e10250b42599d0ba4cbd90b"
 
 inherit allarch
 
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [V2][PATCH 1/2] tzcode-native: update to 2017c

2017-10-25 Thread Armin Kuster
LICENSE changes do to rewording
https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a

Backported to fixes from upstream too.

Changes to code

zic and the reference runtime now reject multiple leap seconds
within 28 days of each other, or leap seconds before the Epoch.
As a result, support for double leap seconds, which was
obsolescent and undocumented, has been removed.  Double leap
seconds were an error in the C89 standard; they have never existed
in civil timekeeping.  (Thanks to Robert Elz and Bradley White for
noticing glitches in the code that uncovered this problem.)

zic now warns about use of the obsolescent and undocumented -y
option, and about use of the obsolescent TYPE field of Rule lines.

zic now allows unambiguous abbreviations like "Sa" and "Su" for
weekdays; formerly it rejected them due to a bug.  Conversely, zic
no longer considers non-prefixes to be abbreviations; for example,
it no longer accepts "lF" as an abbreviation for "lastFriday".
Also, zic warns about the undocumented usage with a "last-"
prefix, e.g., "last-Fri".

Similarly, zic now accepts the unambiguous abbreviation "L" for
"Link" in ordinary context and for "Leap" in leap-second context.
Conversely, zic no longer accepts non-prefixes such as "La" as
abbreviations for words like "Leap".

zic no longer accepts leap second lines in ordinary input, or
ordinary lines in leap second input.  Formerly, zic sometimes
warned about this undocumented usage and handled it incorrectly.

The new macro HAVE_TZNAME governs whether the tzname external
variable is exported, instead of USG_COMPAT.  USG_COMPAT now
governs only the external variables "timezone" and "daylight".
This change is needed because the three variables are not in the
same category: although POSIX requires tzname, it specifies the
other two variables as optional.  Also, USG_COMPAT is now 1 or 0:
if not defined, the code attempts to guess it from other macros.

localtime.c and difftime.c no longer require stdio.h, and .c files
other than zic.c no longer require sys/wait.h.

zdump.c no longer assumes snprintf.  (Reported by Jonathan Leffler.)

Calculation of time_t extrema works around a bug in GCC 4.8.4
(Reported by Stan Shebs and Joseph Myers.)

zic.c no longer mistranslates formats of line numbers in non-English
locales.  (Problem reported by Benno Schulenberg.)

Several minor changes have been made to the code to make it a
bit easier to port to MS-Windows and Solaris.  (Thanks to Kees
Dekker for reporting the problems.)

  Changes to documentation and commentary

The two new files 'theory.html' and 'calendars' contain the
contents of the removed file 'Theory'.  The goal is to document
tzdb theory more accessibly.

The zic man page now documents abbreviation rules.

tz-link.htm now covers how to apply tzdata changes to clients.
(Thanks to Jorge Fábregas for the AIX link.)  It also mentions MySQL.

The leap-seconds.list URL has been updated to something that is
more reliable for tzdb.  (Thanks to Tim Parenti and Brian Inglis.)

Signed-off-by: Armin Kuster 
---
 .../files/0001-Fix-Makefile-quoting-bug.patch  | 174 +
 .../files/0002-Port-zdump-to-C90-snprintf.patch| 115 ++
 ...code-native_2017b.bb => tzcode-native_2017c.bb} |  15 +-
 3 files changed, 298 insertions(+), 6 deletions(-)
 create mode 100644 
meta/recipes-extended/tzcode/files/0001-Fix-Makefile-quoting-bug.patch
 create mode 100644 
meta/recipes-extended/tzcode/files/0002-Port-zdump-to-C90-snprintf.patch
 rename meta/recipes-extended/tzcode/{tzcode-native_2017b.bb => 
tzcode-native_2017c.bb} (54%)

diff --git 
a/meta/recipes-extended/tzcode/files/0001-Fix-Makefile-quoting-bug.patch 
b/meta/recipes-extended/tzcode/files/0001-Fix-Makefile-quoting-bug.patch
new file mode 100644
index 000..e49fa09
--- /dev/null
+++ b/meta/recipes-extended/tzcode/files/0001-Fix-Makefile-quoting-bug.patch
@@ -0,0 +1,174 @@
+From b520d20b8122a783f99f088758b78d928f70ee34 Mon Sep 17 00:00:00 2001
+From: Paul Eggert 
+Date: Mon, 23 Oct 2017 11:42:45 -0700
+Subject: [PATCH] Fix Makefile quoting bug
+
+Problem with INSTALLARGS reported by Zefram in:
+https://mm.icann.org/pipermail/tz/2017-October/025360.html
+Fix similar problems too.
+* Makefile (ZIC_INSTALL, VALIDATE_ENV, CC, install)
+(INSTALL, version, INSTALLARGS, right_posix, posix_right)
+(check_public): Use apostrophes to prevent undesirable
+interpretation of names by the shell.  We still do not support
+directory names containing apostrophes or newlines, but this is
+good enough.
+
+Upstream-Status: Backport
+Signed-off-by: Armin Kuster 
+
+* NEWS: Mention this.
+---
+ Makefile | 64 

Re: [OE-core] [PATCH 2/2] bc: bump version to 1.07.1

2017-10-25 Thread Alexander Kanavin

On 10/25/2017 03:34 PM, Josef Holzmayr wrote:

  meta/recipes-extended/bc/bc_1.06.bb| 26 
  meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++


Please enable diff.renames in your git configuration, and resend.

Also the changes to the recipe need to be explained in the commit 
message itself, not in the cover letter (which never makes it into the 
commit history).


Also, how is "GPLv2 & GPLv3+" different to the previous "GPLv2+"?

Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/2] bc: bump version to 1.07.1

2017-10-25 Thread Josef Holzmayr
Signed-off-by: Josef Holzmayr 
---
 meta/recipes-extended/bc/bc_1.06.bb| 26 
 meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++
 .../bc/files/fix-segment-fault.patch   | 28 --
 3 files changed, 25 insertions(+), 54 deletions(-)
 delete mode 100644 meta/recipes-extended/bc/bc_1.06.bb
 create mode 100644 meta/recipes-extended/bc/bc_1.07.1.bb
 delete mode 100644 meta/recipes-extended/bc/files/fix-segment-fault.patch

diff --git a/meta/recipes-extended/bc/bc_1.06.bb 
b/meta/recipes-extended/bc/bc_1.06.bb
deleted file mode 100644
index d8c8a86..000
--- a/meta/recipes-extended/bc/bc_1.06.bb
+++ /dev/null
@@ -1,26 +0,0 @@
-SUMMARY = "Arbitrary precision calculator language"
-HOMEPAGE = "http://www.gnu.org/software/bc/bc.html;
-
-LICENSE = "GPLv2+ & LGPLv2.1"
-LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
-file://COPYING.LIB;md5=d8045f3b8f929c1cb29a1e3fd737b499 \
-
file://bc/bcdefs.h;endline=31;md5=46dffdaf10a99728dd8ce358e45d46d8 \
-
file://dc/dc.h;endline=25;md5=2f9c558cdd80e31b4d904e48c2374328 \
-
file://lib/number.c;endline=31;md5=99434a0898abca7784acfd36b8191199"
-
-SECTION = "base"
-DEPENDS = "flex"
-PR = "r3"
-
-SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz \
-   file://fix-segment-fault.patch "
-
-SRC_URI[md5sum] = "d44b5dddebd8a7a7309aea6c36fda117"
-SRC_URI[sha256sum] = 
"4ef6d9f17c3c0d92d8798e35666175ecd3d8efac4009d6457b5c99cea72c0e33"
-
-inherit autotools texinfo update-alternatives
-
-ALTERNATIVE_${PN} = "dc"
-ALTERNATIVE_PRIORITY = "100"
-
-BBCLASSEXTEND = "native"
diff --git a/meta/recipes-extended/bc/bc_1.07.1.bb 
b/meta/recipes-extended/bc/bc_1.07.1.bb
new file mode 100644
index 000..5e4bd95
--- /dev/null
+++ b/meta/recipes-extended/bc/bc_1.07.1.bb
@@ -0,0 +1,25 @@
+SUMMARY = "Arbitrary precision calculator language"
+HOMEPAGE = "http://www.gnu.org/software/bc/bc.html;
+
+LICENSE = "GPLv2 & GPLv3+ & LGPLv3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
+file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
+
file://bc/bcdefs.h;endline=28;md5=1acd4c17e6f5fe1f387fd12ac7d96fe2 \
+
file://dc/dc.h;endline=22;md5=6b2786d0e2f15f966acc13f3e71f3ce0 \
+
file://lib/number.c;endline=31;md5=5c437fc63f83a46d4d769d4dd1e74525"
+
+SECTION = "base"
+DEPENDS = "flex ed-native"
+PR = "r0"
+
+SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "cda93857418655ea43590736fc3ca9fc"
+SRC_URI[sha256sum] = 
"62adfca89b0a1c0164c2cdca59ca210c1d44c3ffc46daf9931cf4942664cb02a"
+
+inherit autotools texinfo update-alternatives
+
+ALTERNATIVE_${PN} = "dc"
+ALTERNATIVE_PRIORITY = "100"
+
+BBCLASSEXTEND = "native"
diff --git a/meta/recipes-extended/bc/files/fix-segment-fault.patch 
b/meta/recipes-extended/bc/files/fix-segment-fault.patch
deleted file mode 100644
index 20c0da2..000
--- a/meta/recipes-extended/bc/files/fix-segment-fault.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-Upstream-Status: Pending
-
-when run command such as 'echo "a = 13" | bc -l', it segmentation faults.
-This patch is from 
http://www.mail-archive.com/blfs-support@linuxfromscratch.org/msg04602.html.
-
-Signed-off-by: Kai Kang 
-
 bc-1.06/lib/number.c.orig  2003-09-26 21:14:02.0 +
-+++ bc-1.06/lib/number.c   2003-09-26 21:14:26.0 +
-@@ -34,6 +34,7 @@
- #include 
- #include 
- #include 
-+#include 
- #include /* Prototypes needed for external utility routines. */
- 
- #define bc_rt_warn rt_warn
 bc-1.06/bc/load.c.orig 2003-09-26 21:14:14.0 +
-+++ bc-1.06/bc/load.c  2003-09-26 21:14:26.0 +
-@@ -156,7 +156,7 @@
-   long  label_no;
-   long  vaf_name; /* variable, array or function number. */
-   long  func;
--  program_counter save_adr;
-+  static program_counter save_adr;
- 
-   /* Initialize. */
-   str = code;
-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 0/2] version bump bc to 1.07.1

2017-10-25 Thread Josef Holzmayr
This series bumps bc to version 1.07.1.

The changes include the needed:
- change of license to GPLv3 & LGPLv3 & GPLv2+
- removal of patch which has been upstreamed
- add native class to ed as it is now a build time dependency

Josef Holzmayr (2):
  ed: add native class
  bc: bump version to 1.07.1

 meta/recipes-extended/bc/bc_1.06.bb| 26 
 meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++
 .../bc/files/fix-segment-fault.patch   | 28 --
 meta/recipes-extended/ed/ed_1.14.2.bb  |  3 +++
 4 files changed, 28 insertions(+), 54 deletions(-)
 delete mode 100644 meta/recipes-extended/bc/bc_1.06.bb
 create mode 100644 meta/recipes-extended/bc/bc_1.07.1.bb
 delete mode 100644 meta/recipes-extended/bc/files/fix-segment-fault.patch

-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/2] ed: add native class

2017-10-25 Thread Josef Holzmayr
Signed-off-by: Josef Holzmayr 
---
 meta/recipes-extended/ed/ed_1.14.2.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-extended/ed/ed_1.14.2.bb 
b/meta/recipes-extended/ed/ed_1.14.2.bb
index 87d03b1..06d7cd1 100644
--- a/meta/recipes-extended/ed/ed_1.14.2.bb
+++ b/meta/recipes-extended/ed/ed_1.14.2.bb
@@ -33,3 +33,6 @@ do_install() {
rm -f ${D}${infodir}/dir
fi
 }
+
+BBCLASSEXTEND = "native"
+
-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] Swig dependency error while building firmware with apparmor

2017-10-25 Thread Martin Jansa
swig-native builds swig for your host system, so that it can be executed
during the build. So your apparmor configure most likely searches for swig
in PATH and swig-native dependency will make sure it's there.

On Wed, Oct 25, 2017, 13:56 shubhabrata sen 
wrote:

> Hi Martin,
>
> Thank you for your reply. Could you please give a bit more details about
> this ? I'm relatively new to the openembedded environment.
>
> On Wed, Oct 25, 2017 at 12:28 PM, Martin Jansa 
> wrote:
>
>> you probably want swig-native dependency.
>>
>> On Wed, Oct 25, 2017, 11:09 shubhabrata sen 
>> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to build a firmware with the apparmor recipe and I keep
>>> getting the following error
>>>
>>> *checking for swig... no*
>>> | checking whether the libapparmor debug output should be enabled... no
>>> | checking whether the libapparmor man pages should be generated... yes
>>> | checking for podchecker... podchecker
>>> | checking for pod2man... pod2man
>>> | checking whether python bindings are enabled... yes
>>> *| configure: error: swig is required when enabling python bindings*
>>> | WARNING:
>>> /home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/temp/run.do_configure.8464:1
>>> exit 1 from 'PERL="${PERL}"
>>> PYTHON="/home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/recipe-sysroot-native/usr/bin/python-native/python"
>>> ./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi
>>> --target=arm-poky-linux-gnueabi --prefix=/usr --libdir=/usr/lib
>>> --mandir=/usr/share/man --includedir=/usr/include --with-perl --with-python'
>>>
>>> I've included the SWIG recipe in the build and I can successfully build
>>> the firmware including swig with the bitbake command but somehow the
>>> apparmor recipe can't find the swig package. Any help regarding this would
>>> be appreciated.
>>>
>>> Thanks
>>>
>>> Shubh
>>> --
>>> ___
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] Swig dependency error while building firmware with apparmor

2017-10-25 Thread shubhabrata sen
Hi Martin,

Thank you for your reply. Could you please give a bit more details about
this ? I'm relatively new to the openembedded environment.

On Wed, Oct 25, 2017 at 12:28 PM, Martin Jansa 
wrote:

> you probably want swig-native dependency.
>
> On Wed, Oct 25, 2017, 11:09 shubhabrata sen 
> wrote:
>
>> Hi,
>>
>> I'm trying to build a firmware with the apparmor recipe and I keep
>> getting the following error
>>
>> *checking for swig... no*
>> | checking whether the libapparmor debug output should be enabled... no
>> | checking whether the libapparmor man pages should be generated... yes
>> | checking for podchecker... podchecker
>> | checking for pod2man... pod2man
>> | checking whether python bindings are enabled... yes
>> *| configure: error: swig is required when enabling python bindings*
>> | WARNING: /home/shubhabs/dists/cvp/builds/p1367/tmp/work/
>> cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/temp/run.do_configure.8464:1
>> exit 1 from 'PERL="${PERL}" PYTHON="/home/shubhabs/dists/
>> cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-
>> gnueabi/apparmor/2.10.95-r0/recipe-sysroot-native/usr/bin/python-native/python"
>> ./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi
>> --target=arm-poky-linux-gnueabi --prefix=/usr --libdir=/usr/lib
>> --mandir=/usr/share/man --includedir=/usr/include --with-perl --with-python'
>>
>> I've included the SWIG recipe in the build and I can successfully build
>> the firmware including swig with the bitbake command but somehow the
>> apparmor recipe can't find the swig package. Any help regarding this would
>> be appreciated.
>>
>> Thanks
>>
>> Shubh
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] oe-build-perf-report-email.py: add images as MIME objects

2017-10-25 Thread Markus Lehtonen
Add images as separate MIME objects instead of directly embedding images
in the html (as base64 encoded pngs). This makes the emails better
suited for certain email servers/clients.

Signed-off-by: Markus Lehtonen 
---
 scripts/contrib/oe-build-perf-report-email.py | 42 +--
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/scripts/contrib/oe-build-perf-report-email.py 
b/scripts/contrib/oe-build-perf-report-email.py
index 64e85c26ad..913847bbed 100755
--- a/scripts/contrib/oe-build-perf-report-email.py
+++ b/scripts/contrib/oe-build-perf-report-email.py
@@ -25,6 +25,7 @@ import socket
 import subprocess
 import sys
 import tempfile
+from email.mime.image import MIMEImage
 from email.mime.multipart import MIMEMultipart
 from email.mime.text import MIMEText
 
@@ -111,15 +112,6 @@ def decode_png(infile, outfile):
 subprocess.check_output(['optipng', outfile], stderr=subprocess.STDOUT)
 
 
-def encode_png(pngfile):
-"""Encode png into a  html element"""
-with open(pngfile, 'rb') as f:
-data = f.read()
-
-b64_data = base64.b64encode(data)
-return '\n'
-
-
 def mangle_html_report(infile, outfile, pngs):
 """Mangle html file into a email compatible format"""
 paste = True
@@ -144,9 +136,7 @@ def mangle_html_report(infile, outfile, pngs):
 # Replace charts with  elements
 match = re.match('\n'.format(match.group('id') + '.png'))
-png_file = os.path.join(png_dir, match.group('id') + 
'.png')
-f_out.write(encode_png(png_file))
+f_out.write('http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] curl: Security Advisory - curl - CVE-2017-1000254

2017-10-25 Thread Alexander Kanavin

On 10/25/2017 07:40 AM, akuster808 wrote:



On 10/23/2017 03:29 AM, Alexander Kanavin wrote:

On 10/23/2017 10:44 AM, Li Zhou wrote:

Porting patch from  to solve CVE-2017-1000254.


It's better to update to latest version (7.56) instead of backporting
patches, please do that.


Then these should be stagged for Rocko. Work has been done.


Only if master is also fixed at the same time (or sooner) - there cannot 
be a situation where something is fixed in rocko, but not in master. I'm 
fine if it's via CVE backports, but I would prefer a version upgrade.


Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v3] libnl: 3.2.29 -> 3.4.0

2017-10-25 Thread Alexander Kanavin

On 10/25/2017 05:59 AM, Huang Qiyu wrote:

2) Delete one patch "fix-pktloc_syntax_h-race.patch", for it is 
inappropriate,as the verion 3.4.0 has no lib/Makefile.am file.


Apologies, but this is not a satisfactory reason to remove this patch. 
Has the upstream fixed the problem that the patch is addressing? Or have 
they simply rearranged the makefiles, and moved the problematic lines to 
a different makefile? If so, you should rebase the fix onto the new 
location.


Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

2017-10-25 Thread Alexander Kanavin

On 10/25/2017 02:43 AM, Andre McCurdy wrote:

On Tue, Oct 24, 2017 at 4:23 PM, Joe Slater  wrote:

qemu-usermode is only available for mips64 and o32 code.


Isn't that already handled by meta/conf/machine/include/mips/arch-mips.inc

   # user mode qemu doesn't support mips64 n32: "Invalid ELF image for
this architecture"
   MACHINE_FEATURES_BACKFILL_CONSIDERED_append = "
${@bb.utils.contains('TUNE_FEATURES', 'n32', 'qemu-usermode', '', d)}"


Yes, but this is really unreadable isn't it :) I don't see how anyone 
could grasp that the above means "remove qemu-usermode from 
MACHINE_FEATURES if n32 is in TUNE_FEATURES" (without diving into 
documentation).


Any better way to express this would be appreciated.

Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta][PATCH 1/2] Fix some issues in the fitImage generation

2017-10-25 Thread André Draszik
On Wed, 2017-10-25 at 11:13 +0100, André Draszik wrote:
> On Wed, 2017-10-25 at 09:32 +0200, Thomas Perrot wrote:
> > - Bad image type replacement for aarch64
> > - Fix DTB path in fitimage.its
> 
> It doesn't look like the DTB bit is still relevant in this commit.
> 
> > - Ignore fitImage type in do_bundle_initramfs task because the packaging
> > is made by do_assemble_fitimage_initramfs
> > - the images for arm64 are not compressed the linux_comp variable must
> > therefore be none
> 
> I think it would also make sense to split this into multiple commits, as
> your aarch64 fixes and fitimage fixes aren't directly related.

To be more clear, your fix to kernel.bbclass is independent of everything
else and doesn't apply to aarch64 only, so it should be a separate commit.


Cheers,
Andre'

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] Swig dependency error while building firmware with apparmor

2017-10-25 Thread Martin Jansa
you probably want swig-native dependency.

On Wed, Oct 25, 2017, 11:09 shubhabrata sen 
wrote:

> Hi,
>
> I'm trying to build a firmware with the apparmor recipe and I keep getting
> the following error
>
> *checking for swig... no*
> | checking whether the libapparmor debug output should be enabled... no
> | checking whether the libapparmor man pages should be generated... yes
> | checking for podchecker... podchecker
> | checking for pod2man... pod2man
> | checking whether python bindings are enabled... yes
> *| configure: error: swig is required when enabling python bindings*
> | WARNING:
> /home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/temp/run.do_configure.8464:1
> exit 1 from 'PERL="${PERL}"
> PYTHON="/home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/recipe-sysroot-native/usr/bin/python-native/python"
> ./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi
> --target=arm-poky-linux-gnueabi --prefix=/usr --libdir=/usr/lib
> --mandir=/usr/share/man --includedir=/usr/include --with-perl --with-python'
>
> I've included the SWIG recipe in the build and I can successfully build
> the firmware including swig with the bitbake command but somehow the
> apparmor recipe can't find the swig package. Any help regarding this would
> be appreciated.
>
> Thanks
>
> Shubh
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta][pyro][PATCHv3] Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage

2017-10-25 Thread André Draszik
On Wed, 2017-10-25 at 09:18 +0200, Thomas Perrot wrote:
> When UBOOT_SIGN_ENABLE is active:
> 
> Dependency loop #1 found:
>   do_concat_dtb (dependent Tasks ['linux-
> yocto_4.10.bb:do_assemble_fitimage'])
>   do_install (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot', 'u-
> boot_2017.01.bb:do_compile', 'u-boot_2017.01.bb:do_concat_dtb'])
>   do_deploy (dependent Tasks ['u-boot_2017.01.bb:do_deploy_dtb', 'u-
> boot_2017.01.bb:do_install'])
>   do_assemble_fitimage (dependent Tasks ['linux-yocto_4.10.bb:do_compile', 
> 'u-boot_2017.01.bb:do_deploy'])

Thanks for adding more details of the problem. Please compare this against
the commit message of

http://git.openembedded.org/openembedded-core/commit/?id=7da4c0a56eb2027b3e36b9e42f1f83dfb02bb920

Looks exactly the same.

Are you saying that
http://git.openembedded.org/openembedded-core/commit/?id=7da4c0a56eb2027b3e36b9e42f1f83dfb02bb920
http://git.openembedded.org/openembedded-core/commit/?id=e44b72ab45c757cc83c7856c118588f1af299790
don't fix your problem?


Cheers,
Andre'

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta][PATCH 1/2] Fix some issues in the fitImage generation

2017-10-25 Thread André Draszik
On Wed, 2017-10-25 at 09:32 +0200, Thomas Perrot wrote:
> - Bad image type replacement for aarch64
> - Fix DTB path in fitimage.its

It doesn't look like the DTB bit is still relevant in this commit.

> - Ignore fitImage type in do_bundle_initramfs task because the packaging
> is made by do_assemble_fitimage_initramfs
> - the images for arm64 are not compressed the linux_comp variable must
> therefore be none

I think it would also make sense to split this into multiple commits, as
your aarch64 fixes and fitimage fixes aren't directly related.

> Signed-off-by: Thomas Perrot 
> ---
>  meta/classes/kernel-fitimage.bbclass |  7 +--
>  meta/classes/kernel-uboot.bbclass| 11 ---
>  meta/classes/kernel.bbclass  |  4 +++-
>  3 files changed, 16 insertions(+), 6 deletions(-)
> 
> diff --git a/meta/classes/kernel-fitimage.bbclass b/meta/classes/kernel-
> fitimage.bbclass
> index 179185b6b2..0789ba611f 100644
> --- a/meta/classes/kernel-fitimage.bbclass
> +++ b/meta/classes/kernel-fitimage.bbclass
> @@ -7,10 +7,13 @@ python __anonymous () {
>  depends = "%s u-boot-mkimage-native dtc-native" % depends
>  d.setVar("DEPENDS", depends)
>  
> -if d.getVar("UBOOT_ARCH") == "mips":
> +uarch = d.getVar("UBOOT_ARCH")
> +if uarch == "mips":
>  replacementtype = "vmlinuz.bin"
> -elif d.getVar("UBOOT_ARCH") == "x86":
> +elif uarch == "x86":
>  replacementtype = "bzImage"
> +elif uarch == "arm64":
> +replacementtype = "Image"

Can you keep these tests in alphabetical order please?

>  else:
>  replacementtype = "zImage"
>  
> diff --git a/meta/classes/kernel-uboot.bbclass b/meta/classes/kernel-
> uboot.bbclass
> index 87f02654fa..06d293039a 100644
> --- a/meta/classes/kernel-uboot.bbclass
> +++ b/meta/classes/kernel-uboot.bbclass
> @@ -1,5 +1,5 @@
>  uboot_prep_kimage() {
> - if [ -e arch/${ARCH}/boot/compressed/vmlinux ]; then
> + if [ -e arch/${ARCH}/boot/compressed/vmlinux ] ; then
>   vmlinux_path="arch/${ARCH}/boot/compressed/vmlinux"
>   linux_suffix=""
>   linux_comp="none"
> @@ -11,8 +11,13 @@ uboot_prep_kimage() {
>   linux_comp="none"
>   else
>   vmlinux_path="vmlinux"
> - linux_suffix=".gz"
> - linux_comp="gzip"
> + if [ "${ARCH}" = "arm64" ] ; then
> + linux_suffix=""
> + linux_comp="none"
> + else
> + linux_suffix=".gz"
> + linux_comp="gzip"
> + fi
>   fi

I believe U-Boot supports decompression on any architecture independent of
kernel decompression support. It also supports multiple decompressors, not
just gzip. It would make sense to rather be able to configure the
compression method for U-Boot in a more generic way (including turning it
off completely) for any supported target.


Cheers,
Andre'

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] Swig dependency error while building firmware with apparmor

2017-10-25 Thread shubhabrata sen
Hi,

I'm trying to build a firmware with the apparmor recipe and I keep getting
the following error

*checking for swig... no*
| checking whether the libapparmor debug output should be enabled... no
| checking whether the libapparmor man pages should be generated... yes
| checking for podchecker... podchecker
| checking for pod2man... pod2man
| checking whether python bindings are enabled... yes
*| configure: error: swig is required when enabling python bindings*
| WARNING:
/home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/temp/run.do_configure.8464:1
exit 1 from 'PERL="${PERL}"
PYTHON="/home/shubhabs/dists/cvp/builds/p1367/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/apparmor/2.10.95-r0/recipe-sysroot-native/usr/bin/python-native/python"
./configure --build=x86_64-linux --host=arm-poky-linux-gnueabi
--target=arm-poky-linux-gnueabi --prefix=/usr --libdir=/usr/lib
--mandir=/usr/share/man --includedir=/usr/include --with-perl --with-python'

I've included the SWIG recipe in the build and I can successfully build the
firmware including swig with the bitbake command but somehow the apparmor
recipe can't find the swig package. Any help regarding this would be
appreciated.

Thanks

Shubh
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 1/2] tzcode-native: update to 2017d

2017-10-25 Thread Yi Zhao

Should be 2017c ?

I encountered a zdump build error on Ubuntu 14.04:

zdump.c:803:1: error: static declaration of ‘snprintf’ follows
non-static declaration
|  snprintf(char *s, size_t size, char const *format, ...)
|  ^

There was a discussion for it on upstream mailing list: 
http://mm.icann.org/pipermail/tz/2017-October/025364.html



Thanks,
Yi

在 2017年10月25日 15:49, Armin Kuster 写道:

LICENSE changes do to rewording

https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a

Changes to code

 zic and the reference runtime now reject multiple leap seconds
 within 28 days of each other, or leap seconds before the Epoch.
 As a result, support for double leap seconds, which was
 obsolescent and undocumented, has been removed.  Double leap
 seconds were an error in the C89 standard; they have never existed
 in civil timekeeping.  (Thanks to Robert Elz and Bradley White for
 noticing glitches in the code that uncovered this problem.)

 zic now warns about use of the obsolescent and undocumented -y
 option, and about use of the obsolescent TYPE field of Rule lines.

 zic now allows unambiguous abbreviations like "Sa" and "Su" for
 weekdays; formerly it rejected them due to a bug.  Conversely, zic
 no longer considers non-prefixes to be abbreviations; for example,
 it no longer accepts "lF" as an abbreviation for "lastFriday".
 Also, zic warns about the undocumented usage with a "last-"
 prefix, e.g., "last-Fri".

 Similarly, zic now accepts the unambiguous abbreviation "L" for
 "Link" in ordinary context and for "Leap" in leap-second context.
 Conversely, zic no longer accepts non-prefixes such as "La" as
 abbreviations for words like "Leap".

 zic no longer accepts leap second lines in ordinary input, or
 ordinary lines in leap second input.  Formerly, zic sometimes
 warned about this undocumented usage and handled it incorrectly.

 The new macro HAVE_TZNAME governs whether the tzname external
 variable is exported, instead of USG_COMPAT.  USG_COMPAT now
 governs only the external variables "timezone" and "daylight".
 This change is needed because the three variables are not in the
 same category: although POSIX requires tzname, it specifies the
 other two variables as optional.  Also, USG_COMPAT is now 1 or 0:
 if not defined, the code attempts to guess it from other macros.

 localtime.c and difftime.c no longer require stdio.h, and .c files
 other than zic.c no longer require sys/wait.h.

 zdump.c no longer assumes snprintf.  (Reported by Jonathan Leffler.)

 Calculation of time_t extrema works around a bug in GCC 4.8.4
 (Reported by Stan Shebs and Joseph Myers.)

 zic.c no longer mistranslates formats of line numbers in non-English
 locales.  (Problem reported by Benno Schulenberg.)

 Several minor changes have been made to the code to make it a
 bit easier to port to MS-Windows and Solaris.  (Thanks to Kees
 Dekker for reporting the problems.)

   Changes to documentation and commentary

 The two new files 'theory.html' and 'calendars' contain the
 contents of the removed file 'Theory'.  The goal is to document
 tzdb theory more accessibly.

 The zic man page now documents abbreviation rules.

 tz-link.htm now covers how to apply tzdata changes to clients.
 (Thanks to Jorge Fábregas for the AIX link.)  It also mentions MySQL.

 The leap-seconds.list URL has been updated to something that is
 more reliable for tzdb.  (Thanks to Tim Parenti and Brian Inglis.)

Signed-off-by: Armin Kuster 
---
  .../tzcode/{tzcode-native_2017b.bb => tzcode-native_2017c.bb}  | 10 +-
  1 file changed, 5 insertions(+), 5 deletions(-)
  rename meta/recipes-extended/tzcode/{tzcode-native_2017b.bb => 
tzcode-native_2017c.bb} (63%)

diff --git a/meta/recipes-extended/tzcode/tzcode-native_2017b.bb 
b/meta/recipes-extended/tzcode/tzcode-native_2017c.bb
similarity index 63%
rename from meta/recipes-extended/tzcode/tzcode-native_2017b.bb
rename to meta/recipes-extended/tzcode/tzcode-native_2017c.bb
index 165d2c6..c8a987f 100644
--- a/meta/recipes-extended/tzcode/tzcode-native_2017b.bb
+++ b/meta/recipes-extended/tzcode/tzcode-native_2017c.bb
@@ -3,16 +3,16 @@
  SUMMARY = "tzcode, timezone zoneinfo utils -- zic, zdump, tzselect"
  LICENSE = "PD & BSD & BSD-3-Clause"
  
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ef1a352b901ee7b75a75df8171d6aca7"

+LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
  
  SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode \

 
http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;
  UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
  
-SRC_URI[tzcode.md5sum] = "afaf15deb13759e8b543d86350385b16"

-SRC_URI[tzcode.sha256sum] = 

[OE-core] ✗ patchtest: failure for "[meta] Fix some issues in the ..." and 1 more

2017-10-25 Thread Patchwork
== Series Details ==

Series: "[meta] Fix some issues in the ..." and 1 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9470/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch[meta,1/2] Fix some issues in the fitImage generation
 Issue Shortlog does not follow expected format 
[test_shortlog_format] 
  Suggested fixCommit shortlog (first line of commit message) should follow 
the format ": "



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta][pyro][PATCHv2] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas PERROT
Hi,

It's done, I just submit the path for the master branch.

Best regards,
Thomas P.

On Tue, Oct 24, 2017 at 9:38 AM, akuster808  wrote:

>
>
> On 10/20/2017 02:47 AM, Thomas Perrot wrote:
> > - Bad image type replacement for aarch64
> > - Fix DTB path in fitimage.its
> > - Ignore fitImage type in do_bundle_initramfs task because the packaging
> is made by do_assemble_fitimage_initramfs
> > - the images for arm64 are not compressed the linux_comp variable must
> therefore be none
> >
> > Signed-off-by: Thomas Perrot 
> > ---
> >  meta/classes/kernel-fitimage.bbclass |  6 +-
> >  meta/classes/kernel-uboot.bbclass| 11 ---
> >  meta/classes/kernel.bbclass  |  4 +++-
> I don't see this in master. Please resubmit for Master.
>
> - armin
> >  3 files changed, 16 insertions(+), 5 deletions(-)
> >
> > diff --git a/meta/classes/kernel-fitimage.bbclass b/meta/classes/kernel-
> fitimage.bbclass
> > index 2630b47316..abbc309b09 100644
> > --- a/meta/classes/kernel-fitimage.bbclass
> > +++ b/meta/classes/kernel-fitimage.bbclass
> > @@ -7,8 +7,11 @@ python __anonymous () {
> >  depends = "%s u-boot-mkimage-native dtc-native" % depends
> >  d.setVar("DEPENDS", depends)
> >
> > -if d.getVar("UBOOT_ARCH") == "x86":
> > +uarch = d.getVar("UBOOT_ARCH")
> > +if uarch == "x86":
> >  replacementtype = "bzImage"
> > +elif uarch == "arm64":
> > +replacementtype = "Image"
> >  else:
> >  replacementtype = "zImage"
> >
> > @@ -351,6 +354,7 @@ fitimage_assemble() {
> >   DTB_PATH="arch/${ARCH}/boot/${DTB}"
> >   fi
> >
> > + DTB=$(echo "${DTB}" | tr '/' '_')
> >   DTBS="${DTBS} ${DTB}"
> >   fitimage_emit_section_dtb ${1} ${DTB} ${DTB_PATH}
> >   done
> > diff --git a/meta/classes/kernel-uboot.bbclass
> b/meta/classes/kernel-uboot.bbclass
> > index 868e97d7a7..940f91d90e 100644
> > --- a/meta/classes/kernel-uboot.bbclass
> > +++ b/meta/classes/kernel-uboot.bbclass
> > @@ -1,12 +1,17 @@
> >  uboot_prep_kimage() {
> > - if [ -e arch/${ARCH}/boot/compressed/vmlinux ]; then
> > + if [ -e arch/${ARCH}/boot/compressed/vmlinux ] ; then
> >   vmlinux_path="arch/${ARCH}/boot/compressed/vmlinux"
> >   linux_suffix=""
> >   linux_comp="none"
> >   else
> >   vmlinux_path="vmlinux"
> > - linux_suffix=".gz"
> > - linux_comp="gzip"
> > + if [ "${ARCH}" = "arm64" ] ; then
> > + linux_suffix=""
> > + linux_comp="none"
> > + else
> > + linux_suffix=".gz"
> > + linux_comp="gzip"
> > + fi
> >   fi
> >
> >   ${OBJCOPY} -O binary -R .note -R .comment -S "${vmlinux_path}"
> linux.bin
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index ce2cab65ae..14677ac0fc 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -219,7 +219,9 @@ do_bundle_initramfs () {
> >   # Backing up kernel image relies on its type(regular file
> or symbolic link)
> >   tmp_path=""
> >   for type in ${KERNEL_IMAGETYPES} ; do
> > - if [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
> > + if [ "$type" = "fitImage" ] ; then
> > + continue
> > + elif [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
> >   linkpath=`readlink -n
> ${KERNEL_OUTPUT_DIR}/$type`
> >   realpath=`readlink -fn
> ${KERNEL_OUTPUT_DIR}/$type`
> >   mv -f $realpath $realpath.bak
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v8] kernel: Add support for multiple kernel packages

2017-10-25 Thread Bruce Ashfield
On Thu, Oct 19, 2017 at 3:19 PM, Haris Okanovic  wrote:
> Some distros may want to provide alternate kernel "flavors" via feeds or
> within bootable images. For example, readily available builds which
> provide certain diagnostic features can enable developers and testers to
> more quickly resolve issues by avoiding lengthy kernel builds.
>
> This change allows for building multiple flavors of the kernel and
> module packages by templatizing kernel package names via a new
> KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the old
> name of "kernel", but can be overridden by certain recipes providing
> alternate kernel flavors.
>
> To maintain compatibility, recipes providing alternate kernel flavors
> cannot be the "preferred provider" for virtual/kernel. This is because
> OE puts the preferred provider's build and source at
> "tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
> "tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
> "tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using the
> default KERNEL_PACKAGE_NAME="kernel" follows the old semantics -- build
> in the old location and may be preferred provider -- while recipes using
> all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and don't
> provide "virtual/kernel".
>
> Testing:
>  1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
> linux-yocto-tiny_4.9.bb so that it may build alongside
> the main kernel.
>  2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel flavors.
>  3. Verified image and modules IPKs exist for both:
> tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
> tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
>  4. Verified linux-yocto is the "preferred provider", and was built in
> shared directory: tmp-glibc/work-shared/qemux86/kernel-*
>  5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
> core-image-base.bb to include both kernel flavors.
>  6. `bitbake core-image-base` to build an image.
>  7. Verified image contains two bzImage's under /boot/, with
> "yocto-standard" selected to boot via symlink.
>
> Discussion threads:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-December/thread.html#114122
> http://lists.openembedded.org/pipermail/openembedded-core/2017-July/thread.html#139130
>
> Signed-off-by: Ioan-Adrian Ratiu 
> Signed-off-by: Gratian Crisan 
> Signed-off-by: Haris Okanovic 
> Coauthored-by: Gratian Crisan 
> Coauthored-by: Haris Okanovic 
> Coauthored-by: Josh Hernstrom 
> ---
> [PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to the
> "work" directory in alternate kernel builds, instead of "work-shared",
> so
> that the two builds don't clobber each other.
>
> [PATCH v3] An updated version of this change rebased onto the current
> OE-core master. Changes:
>  - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
>kernel builds, since alternate kernels aren't the
>PREFERRED_PROVIDER for virtual/kernel by definition.
>  - Remove "virtual/kernel" from PROVIDES in alternate kernel builds.
>
> [PATCH v4] Another rebase onto master; no functional change.
> Improved description and testing steps.
>
> [PATCH v5]
>  - Warn when PN == KERNEL_PACKAGE_NAME (bug # 11905)
>  - Add KERNEL_DEPLOYSUBDIR to avoid DEPLOYDIR collisions
>
> [PATCH v6] Add KERNEL_PACKAGE_NAME to kernel-module-split.bbclass for
> module recipes; fixes lttng-modules build.
>
> [PATCH v7] Remove second definition of KERNEL_PACKAGE_NAME from
> kernel-module-split.bbclass; apply a default in two places where
> KERNEL_PACKAGE_NAME is referenced.
>
> [PATCH v8] Rebase onto current master and more fixups.
>  - kernel-devicetree.bbclass: Fixup package names
>  - depmodwrapper-cross: don't error when called from alt kernel recipes
>  - kernel.bbclass: Don't install /boot/image symlink in alt recipes
>
> https://github.com/harisokanovic/openembedded-core/tree/dev/hokanovi/multi-kernel-packages-v8
> ---
>  meta/classes/kernel-devicetree.bbclass |   8 +-
>  meta/classes/kernel-module-split.bbclass   |   9 +-
>  meta/classes/kernel.bbclass| 114 
> +
>  meta/conf/documentation.conf   |   1 +
>  .../recipes-kernel/kmod/depmodwrapper-cross_1.0.bb |  14 +--
>  meta/recipes-kernel/linux/linux-yocto.inc  |   2 +-
>  6 files changed, 90 insertions(+), 58 deletions(-)
>
> diff --git a/meta/classes/kernel-devicetree.bbclass 
> b/meta/classes/kernel-devicetree.bbclass
> index 6e08be4b70..4f80cc62eb 100644
> --- a/meta/classes/kernel-devicetree.bbclass
> +++ b/meta/classes/kernel-devicetree.bbclass
> @@ -1,10 +1,10 @@
>  # Support for device tree generation
>  PACKAGES_append = " \
> -kernel-devicetree \
> -${@['kernel-image-zimage-bundle', 
> 

[OE-core] [PATCH 2/2] tzdata: update 2017d

2017-10-25 Thread Armin Kuster
LICENSE changed to to rewording
https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a

  Briefly:
  Northern Cyprus switches from +03 to +02/+03 on 2017-10-29.
  Fiji ends DST 2018-01-14, not 2018-01-21.
  Namibia switches from +01/+02 to +02 on 2018-04-01.
  Sudan switches from +03 to +02 on 2017-11-01.
  Tonga likely switches from +13/+14 to +13 on 2017-11-05.
  Turks & Caicos switches from -04 to -05/-04 on 2018-11-04.
  A new file tzdata.zi now holds a small text copy of all data.
  The zic input format has been regularized slightly.

  Changes to future time stamps

Northern Cyprus has decided to resume EU rules starting
2017-10-29, thus reinstituting winter time.

Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously
predicted.  (Thanks to Dominic Fok.)  Adjust future predictions
accordingly.

Namibia will switch from +01 with DST to +02 all year on
2017-09-03 at 02:00.  This affects UT offsets starting 2018-04-01
at 02:00.  (Thanks to Steffen Thorsen.)

Sudan will switch from +03 to +02 on 2017-11-01.  (Thanks to Ahmed
Atyya and Yahia Abdalla.)  South Sudan is not switching, so
Africa/Juba is no longer a link to Africa/Khartoum.

Tonga has likely ended its experiment with DST, and will not
adjust its clocks on 2017-11-05.  Although Tonga has not announced
whether it will continue to observe DST, the IATA is assuming that
it will not.  (Thanks to David Wade.)

Turks & Caicos will switch from -04 all year to -05 with US DST on
2018-03-11 at 03:00.  This affects UT offsets starting 2018-11-04
at 02:00.  (Thanks to Steffen Thorsen.)

  Changes to past time stamps

Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03.
(Thanks to Arthur David Olson.)

Detroit did not observe DST in 1967.

Use railway time for Asia/Kolkata before 1941, by switching to
Madras local time (UT +052110) in 1870, then to IST (UT +0530) in
1906.  Also, treat 1941-2's +0630 as DST, like 1942-5.

Europe/Dublin's 1946 and 1947 fallback transitions occurred at
02:00 standard time, not 02:00 DST.  (Thanks to Michael Deckers.)

Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to
American time in 1892, not 1879.  (Thanks to Michael Deckers.)

Adjust the 1867 transition in Alaska to better reflect the
historical record, by changing it to occur on 1867-10-18 at 15:30
Sitka time rather than at the start of 1867-10-17 local time.
Although strictly speaking this is accurate only for Sitka,
the rest of Alaska's blanks need to be filled in somehow.

Fix off-by-one errors in UT offsets for Adak and Nome before 1867.
(Thanks to Michael Deckers.)

Add 7 s to the UT offset in Asia/Yangon before 1920.

  Changes to zone names

Remove Canada/East-Saskatchewan from the 'backward' file, as it
exceeded the 14-character limit and was an unused misnomer anyway.

Signed-off-by: Armin Kuster 
---
 meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-extended/tzdata/{tzdata_2017b.bb => tzdata_2017c.bb} (97%)

diff --git a/meta/recipes-extended/tzdata/tzdata_2017b.bb 
b/meta/recipes-extended/tzdata/tzdata_2017c.bb
similarity index 97%
rename from meta/recipes-extended/tzdata/tzdata_2017b.bb
rename to meta/recipes-extended/tzdata/tzdata_2017c.bb
index 55e8976..9e5b929 100644
--- a/meta/recipes-extended/tzdata/tzdata_2017b.bb
+++ b/meta/recipes-extended/tzdata/tzdata_2017c.bb
@@ -2,15 +2,15 @@ SUMMARY = "Timezone data"
 HOMEPAGE = "http://www.iana.org/time-zones;
 SECTION = "base"
 LICENSE = "PD & BSD & BSD-3-Clause"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ef1a352b901ee7b75a75df8171d6aca7"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
 DEPENDS = "tzcode-native"
 
 SRC_URI = 
"http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;
 UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
 
-SRC_URI[tzdata.md5sum] = "50dc0dc50c68644c1f70804f2e7a1625"
-SRC_URI[tzdata.sha256sum] = 
"f8242a522ea3496b0ce4ff4f2e75a049178da21001a08b8e666d8cbe07d18086"
+SRC_URI[tzdata.md5sum] = "1e751e7e08f8b68530674f04619d894d"
+SRC_URI[tzdata.sha256sum] = 
"d6543f92a929826318e2f44ff3a7611ce5f565a43e10250b42599d0ba4cbd90b"
 
 inherit allarch
 
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/2] tzcode-native: update to 2017d

2017-10-25 Thread Armin Kuster
LICENSE changes do to rewording

https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a

Changes to code

zic and the reference runtime now reject multiple leap seconds
within 28 days of each other, or leap seconds before the Epoch.
As a result, support for double leap seconds, which was
obsolescent and undocumented, has been removed.  Double leap
seconds were an error in the C89 standard; they have never existed
in civil timekeeping.  (Thanks to Robert Elz and Bradley White for
noticing glitches in the code that uncovered this problem.)

zic now warns about use of the obsolescent and undocumented -y
option, and about use of the obsolescent TYPE field of Rule lines.

zic now allows unambiguous abbreviations like "Sa" and "Su" for
weekdays; formerly it rejected them due to a bug.  Conversely, zic
no longer considers non-prefixes to be abbreviations; for example,
it no longer accepts "lF" as an abbreviation for "lastFriday".
Also, zic warns about the undocumented usage with a "last-"
prefix, e.g., "last-Fri".

Similarly, zic now accepts the unambiguous abbreviation "L" for
"Link" in ordinary context and for "Leap" in leap-second context.
Conversely, zic no longer accepts non-prefixes such as "La" as
abbreviations for words like "Leap".

zic no longer accepts leap second lines in ordinary input, or
ordinary lines in leap second input.  Formerly, zic sometimes
warned about this undocumented usage and handled it incorrectly.

The new macro HAVE_TZNAME governs whether the tzname external
variable is exported, instead of USG_COMPAT.  USG_COMPAT now
governs only the external variables "timezone" and "daylight".
This change is needed because the three variables are not in the
same category: although POSIX requires tzname, it specifies the
other two variables as optional.  Also, USG_COMPAT is now 1 or 0:
if not defined, the code attempts to guess it from other macros.

localtime.c and difftime.c no longer require stdio.h, and .c files
other than zic.c no longer require sys/wait.h.

zdump.c no longer assumes snprintf.  (Reported by Jonathan Leffler.)

Calculation of time_t extrema works around a bug in GCC 4.8.4
(Reported by Stan Shebs and Joseph Myers.)

zic.c no longer mistranslates formats of line numbers in non-English
locales.  (Problem reported by Benno Schulenberg.)

Several minor changes have been made to the code to make it a
bit easier to port to MS-Windows and Solaris.  (Thanks to Kees
Dekker for reporting the problems.)

  Changes to documentation and commentary

The two new files 'theory.html' and 'calendars' contain the
contents of the removed file 'Theory'.  The goal is to document
tzdb theory more accessibly.

The zic man page now documents abbreviation rules.

tz-link.htm now covers how to apply tzdata changes to clients.
(Thanks to Jorge Fábregas for the AIX link.)  It also mentions MySQL.

The leap-seconds.list URL has been updated to something that is
more reliable for tzdb.  (Thanks to Tim Parenti and Brian Inglis.)

Signed-off-by: Armin Kuster 
---
 .../tzcode/{tzcode-native_2017b.bb => tzcode-native_2017c.bb}  | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-extended/tzcode/{tzcode-native_2017b.bb => 
tzcode-native_2017c.bb} (63%)

diff --git a/meta/recipes-extended/tzcode/tzcode-native_2017b.bb 
b/meta/recipes-extended/tzcode/tzcode-native_2017c.bb
similarity index 63%
rename from meta/recipes-extended/tzcode/tzcode-native_2017b.bb
rename to meta/recipes-extended/tzcode/tzcode-native_2017c.bb
index 165d2c6..c8a987f 100644
--- a/meta/recipes-extended/tzcode/tzcode-native_2017b.bb
+++ b/meta/recipes-extended/tzcode/tzcode-native_2017c.bb
@@ -3,16 +3,16 @@
 SUMMARY = "tzcode, timezone zoneinfo utils -- zic, zdump, tzselect"
 LICENSE = "PD & BSD & BSD-3-Clause"
 
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ef1a352b901ee7b75a75df8171d6aca7"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
 SRC_URI =" 
http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode
 \

http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;
 UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
 
-SRC_URI[tzcode.md5sum] = "afaf15deb13759e8b543d86350385b16"
-SRC_URI[tzcode.sha256sum] = 
"4d1735bb54e22b8d7443d4d1f1a13d007ae11be79a35e51f8e8322fb8e292d40"
-SRC_URI[tzdata.md5sum] = "50dc0dc50c68644c1f70804f2e7a1625"
-SRC_URI[tzdata.sha256sum] = 
"f8242a522ea3496b0ce4ff4f2e75a049178da21001a08b8e666d8cbe07d18086"
+SRC_URI[tzcode.md5sum] = "2fe6986231db5182c61d565021a0cd7b"
+SRC_URI[tzcode.sha256sum] = 
"81e8b4bc23e60906640c266bbff3789661e22f0fa29fe61b96ec7c2816c079b7"
+SRC_URI[tzdata.md5sum] = "1e751e7e08f8b68530674f04619d894d"

[OE-core] ✗ patchtest: failure for Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage (rev3)

2017-10-25 Thread Patchwork
== Series Details ==

Series: Avoid a circular dependency between do_concat_dtb and 
do_assemble_fitimage (rev3)
Revision: 3
URL   : https://patchwork.openembedded.org/series/9444/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch[meta, pyro, v3] Avoid a circular dependency between 
do_concat_dtb and do_assemble_fitimage
 Issue Shortlog does not follow expected format 
[test_shortlog_format] 
  Suggested fixCommit shortlog (first line of commit message) should follow 
the format ": "



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 2/2] Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage

2017-10-25 Thread Thomas Perrot
When UBOOT_SIGN_ENABLE is active:

Dependency loop #1 found:
  do_concat_dtb (dependent Tasks ['linux-yocto_4.10.bb:do_assemble_fitimage'])
  do_install (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot', 
'u-boot_2017.01.bb:do_compile', 'u-boot_2017.01.bb:do_concat_dtb'])
  do_deploy (dependent Tasks ['u-boot_2017.01.bb:do_deploy_dtb', 
'u-boot_2017.01.bb:do_install'])
  do_assemble_fitimage (dependent Tasks ['linux-yocto_4.10.bb:do_compile', 
'u-boot_2017.01.bb:do_deploy'])

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass |  2 +-
 meta/classes/uboot-sign.bbclass  | 21 +
 2 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 0789ba611f..13d61a2298 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -33,7 +33,7 @@ python __anonymous () {
 # the fitImage:
 if d.getVar('UBOOT_SIGN_ENABLE') == "1":
 uboot_pn = d.getVar('PREFERRED_PROVIDER_u-boot') or 'u-boot'
-d.appendVarFlag('do_assemble_fitimage', 'depends', ' %s:do_deploy' 
% uboot_pn)
+d.appendVarFlag('do_assemble_fitimage', 'depends', ' 
%s:do_deploy_dtb' % uboot_pn)
 }
 
 # Options for the device tree compiler passed to mkimage '-D' feature:
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 8ee904e7df..2f616bf2a9 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -47,16 +47,14 @@ do_deploy_dtb () {
cd ${DEPLOYDIR}
 
if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
-   install ${B}/${UBOOT_DTB_BINARY} ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
-   rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
+   install ${B}/${UBOOT_DTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_BINARY}
fi
if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
-   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
-   rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
+   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_BINARY}
fi
 }
 
@@ -70,11 +68,10 @@ do_concat_dtb () {
oe_runmake EXT_DTB=${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
install ${B}/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
install ${B}/${UBOOT_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_IMAGE}
-   elif [ -e "${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOYDIR}/${UBOOT_DTB_IMAGE}" ]; then
-   cd ${DEPLOYDIR}
-   cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} | tee 
${B}/${UBOOT_BINARY} > ${UBOOT_IMAGE}
+   elif [ -e "${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}" ]; then
+   cat ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} | tee ${B}/${UBOOT_BINARY} > 
${UBOOT_IMAGE}
else
-   bbwarn "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
+   bbfatal "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
fi
fi
 }
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta][PATCH 1/2] Fix some issues in the fitImage generation

2017-10-25 Thread Thomas Perrot
- Bad image type replacement for aarch64
- Fix DTB path in fitimage.its
- Ignore fitImage type in do_bundle_initramfs task because the packaging is 
made by do_assemble_fitimage_initramfs
- the images for arm64 are not compressed the linux_comp variable must 
therefore be none

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass |  7 +--
 meta/classes/kernel-uboot.bbclass| 11 ---
 meta/classes/kernel.bbclass  |  4 +++-
 3 files changed, 16 insertions(+), 6 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 179185b6b2..0789ba611f 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -7,10 +7,13 @@ python __anonymous () {
 depends = "%s u-boot-mkimage-native dtc-native" % depends
 d.setVar("DEPENDS", depends)
 
-if d.getVar("UBOOT_ARCH") == "mips":
+uarch = d.getVar("UBOOT_ARCH")
+if uarch == "mips":
 replacementtype = "vmlinuz.bin"
-elif d.getVar("UBOOT_ARCH") == "x86":
+elif uarch == "x86":
 replacementtype = "bzImage"
+elif uarch == "arm64":
+replacementtype = "Image"
 else:
 replacementtype = "zImage"
 
diff --git a/meta/classes/kernel-uboot.bbclass 
b/meta/classes/kernel-uboot.bbclass
index 87f02654fa..06d293039a 100644
--- a/meta/classes/kernel-uboot.bbclass
+++ b/meta/classes/kernel-uboot.bbclass
@@ -1,5 +1,5 @@
 uboot_prep_kimage() {
-   if [ -e arch/${ARCH}/boot/compressed/vmlinux ]; then
+   if [ -e arch/${ARCH}/boot/compressed/vmlinux ] ; then
vmlinux_path="arch/${ARCH}/boot/compressed/vmlinux"
linux_suffix=""
linux_comp="none"
@@ -11,8 +11,13 @@ uboot_prep_kimage() {
linux_comp="none"
else
vmlinux_path="vmlinux"
-   linux_suffix=".gz"
-   linux_comp="gzip"
+   if [ "${ARCH}" = "arm64" ] ; then
+   linux_suffix=""
+   linux_comp="none"
+   else
+   linux_suffix=".gz"
+   linux_comp="gzip"
+   fi
fi
 
[ -n "${vmlinux_path}" ] && ${OBJCOPY} -O binary -R .note -R .comment 
-S "${vmlinux_path}" linux.bin
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 756707a3c2..7f8c8985f3 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -208,7 +208,9 @@ do_bundle_initramfs () {
# Backing up kernel image relies on its type(regular file or 
symbolic link)
tmp_path=""
for type in ${KERNEL_IMAGETYPES} ; do
-   if [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
+   if [ "$type" = "fitImage" ] ; then
+   continue
+   elif [ -h ${KERNEL_OUTPUT_DIR}/$type ] ; then
linkpath=`readlink -n 
${KERNEL_OUTPUT_DIR}/$type`
realpath=`readlink -fn 
${KERNEL_OUTPUT_DIR}/$type`
mv -f $realpath $realpath.bak
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [meta][pyro][PATCHv2] Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage

2017-10-25 Thread Thomas PERROT
Hi,

It is an issue with the fitImage generation when UBOOT_SIGN_ENABLE is
enabled, unrelated to extlinux.

I just update the commit message and push a v3 of this patch.

Best regards,
Thomas P.



On Tue, Oct 24, 2017 at 10:08 AM, André Draszik  wrote:

> Hi,
>
> On Mon, 2017-10-23 at 18:23 +0200, Thomas Perrot wrote:
> > Signed-off-by: Thomas Perrot 
>
> Your commit message doesn't explain what problem you're trying to solve.
>
> I can only guess that it's the same as this:
> http://lists.openembedded.org/pipermail/openembedded-core/
> 2017-September/142619.html
> http://lists.openembedded.org/pipermail/openembedded-core/
> 2017-September/142621.html
>
> ? If so, just submit requests for backporting, or explain why this doesn't
> work in pyro.
>
>
> > ---
> >  meta/classes/kernel-fitimage.bbclass |  2 +-
> >  meta/classes/uboot-sign.bbclass  | 21 +
> >  2 files changed, 10 insertions(+), 13 deletions(-)
> >
> > diff --git a/meta/classes/kernel-fitimage.bbclass b/meta/classes/kernel-
> > fitimage.bbclass
> > index abbc309b09..5ad439e82d 100644
> > --- a/meta/classes/kernel-fitimage.bbclass
> > +++ b/meta/classes/kernel-fitimage.bbclass
> > @@ -31,7 +31,7 @@ python __anonymous () {
> >  # the fitImage:
> >  if d.getVar('UBOOT_SIGN_ENABLE') == "1":
> >  uboot_pn = d.getVar('PREFERRED_PROVIDER_u-boot') or
> 'u-boot'
> > -d.appendVarFlag('do_assemble_fitimage', 'depends', '
> > %s:do_deploy' % uboot_pn)
> > +d.appendVarFlag('do_assemble_fitimage', 'depends', '
> > %s:do_deploy_dtb' % uboot_pn)
>
> You should also update the description of the executed tasks at the top of
> uboot-sign.bbclass if you're changing this.
>
> Cheers,
> Andre'
>
>
> >  }
> >
> >  # Options for the device tree compiler passed to mkimage '-D' feature:
> > diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-
> > sign.bbclass
> > index 8ee904e7df..2f616bf2a9 100644
> > --- a/meta/classes/uboot-sign.bbclass
> > +++ b/meta/classes/uboot-sign.bbclass
> > @@ -47,16 +47,14 @@ do_deploy_dtb () {
> >   cd ${DEPLOYDIR}
> >
> >   if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
> > - install ${B}/${UBOOT_DTB_BINARY}
> > ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
> > - rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
> > - ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
> > - ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
> > + install ${B}/${UBOOT_DTB_BINARY}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
> > + ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_SYMLINK}
> > + ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_BINARY}
> >   fi
> >   if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
> > - install ${B}/${UBOOT_NODTB_BINARY}
> > ${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
> > - rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
> > - ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
> > - ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
> > + install ${B}/${UBOOT_NODTB_BINARY}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
> > + ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_SYMLINK}
> > + ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_BINARY}
> >   fi
> >  }
> >
> > @@ -70,11 +68,10 @@ do_concat_dtb () {
> >   oe_runmake
> > EXT_DTB=${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
> >   install ${B}/${UBOOT_BINARY}
> > ${DEPLOYDIR}/${UBOOT_IMAGE}
> >   install ${B}/${UBOOT_BINARY}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_IMAGE}
> > - elif [ -e "${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}" -a -e
> > "${DEPLOYDIR}/${UBOOT_DTB_IMAGE}" ]; then
> > - cd ${DEPLOYDIR}
> > - cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} | tee
> > ${B}/${UBOOT_BINARY} > ${UBOOT_IMAGE}
> > + elif [ -e "${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}" -a
> > -e "${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}" ]; then
> > + cat ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
> > ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} | tee ${B}/${UBOOT_BINARY} >
> > ${UBOOT_IMAGE}
> >   else
> > - bbwarn "Failure while adding public key to u-boot
> > binary. Verified boot won't be available."
> > + bbfatal "Failure while adding public key to u-
> > boot binary. Verified boot won't be available."
> >   fi
> >   fi
> >  }
> > --
> > 2.13.6
> >
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list

[OE-core] [meta][pyro][PATCHv3] Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage

2017-10-25 Thread Thomas Perrot
When UBOOT_SIGN_ENABLE is active:

Dependency loop #1 found:
  do_concat_dtb (dependent Tasks ['linux-yocto_4.10.bb:do_assemble_fitimage'])
  do_install (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot', 
'u-boot_2017.01.bb:do_compile', 'u-boot_2017.01.bb:do_concat_dtb'])
  do_deploy (dependent Tasks ['u-boot_2017.01.bb:do_deploy_dtb', 
'u-boot_2017.01.bb:do_install'])
  do_assemble_fitimage (dependent Tasks ['linux-yocto_4.10.bb:do_compile', 
'u-boot_2017.01.bb:do_deploy'])

Signed-off-by: Thomas Perrot 
---
 meta/classes/kernel-fitimage.bbclass |  2 +-
 meta/classes/uboot-sign.bbclass  | 21 +
 2 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index abbc309b09..5ad439e82d 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -31,7 +31,7 @@ python __anonymous () {
 # the fitImage:
 if d.getVar('UBOOT_SIGN_ENABLE') == "1":
 uboot_pn = d.getVar('PREFERRED_PROVIDER_u-boot') or 'u-boot'
-d.appendVarFlag('do_assemble_fitimage', 'depends', ' %s:do_deploy' 
% uboot_pn)
+d.appendVarFlag('do_assemble_fitimage', 'depends', ' 
%s:do_deploy_dtb' % uboot_pn)
 }
 
 # Options for the device tree compiler passed to mkimage '-D' feature:
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 8ee904e7df..2f616bf2a9 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -47,16 +47,14 @@ do_deploy_dtb () {
cd ${DEPLOYDIR}
 
if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
-   install ${B}/${UBOOT_DTB_BINARY} ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
-   rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
-   ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
+   install ${B}/${UBOOT_DTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_BINARY}
fi
if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
-   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
-   rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
-   ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
+   install ${B}/${UBOOT_NODTB_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_SYMLINK}
+   ln -sf ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_BINARY}
fi
 }
 
@@ -70,11 +68,10 @@ do_concat_dtb () {
oe_runmake EXT_DTB=${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
install ${B}/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
install ${B}/${UBOOT_BINARY} 
${DEPLOY_DIR_IMAGE}/${UBOOT_IMAGE}
-   elif [ -e "${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOYDIR}/${UBOOT_DTB_IMAGE}" ]; then
-   cd ${DEPLOYDIR}
-   cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} | tee 
${B}/${UBOOT_BINARY} > ${UBOOT_IMAGE}
+   elif [ -e "${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE}" -a -e 
"${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}" ]; then
+   cat ${DEPLOY_DIR_IMAGE}/${UBOOT_NODTB_IMAGE} 
${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE} | tee ${B}/${UBOOT_BINARY} > 
${UBOOT_IMAGE}
else
-   bbwarn "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
+   bbfatal "Failure while adding public key to u-boot 
binary. Verified boot won't be available."
fi
fi
 }
-- 
2.13.6

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core