[OE-core] [PATCH v4 7/7] wic: selftest: add tests for --fixed-size partition flags

wic has a new flag for setting a fixed parition size --fixed-size. Add tests that verify if partition is indeed sized properly and that errors are signaled when there is not enough space to fit partition data. Signed-off-by: Maciej Borzecki ---

[OE-core] [PATCH v4 2/7] oeqa/utils/commands.py: allow use of binaries from native sysroot

Tests may need to run a native tool that is not available on the host filesystem, but can be built using one of the *-native recipes. In such case, the tool will be available in native sysroot, and running in from that location will require adjustments to PATH. runCmd() can now take a path to

[OE-core] [PATCH v4 6/7] wic: selftest: do not assume bzImage kernel image

Instead of assuming that bzImage is available, query bitbake enviroment for KERNEL_IMAGETYPE. Signed-off-by: Maciej Borzecki --- meta/lib/oeqa/selftest/wic.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/wic.py

[OE-core] [PATCH v4 3/7] wic: add --fixed-size wks option

Added new option --fixed-size to wks. The option can be used to indicate the exact size of a partition. The option cannot be added together with --size, in which case an error will be raised. Other options that influence automatic partition size (--extra-space, --overhead-factor), if specifiec

[OE-core] [PATCH v4 4/7] wic: selftest: avoid COMPATIBLE_HOST issues

wic tests will unconditionally attempt to build syslinux and add configuration options that may not be compatible with current machine. Resolve this by consulting HOST_ARCH (which defaults to TARGET_ARCH) and build recipes, add configuration options or skip tests conditionally. A convenience

[OE-core] [PATCH v4 5/7] wic: selftest: do not repeat core-image-minimal

Replace repeated core-image-minimal with Wic class field. Signed-off-by: Maciej Borzecki --- meta/lib/oeqa/selftest/wic.py | 111 +++--- 1 file changed, 73 insertions(+), 38 deletions(-) diff --git a/meta/lib/oeqa/selftest/wic.py

[OE-core] [PATCH v4 1/7] oe-selftest: enforce en_US.UTF-8 locale

Replicate bitbake and eforce en_US.UTF-8 locale so that ouptut of locale-aware tools remains stable. Signed-off-by: Maciej Birzecki Signed-off-by: Maciej Borzecki --- scripts/oe-selftest | 3 +++ 1 file changed, 3 insertions(+) diff

[OE-core] [PATCH v4 0/7] wic: bugfixes & --fixed-size support, tests, oe-selftest: minor fixes

v4 of patch series previously posted here [1]. Some of the patches that were posted as part of v3 are already in master. This version contains only the patches that were not merged yet. Changes since v3: * Running wic tests on Ubuntu resulted in test_fixed_size to fail. The reason was that

Re: [OE-core] Contents of non-rootfs partitions

> On Nov 22, 2016, at 11:13 PM, Kristian Amlie wrote: > > On 23/11/16 00:45, Khem Raj wrote: >> On 11/22/16 1:05 AM, Kristian Amlie wrote: >>> Hey >>> >>> In Mender we are using a dual rootfs partition layout (A/B layout) with a >>> persistent data partition on the

Re: [OE-core] Contents of non-rootfs partitions

On 23/11/16 00:45, Khem Raj wrote: > On 11/22/16 1:05 AM, Kristian Amlie wrote: >> Hey >> >> In Mender we are using a dual rootfs partition layout (A/B layout) with a >> persistent data partition on the side. We're using wic to do the actual >> image building. >> >> However, putting files into

