openembedded-core.git/meta/classes, branch master-next-1.9

image_types: Add missing ext4 support

2015-03-31T21:38:50+00:00

This is particularly problematic since qemu images switched to ext4 by
default and now cannot work properly with UIs like hob.

This patch adds in ext4 to the appropriate IMAGE* variables fixing this.

[YOCTO #7426]

Signed-off-by: Richard Purdie

insane: Add baremetal mappings to the QA arch test

2015-03-31T21:27:52+00:00

Add mappings for i586-elf, x86_64-elf and arm-eabi to binary lookup
table which allows for a variety of baremetal toolchain generation.

Signed-off-by: Richard Purdie

siteinfo: Add x86_64-elf support

2015-03-31T21:27:51+00:00

Teach siteinfo about x86_64-elf so that baremetal toolchains parse/build.

Signed-off-by: Richard Purdie

populate_sdk_ext: Log the "Preparing build system" step

2015-03-31T15:28:25+00:00

When using bitbake to do the setscene as part of sdk setup, it would be
useful to have a log in the case where it fails.

The log is called preparing_build_system.log and is in the top level
directory of the extracted sdk.

Signed-off-by: Randy Witt 
Signed-off-by: Richard Purdie

autotools: Avoid find race for S = "${WORKDIR}"

2015-03-29T22:07:17+00:00

For recipes with PACKAGES_remove = "${PN}", the find which removes .la files
can race against deletion of other directories in WORKDIR e.g.:

find: '/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/sstate-build-populate_lic': No such file or directory
| WARNING: /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/temp/run.do_configure.6558:1 exit 1 from
|   find /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7 -name \*.la -delete

The simplest fix is to add the find option which ignores these kind of races.

[YOCTO #7522]

Signed-off-by: Richard Purdie

kernel-yocto: merge duplicate kernel_configme task definitions

2015-03-29T22:07:16+00:00

The kernel_configme task was added twice (once in the .bbclass, one in a .inc)
with different ordering constraints.

Change this to be just one definition in the bbclass with the stronger ordering
constraints.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

linux-yocto: add kern-tools-native to kernel_metadata depends

2015-03-29T22:07:15+00:00

The autobuilder failed like this:

  temp/run.do_kernel_metadata.25242: line 165: createme: command not found

createme is provided by kern-tools-native.  do_patch has a dependency on
kern-tools-native, but do_kernel_metadata runs before do_patch.  So move the
dependency from do_patch to do_kernel_metadata, moving the statement from the
.inc to the class so it's alongside the task definition.

[ YOCTO #7531 ]

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

toaster.bbclass: do not add symbolic links to artifacts

2015-03-29T22:07:14+00:00

This patch removes the symbolic links from the artifact list.

[YOCTO #7184]

Signed-off-by: Alexandru DAMIAN 
Signed-off-by: Richard Purdie

kernel-yocto: allow in-tree defconfigs

2015-03-24T22:51:07+00:00

In a similar manner to the kernel itself, which does the following to
bring a defconfig into the configuration:

    defconfig: $(obj)/conf
    ifeq ($(KBUILD_DEFCONFIG),)
        $< --defconfig $(Kconfig)
    else
        @echo "*** Default configuration is based on '$(KBUILD_DEFCONFIG)'"
        $(Q)$< --defconfig=arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG) $(Kconfig)
    endif

We do the same with the linux-yocto configuration processing. If a
defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it
from the source tree, into a common location and normalized "defconfig"
name, where the rest of the process will include and incorporate it
into the configuration process.

If the fetcher has already placed a defconfig in WORKDIR (from the
SRC_URI), we don't overwrite it, but instead warn the user that SRC_URI
defconfigs take precedence.

[YOCTO: #7474]

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

image.bbclass: Empty /var/volatile if it is a mount point

2015-03-24T17:52:43+00:00

If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there, they will no longer be able to be accessed
once the tmpfs gets mounted at /var/volatile.

This problem can be seen for instance when systemd creates
/var/volatile/log/journal as part of its package installation. It then
assumes the journal is persistent even though /var/volatile/log/journal
goes away shortly thereafter.

This change makes sure that there are no files in /var/volatile if it is
to be used as a mount point.

[Yocto #7388]

Signed-off-by: Randy Witt 
Signed-off-by: Richard Purdie