Re: [OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

> On Nov 22, 2016, at 10:49 PM, Yuanjie Huang > wrote: > > > On 11/23/2016 11:38 AM, Khem Raj wrote: >> are they regenerating code during configure ? > No, code is generated during compilation. Corresponding c files are not > included in git repo, so these files

Re: [OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

On 11/23/2016 11:38 AM, Khem Raj wrote: are they regenerating code during configure ? No, code is generated during compilation. Corresponding c files are not included in git repo, so these files are always compiled from flex/bison source files. On Nov 22, 2016, at 7:22 PM, Yuanjie Huang

Re: [OE-core] [PATCH] kernel-fitimage.bbclass: Check value of UBOOT_SIGN_ENABLE

Just pinging these patches, to see if there were any issues or comments. I realize I sent them just before a release so it was very likely they would get lost in the noise. Thanks, Nathan On 21 October 2016 at 22:07, Nathan Rossi wrote: > Check the value of

Re: [OE-core] [PATCH] kernel-fitimage.bbclass: Allow unset load/entry addresses for ramdisks

Just pinging these patches, to see if there were any issues or comments. I realize I sent them just before a release so it was very likely they would get lost in the noise. Thanks, Nathan On 21 October 2016 at 22:07, Nathan Rossi wrote: > Allow the load and entry

Re: [OE-core] [PATCH] kernel-fitimage.bbclass: Don't assume KERNEL_IMAGETYPE == fitImage

Just pinging these patches, to see if there were any issues or comments. I realize I sent them just before a release so it was very likely they would get lost in the noise. Thanks, Nathan On 21 October 2016 at 22:07, Nathan Rossi wrote: > The name of the output image for

Re: [OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

are they regenerating code during configure ? > On Nov 22, 2016, at 7:22 PM, Yuanjie Huang > wrote: > > Hi Raj, > > We observed gdb/ada-lex.l is processed by flex while gdb/c-exp.y, > gdb/f-exp.y, gdb/go-exp.y and many others are handled by bison. Basically, >

Re: [OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

Hi Raj, We observed gdb/ada-lex.l is processed by flex while gdb/c-exp.y, gdb/f-exp.y, gdb/go-exp.y and many others are handled by bison. Basically, all language-specific codes in gdb are generated. Best, Yuanjie On 11/23/2016 11:05 AM, Khem Raj wrote: On Nov 22, 2016, at 6:00 PM, Yuanjie

[OE-core] [PATCH 1/1] grub/grub-efi: fix conflict

While installing grub and grub-efi, there are conflict files in ${sysconfdir} ${datadir} ${bindir} ${sbindir}. Debian use a common package grub-common for both of pc bios and efi, and use package grub-pc-bin for pc bios, grub-efi-amd64-bin for efi. Both of grub-pc-bin and grub-efi-amd64-bin

[OE-core] [PATCH 0/1] grub/grub-efi: fix conflict

The following changes since commit 43e652f3d1fee5ce7fad67e6400315eab1b34270: devtool: add "rename" subcommand (2016-11-07 11:04:22 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib hongxu/fix-grub

Re: [OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

> On Nov 22, 2016, at 6:00 PM, Yuanjie Huang > wrote: > > From: Yuanjie Huang > > Some source code of gdb is generated with flex or bison. Make both > dependencies, to avoid compilation failure on host without them. can you find out

[OE-core] [PATCH 1/1] gdb-cross: depends on flex-native and bison-native

From: Yuanjie Huang Some source code of gdb is generated with flex or bison. Make both dependencies, to avoid compilation failure on host without them. Signed-off-by: Yuanjie Huang --- meta/recipes-devtools/gdb/gdb-cross.inc | 2 +- 1

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

On 11/22/2016 03:36 PM, Khem Raj wrote: On 11/22/16 3:08 PM, Manjukumar Harthikote Matha wrote: Hi Khem, On 11/22/2016 02:03 PM, Khem Raj wrote: This is ok for master Is there a particular reason not have in Morty? We have arm-trusted-firmware failing to build due to this issue. I have

Re: [OE-core] Contents of non-rootfs partitions

On 11/22/16 1:05 AM, Kristian Amlie wrote: > Hey > > In Mender we are using a dual rootfs partition layout (A/B layout) with a > persistent data partition on the side. We're using wic to do the actual image > building. > > However, putting files into this data partition is not a

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

On 11/22/16 3:08 PM, Manjukumar Harthikote Matha wrote: > Hi Khem, > > On 11/22/2016 02:03 PM, Khem Raj wrote: >> This is ok for master > Is there a particular reason not have in Morty? We have arm-trusted-firmware > failing to build due to this issue. I have submitted a patch to master as well

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

Hi Khem, On 11/22/2016 02:03 PM, Khem Raj wrote: This is ok for master Is there a particular reason not have in Morty? We have arm-trusted-firmware failing to build due to this issue. I have submitted a patch to master as well Thanks Manju On Nov 22, 2016 1:31 PM, "Manjukumar Matha"

Re: [OE-core] [PATCH] module.bbclass: allow to override location of Module.symvers

On Mon, Nov 21, 2016 at 09:37:13AM +, André Draszik wrote: > From: André Draszik > > Requiring all build systems for external kernel modules to > place Module.symvers directly into ${B}/. is quite an > artificial assumption/requirement. It doesn't have to end > up

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

This is ok for master On Nov 22, 2016 1:31 PM, "Manjukumar Matha" < manjukumar.harthikote-ma...@xilinx.com> wrote: > There was bug with alignment frags for aarch64 in binutils. This is > fixed in master of binutils. This patch backports the fix to binutils > 2.27 version. > > Signed-off-by:

[OE-core] [PATCH] binutils-2.27.inc: Fix alignment frags for aarch64

There was bug with alignment frags for aarch64 in binutils. This is fixed in master of binutils. This patch backports the fix to binutils 2.27 version. Signed-off-by: Manjukumar Matha Signed-off-by: Nathan Rossi ---

Re: [OE-core] [PATCH v3 09/11] wic: selftest: add tests for --fixed-size partition flags

On Tue, Nov 22, 2016 at 4:02 PM, Maciej Borzęcki wrote: > On Tue, Nov 22, 2016 at 3:47 PM, Burton, Ross wrote: >> >> On 15 November 2016 at 09:52, Maciej Borzecki >> wrote: >>> >>> wic has a new flag for setting a

[OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

There was bug with alignment frags for aarch64 in binutils. This is fixed in master of binutils. This patch backports the fix to binutils 2.27 version. Signed-off-by: Manjukumar Matha Signed-off-by: Nathan Rossi ---

Re: [OE-core] [PATCH] sanity: removed broken compiler check

On Tue, Nov 22, 2016 at 4:16 AM, Enrico Scholz wrote: > "Burton, Ross" writes: > >>> Is this check really so useful? gcc + g++ are elementary tools which can >>> be expected. >> >> But they're not if BUILD_CC is overridden. For example if

Re: [OE-core] [PATCHv2] apt-package: Include maintenance scripts

On 11/21/2016 02:57 PM, Linus Wallgren wrote: > Apt can run multiple tasks daily, such as for example clean, update, > autoclean, unattended-upgrades etc. > > [YOCTO #10669] > > Signed-off-by: Linus Wallgren Acked-by: Aníbal Limón >

[OE-core] [PATCH] libpcap: Disable exposed bits of WinPCAP remote capture support

Disable bits of remote capture support inherited from the WinPCAP merge which cause applications to fails to build if they define HAVE_REMOTE. Signed-off-by: Fabio Berton --- .../libpcap/libpcap/disable-remote.patch | 36 ++

[OE-core] [PATCH][morty 2/2] Revert "epiphany: remove unnecessary libwnck3 dependency"

This version of epiphany still needs libwnck3. This reverts commit fb5c4f181176710a4cfb3c875b5edb4e5aa5df73. Signed-off-by: Ross Burton --- meta/recipes-gnome/epiphany/epiphany_3.20.3.bb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCH][morty 1/2] Revert "libwnck3: remove the recipe"

The epiphany in morty still needs libwnck3, so bring it back. This reverts commit 129281e8557ec8d29ecf863675884713a3050f4b. Signed-off-by: Ross Burton --- meta/recipes-gnome/libwnck/libwnck3_3.20.1.bb | 19 +++ 1 file changed, 19 insertions(+) create

[OE-core] [PATCH 1/1] scripst/runqemu: Allow to use qemu from host.

From: Mariano Lopez This will add support to use qemu from the running host, with this is possible to put qemu-native in ASSUME_PROVIDED variable. By default it will try to get qemu from the build sysroot, and only if it fails will try to use the host's qemu.

Re: [OE-core] Loss of a wayland socket by a systemd user session

Hi Daniel, On Fri, 18 Nov 2016 20:47:05 -0600 Daniel Díaz wrote: > Hello! > > > On 11/18/2016 12:12 PM, Tomas Novotny wrote: > > I'm using weston and its 'weston-start' script shipped with oe-core (morty). > > It works perfectly until root is logged in. The problematic

Re: [OE-core] [PATCH 7/7] kern-tools: error checking and tree generation fixes

On 2016-11-22 11:53 AM, akuster808 wrote: Bruce, On 11/22/2016 07:59 AM, Bruce Ashfield wrote: During processing of the kernel meta data the kern tools were not properly exiting on syntax errors or invalid commands. Does Morty need this? It won't do any harm, if you also pick up my kernel

Re: [OE-core] [PATCH 7/7] kern-tools: error checking and tree generation fixes

Bruce, On 11/22/2016 07:59 AM, Bruce Ashfield wrote: During processing of the kernel meta data the kern tools were not properly exiting on syntax errors or invalid commands. Does Morty need this? -Armin Noticing and debugging these issues wasn't trivial. To make this easier, we now trap

[OE-core] [PATCH 1/1] nfs-utils: 1.3.3 -> 1.3.4

From: Mariano Lopez Signed-off-by: Mariano Lopez --- .../files/nfs-utils-debianize-start-statd.patch| 23 +++-- ...tatd-fix-a-segfault-caused-by-improper-us.patch | 113 - .../{nfs-utils_1.3.3.bb =>

Re: [OE-core] [PATCH 2/5] taglib: Update to 1.11.1

HAVE_BOOST_BYTESWAP is infact the right fix if we want to disable boost byteswap. It will then fall back to finding them in compiler which should be ok for OE since we have new enough compiler. Thanks for helping out here. On Tue, Nov 22, 2016 at 3:20 AM, Burton, Ross

Re: [OE-core] distro checking and lsb_release

On 22/11/16 15:32, Burton, Ross wrote: > > On 22 November 2016 at 15:11, Jack Mitchell >wrote: > > >distro_id = distro_data['DISTRIB_ID'] > release = distro_data['DISTRIB_RELEASE'] > TypeError: 'NoneType' object is not

[OE-core] [PATCH 0/7] linux-yocto: consolidated pull request

Hi all, I sent some of these previously, but I kept them in this pull request since the changes are all incremental. New in this pull request are 4.8.10 and the introduction of 4.9-rcX as the linux-yocto-dev kernel. Bruce The following changes since commit

[OE-core] [PATCH 4/7] linux-yocto/4.4: update to v4.4.32

Updating from v4.4.30 -> v4.4.32. The shortlog summary of the changes follows: 4dab3e4df994 Linux 4.4.32 ae94da4c53b7 scsi: megaraid_sas: fix macro MEGASAS_IS_LOGICAL to avoid regression 2be0548e64f1 drm/radeon: fix DP mode validation ccc31f819918 drm/radeon/dp: add back special

[OE-core] [PATCH 7/7] kern-tools: error checking and tree generation fixes

During processing of the kernel meta data the kern tools were not properly exiting on syntax errors or invalid commands. Noticing and debugging these issues wasn't trivial. To make this easier, we now trap the error and dump the offending meta-data for the user to see. There was also an issue

[OE-core] [PATCH 6/7] linux-yocto-dev: update to 4.9-rcX

Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb index

[OE-core] [PATCH 5/7] linux-yocto/4.8: update to v4.8.10

Integrating the 4.8.9 and 4.8.10 -stable updates. The commit log is as follows: cf5ae2989a32 Linux 4.8.10 5cd8f6788ff3 usb: gadget: f_fs: stop sleeping in ffs_func_eps_disable e2458382c792 usb: gadget: f_fs: edit epfile->ep under lock e34a0f1c53b5 sparc64: Delete now unused user copy

[OE-core] [PATCH 3/7] linux-yocto/4.8: update from v4.8.6 -> v4.8.8

Updating to the korg -stable release 4.8.8. The short log change summary follows: 61385cc1db42 Linux 4.8.8 8ed841d6c045 scsi: megaraid_sas: fix macro MEGASAS_IS_LOGICAL to avoid regression 32f60e9b621f scsi: megaraid_sas: Fix data integrity failure for JBOD (passthrough) devices

[OE-core] [PATCH 1/7] linux-yocto/4.8: fix cryptodev compilation error

It was reported that compilation was broken for the in tree variant of cryptodev. This commit integrates two patches that fix the issue: efbdfa1ed95f cryptodev: stomp dynamic version numbering for in tree builds 32f54070205f cryptodev: fix compile error when enable CONFIG_CRYPTODEV

[OE-core] [PATCH 2/7] linux-yocto/4.8: update to v4.8.6-rt5

Paul Gortmaker sent along updates to the latest 4.8 -rt version. Updating the SRCREVs to include the following commits: f83a3d4a643b v4.8.6-rt5 74c7ffc2e3f2 NFSv4: don't disable preemption on !RT 9711dc408890 kbuild: Add -fno-pie to KBUILD_AFLAGS: 7b4d4278e307 v4.8.6-rt4

Re: [OE-core] distro checking and lsb_release

On 22 November 2016 at 15:11, Jack Mitchell wrote: > >distro_id = distro_data['DISTRIB_ID'] > release = distro_data['DISTRIB_RELEASE'] > TypeError: 'NoneType' object is not subscriptable > You're using arch which doesn't set those fields. There's a patch on

Re: [OE-core] distro checking and lsb_release

On 22/11/16 14:25, Burton, Ross wrote: > > On 22 November 2016 at 14:07, Jack Mitchell >wrote: > > With the recent changes to distro checking the lsb_release binary > is now > required. I tried adding this to SANITY_REQUIRED_UTILITIES

Re: [OE-core] [PATCH v3 09/11] wic: selftest: add tests for --fixed-size partition flags

On Tue, Nov 22, 2016 at 3:47 PM, Burton, Ross wrote: > > On 15 November 2016 at 09:52, Maciej Borzecki > wrote: >> >> wic has a new flag for setting a fixed parition size --fixed-size. Add >> tests that verify if partition is indeed sized

Re: [OE-core] [PATCH v3 09/11] wic: selftest: add tests for --fixed-size partition flags

On 15 November 2016 at 09:52, Maciej Borzecki wrote: > wic has a new flag for setting a fixed parition size --fixed-size. Add > tests that verify if partition is indeed sized properly and that errors > are signaled when there is not enough space to fit partition data.

Re: [OE-core] distro checking and lsb_release

On 22 November 2016 at 14:07, Jack Mitchell wrote: > With the recent changes to distro checking the lsb_release binary is now > required. I tried adding this to SANITY_REQUIRED_UTILITIES however it > seems as though the distro check is done before the SanityEvent is >

[OE-core] distro checking and lsb_release

With the recent changes to distro checking the lsb_release binary is now required. I tried adding this to SANITY_REQUIRED_UTILITIES however it seems as though the distro check is done before the SanityEvent is triggered. Where would be the best place to check this binary is available to prevent an

Re: [OE-core] [PATCH] sanity: removed broken compiler check

"Burton, Ross" writes: >> Is this check really so useful? gcc + g++ are elementary tools which can >> be expected. > > But they're not if BUILD_CC is overridden. For example if the host gcc is > actually too old/new for OE to work and BUILD_CC has been set to point at a >

Re: [OE-core] [PATCH] sanity: removed broken compiler check

On 22 November 2016 at 12:01, Enrico Scholz wrote: > Is this check really so useful? gcc + g++ are elementary tools which can > be expected. > But they're not if BUILD_CC is overridden. For example if the host gcc is actually too old/new for OE to work and

Re: [OE-core] [PATCH] sanity: removed broken compiler check

"Burton, Ross" writes: >> Is there a reason check_app_exists() wasn’t fixed to handle symlinks >> instead? > > Agreed, the check should handle splitting the argument and links, instead > of removing a key sanity check. Is this check really so useful? gcc + g++ are

Re: [OE-core] Contents of non-rootfs partitions

On 22/11/16 12:10, Patrick Ohly wrote: >> ... > > All of these introduce some special mechanism. Let me propose something > that might integrate better with the existing tooling: > > The "rootfs" directory gets redefined as representing the entire virtual > file system. When creating a disk

Re: [OE-core] [PATCH] sanity: removed broken compiler check

On 22 November 2016 at 03:22, Christopher Larson wrote: > Is there a reason check_app_exists() wasn’t fixed to handle symlinks > instead? > Agreed, the check should handle splitting the argument and links, instead of removing a key sanity check. Ross --

Re: [OE-core] [PATCH 2/5] taglib: Update to 1.11.1

On 22 November 2016 at 10:44, Burton, Ross wrote: > No but I've an example where boost doesnt build at all and this breaks > core-image-sato (IA x32)... > > Building all of boost just for a macro seems rather unfortunate. > Found the magic -D options to convince taglib

[OE-core] [PATCH] taglib: Update to 1.11.1

Forcibly disable Boost as the macros it looks for are also present in our C++ standard library. Enable c++11 in cmake as well as in CXXFLAGS [Khem Raj] CXXFLAGS is required due to a cmake bug where it does not honor CMAKE_CXX_FLAGS during configure time checks [Khem Raj] Signed-off-by: Ross

Re: [OE-core] [PATCH] sanity: removed broken compiler check

Christopher Larson writes: >> |Please install the following missing utilities: C Compiler (ccache gcc >> ),C++ Compiler (ccache g++ ) >> >> Remove this check for now. >> [...] >> +++ b/meta/classes/sanity.bbclass >> [...] >> -if not check_app_exists('${BUILD_CC}',

Re: [OE-core] Contents of non-rootfs partitions

On Tue, 2016-11-22 at 10:05 +0100, Kristian Amlie wrote: > Hey > > In Mender we are using a dual rootfs partition layout (A/B layout) > with a persistent data partition on the side. We're using wic to do > the actual image building. > > However, putting files into this data partition is not a >

Re: [OE-core] [PATCH 2/5] taglib: Update to 1.11.1

On 22 November 2016 at 03:46, Khem Raj wrote: > its a build time dependency. Do we have a usecase/images where taglib is > used > and boost is just pulled into build because of taglib ? > No but I've an example where boost doesnt build at all and this breaks core-image-sato

[OE-core] [PATCH 4/4] package.bbclass: support persistent /var/log

Add a new file, fs-perms-persistent-log.txt, which treats /var/log as a directory instead of a link. Modify package.bbclass to use this file if VOLATILE_LOG_DIR is not set to "yes". [YOCTO #6132] Signed-off-by: Chen Qi --- meta/classes/package.bbclass | 2 +-

[OE-core] [PATCH 1/4] bitbake.conf: add VOLATILE_LOG_DIR variable

The default value is "yes" which results in the /var/log being a link pointing to /var/volatile/log which is on tmpfs. The user could override this value to "no" which causes /var/log to be a directory on persistent storage. [YOCTO #6132] Signed-off-by: Chen Qi ---

[OE-core] [PATCH 0/4] Persistent /var/log support

The following changes since commit a675b2c89e477af088faee9b3be96eae19a85f0b: sanity.bbclass: fix logging of an error (2016-11-15 15:18:50 +) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib ChenQi/persistent-var-log

[OE-core] [PATCH 3/4] initscripts: support persistent /var/log

Respect VOLATILE_VAR_LOG variable so that if it's set to "no", we could have persistent /var/log on the final image. [YOCTO #6132] Signed-off-by: Chen Qi --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 1 - meta/recipes-core/initscripts/initscripts_1.0.bb

[OE-core] [PATCH 2/4] base-files: respect VOLATILE_LOG_DIR

Respect VOLATILE_LOG_DIR variable. In this way, if the user overrides this variable to be "no", /var/log on the final image would reside on persistent storage. [YOCTO #6132] Signed-off-by: Chen Qi --- meta/recipes-core/base-files/base-files_3.0.14.bb | 4 ++-- 1 file

Re: [OE-core] Contents of non-rootfs partitions

On 22/11/16 10:27, Yann Dirson wrote: > Since usually such a data partition needs to be written at times, you'll > anyway have to handle the event of it getting corrupted, and possibly have to > reformat it. > With this in mind, one option is to include default contents in your rootfs, > and

[OE-core] [PATCH] grub-efi: Force no-pie build

PIE is enabled by default on the latest Debian LD. Disable it for grub-efi. Otherwise: | /usr/bin/ld: -r and -pie may not be used together | collect2: error: ld returned 1 exit status | Makefile:61382: recipe for target 'trig.module' failed | make[3]: *** [trig.module] Error 1 Signed-off-by:

[OE-core] Contents of non-rootfs partitions

Hey In Mender we are using a dual rootfs partition layout (A/B layout) with a persistent data partition on the side. We're using wic to do the actual image building. However, putting files into this data partition is not a straightforward operation ATM. All recipes in OE put files into the