Re: [yocto] Install native recipe into filesystem

[Ross Burton]

On 19/11/2019 21:15, Jeff Kaisner wrote:
We have several executables that can run on the target (ARM64) but also 
on the host system (x86).  I added the BBCLASSEXTEND = "native" and can 
build all the recipes in native mode.  Once done, I would like to be 
able to install them on the host system, but don’t see a package for 
them (or understand that part of the process).


I'm guessing you have a recipe called something like foo.bb.  You've 
added BBCLASSEXTEND=native to this, and can bitbake foo-native.


If you want to also build this for the target, simply add foo to the 
IMAGE_DEPENDS or directly bitbake foo.


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

Re: [yocto] Enable systemd service with parameter

[Ross Burton]

On 17/11/2019 19:44, Mateusz Majchrzycki wrote:
What am I doing wrong? I suppose the symlink is not a problem as 
normally systemctl enables service with non-existent file as a parameter 
(it fails on start, but not enabling).


The problem is that the systemd class doesn't know what to do here.  I 
thought there were patches to handle this already, what release of yocto 
are you using?


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

Re: [yocto] Collaboration on Testing GCC/LLVM Toolchains

[Ross Burton]

On 14/11/2019 18:05, Nicholas Krause wrote:

I think its a good idea. Currently, we test released versions mostly,
however, there is
a class to switch to git versions and primarily be able to use tip of
master for a given
recipe, this would be something I wish we had but so far we have not
fully completed it
I know Ross had started this work and created initial skeleton, So
step one would be to
complete that class so we can easily switch recipes to use dev
versions of packages
this will go beyond GCC but certainly will be a tremendous achievement.


Does Ross have a copy of the skeleton or someone else as I would

like to take a look at it. Don't think I will be much help writing it as

I'm not too familiar with bitbake recipes or classes themselves.
Fixing devupstream.bbclass (already integrated into oe-core) to also 
extend native recipes is a non-trivial engineering effort sadly.


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

Re: [yocto] [meta-mingw][PATCH] Add sdktest image

[Ross Burton]

On 12/11/2019 19:48, Joshua Watt wrote:

Adds a specific image that can be used to build MinGW SDKs. This image
includes extra recipes that are know to build for MinGW so that they can
be tested on the autobuilder.


+1 feel free to merge.

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

Re: [yocto] pkg-config not found

[Ross Burton]

On 12/11/2019 21:06, Mark Hawthorne wrote:

I have an autotools build that uses the following autoconfig file:

AC_INIT([my-program], [1])
AM_INIT_AUTOMAKE([-Wall -Werror foreign])
AC_LANG(C++)
AC_PROG_CXX
AX_PTHREAD()
PKG_CHECK_MODULES(LIBPNG, libpng >= 1.6.34)
PKG_CHECK_MODULES(FREETYPE2, freetype2 >= 21.0.15)
PKG_CHECK_MODULES(EGL, egl > 0)
PKG_CHECK_MODULES(GLES2, glesv2 > 0)
PKG_CHECK_MODULES(GLM, glm >= 0.9.9)
PKG_CHECK_MODULES(SPATIALITE, spatialite >= 4.3.0)
AC_CONFIG_FILES([Makefile])
AC_OUTPUT


I have made the following bitbake recipe file


SUMMARY = "my program"
HOMEPAGE = ""
DESCRIPTION = ""
LICENSE = "MIT"
LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"


SRC_URI = "git://u...@bitbucket.org/user/myrepo.git 
"


SRCREV = "dc1391dbc82702fd0126d4156d4ab59571427efe"

DEPENDS_${PN} = "libpng freetype glm libegl libgles2 libspatialite"

S = "${WORKDIR}/git"

inherit pkgconfig autotools


The build fails with this error:

configure: error: in 
`/home/user/Documents/tisdk/build/arago-tmp-external-arm-toolchain/work/armv7at2hf-neon-linux-gnueabi/my-program/1.0-r0/build':
configure: error: The pkg-config script could not be found or is too 
old.  Make sure it is in your PATH or set the PKG_CONFIG environment 
variable to the full path to pkg-config.


Alternatively, you may set the environment variables LIBPNG_CFLAGS and 
LIBPNG_LIBS to avoid the need to call pkg-config.




That *should* work.  The config.log in the build directory might have 
more useful information.


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

Re: [yocto] Building only the app and not the Linux core

[Ross Burton]

On 12/11/2019 16:52, gholhak...@yahoo.com wrote:

so you mean there is no way not to build them? I don't need any native tool.
I define my cross-compilation toolchain in my layer.
I asked you in twitter, you said "Use multiconfig to split the Linux 
and  rtos entirely". I could not figure it, so I decided not to bother 
you in twitter and ask it here :)


Have a look and you'll see what it is building.  If you can remove those 
dependencies from your build then it won't build them...


I suspect you can't.  Your cross compiler will be built in the 
x86-64_linux folder for a start.


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

Re: [yocto] Building only the app and not the Linux core

[Ross Burton]

On 12/11/2019 16:17, gholhak...@yahoo.com wrote:
My question now is, how can I avoid hassle of building the x86_64-linux? 
I just need my test.elf file.


Have a look in that folder to see what it is building.  That directory 
is for native tools, like GCC.


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

Re: [yocto] Building only the app and not the Linux core

[Ross Burton]

On 12/11/2019 15:33, gholhak...@yahoo.com wrote:

Hi all,

I would like to build my yocto project, but only my applications. I 
mean, I would like to separate my Linux build and the application build.
I want to just have my meta-layer which contains my application being 
build by calling the bitbake command.

Can anyone give me a pointer? Using the multiconfig is the way to do it?

Best
Em

P.S. If I want to be more specific, I just want to use Yocto as a 
cross-compilation tool for baremetal applications.


Baremetal != "just my app and not Linux".

If you want to build a bare metal application then setup the 
distribution as such: meta-freertos is one example using FreeRTOS, and 
we have newlib or baremetal options for the toolchain.  Using Linux and 
glibc is just the default and not hardcoded.


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

Re: [yocto] [meta-gplv2][PATCH] dosfstools: fix out of bound writes

[Ross Burton]

On 06/11/2019 12:37, Bagwell, Anthony wrote:
> Fix write issues where sprintf writes across both name and ext fields
> and drops the final null terminator outside the struct

ERROR: dosfstools-2.11-r5 do_patch: Command Error: 'quilt --quiltrc 
/data/poky-tmp/gpl2/work/corei7-64-poky-linux/dosfstools/2.11-r5/recipe-sysroot-native/etc/quiltrc 
push' exited with 0  Output:

Applying patch fixing-out-of-bound-writes.patch
patching file dosfsck/check.c
Hunk #1 succeeded at 58 with fuzz 1.
Hunk #2 FAILED at 117.
Hunk #3 FAILED at 157.
Hunk #4 FAILED at 318.
3 out of 4 hunks FAILED -- rejects in file dosfsck/check.c
Patch fixing-out-of-bound-writes.patch does not apply (enforce with -f)

Did you prepare this against master?

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

Re: [yocto] Using GitLab for OE/Yocto layers

[Ross Burton]

On 06/11/2019 21:41, Adrian Bunk wrote:

1. Patch review

Merge requests work well when there is one maintainer who reviews
everything. For not regressing on the current level of review before
something hits master, merging a merge request into master-next
should then result in patch review emails sent to a list.
Or a setup where creation of a merge request automatically generates
review emails.

This is similar to all patches for stable branches now being sent for
review to the mailing list a few days before they get merged into the
stable branch, which has caught problematic patches due to more people
reviewing them.


I've had discussions about this in the past too.  With merge requests it 
seems reasonable to automatically tag in relevant maintainers when the 
request is created to request review.  For example if oe-core was on 
GitLab then a MR touching GCC would automatically assign to Khem.


I agree that drive-by review is an important part for a core layer such 
as oe-core where a single maintainer can't know all of the details, so 
the ability to post at least new merge requests - and ideally all 
traffic - to a list for this is essential.


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

Re: [yocto] help with meta-java

[Ross Burton]

On 05/11/2019 08:18, Vincent Prince wrote:

Main layer maintainers:
   Henning Heinold 
   Maxin John 
   Otavio Salvador 
   Richard Leitner 


Maxin no longer works at Intel and I believe doesn't work on Yocto 
anymore either.


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

Re: [yocto] Debugging custom python code in recipes

[Ross Burton]

On 01/11/2019 21:30, Alan Martinović wrote:

Cool, thanks.

This one seems to be the most up to date from the python debugger wrappers:
https://github.com/ionelmc/python-remote-pdb


Entirely worth writing a proper class and pushing a layer somewhere.


The `shell_wait()` in your bbclass is related to the pdb() functionality?


No, it's just a way of making shell tasks pause for inspecting the state 
of the build tree during a task.  I was debugging some nasty packaging 
failures...


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

Re: [yocto] Debugging custom python code in recipes

[Ross Burton]

On 01/11/2019 20:44, Alan Martinović wrote:

Hey,
there was a question today about options for debugging python scripts in yocto.
I've patched up this PoC for remote debugging.


FWIW, I've done something similar using bare pdb.

https://github.com/rossburton/meta-ross/blob/master/classes/pdb.bbclass

Just call pdb() from Python context.  Not as neat as epdb though.

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

Re: [yocto] visual studio code packages or building instructions?

[Ross Burton]

On 01/11/2019 17:51, Aaron Solochek wrote:

Well I grabbed the .deb that one of those links mentioned and converted it to 
an rpm, but of course there are a ton of unmet dependencies, so I might have to 
build it anyway.

I found these instructions for building it, which are pinned to an older 
version (which is probably fine)

https://github.com/futurejones/code-oss-aarch64

I have gotten most of the dependencies built with bitbake, except for the  x11 
stuff:

ERROR: Nothing RPROVIDES 'packagegroup-core-x11' (but 
/home/aarons/sri/bullitt/nxp/imx-yocto-bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/fsl-image-qt5-validation-imx.bb
 RDEPENDS on or otherwise requires it)
packagegroup-core-x11 was skipped: missing required distro feature 'x11' (not 
in DISTRO_FEATURES)
NOTE: Runtime target 'packagegroup-core-x11' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-core-x11']
ERROR: Required build target 'fsl-image-qt5-validation-imx' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['fsl-image-qt5-validation-imx', 
'packagegroup-core-x11']

But this is my local.conf:

MACHINE ??= 'imx8mqevk'
DISTRO ?= 'fsl-imx-wayland'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
 STOPTASKS,${TMPDIR},1G,100K \
 STOPTASKS,${DL_DIR},1G,100K \
 STOPTASKS,${SSTATE_DIR},1G,100K \
 STOPTASKS,/tmp,100M,100K \
 ABORT,${TMPDIR},100M,1K \
 ABORT,${DL_DIR},100M,1K \
 ABORT,${SSTATE_DIR},100M,1K \
 ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"
#IMAGE_FEATURES_append = " package-management tools-sdk  x11-base x11"
IMAGE_FEATURES += "package-management"
IMAGE_FEATURES += "tools-sdk"
IMAGE_FEATURES += "x11-base"
IMAGE_FEATURES += "x11"


As you can see, I tried adding x11 both using IMAGE_FEATURES += as well as 
IMAGE_FEATURES_append (where I would then comment out the += lines)
Why is x11 never getting added to the DISTRO_FEATURES? I also tried putting x11 
in DISTRO_FEATURES and DISTRO_FEATURES_append.

What is the correct thing here?


Adding x11 to IMAGE_FEATURES doesn't achieve anything, as x11 isn't an 
IMAGE_FEATURE.  It's a DISTRO_FEATURE.


DISTRO ?= 'fsl-imx-wayland'

https://github.com/Freescale/meta-freescale-distro/blob/master/conf/distro/fsl-wayland.conf 
says that this explicitly does DISTRO_FEATURES_remove = "x11" so you 
can't add it back.


I suggest you use a DISTRO that supports X11.

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

Re: [yocto] visual studio code packages or building instructions?

[Ross Burton]

On 01/11/2019 16:35, Aaron Solochek wrote:

I would like to get visual studio code on my NXP i.MX8. If someone is
aware of a aarch64 rpm of it, that would be the easiest. Alternatively,
if anyone knows how to build it using bitbake, I can build it myself.


Well Microsoft only make x86 binaries available:

https://code.visualstudio.com/#alt-downloads

So you'll have to follow the instructions at 
https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run


They use Yarn, so you'll have to package that first.

Comments like 
https://github.com/microsoft/vscode/issues/6442#issuecomment-509605292 
on the bug asking for RPi support isn't exactly encouraging though.


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

Re: [yocto] GCC version 8 upgrade

[Ross Burton]

On 31/10/2019 15:49, Bishop . wrote:
How silly would it be to try and get GCC sdk v8 complied and installed 
for Jethro?


Quite.  GCC upgrades are tricky things to do at the best of times.

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

Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

[Ross Burton]

On 30/10/2019 12:11, Arno Steffens wrote:

I use a poky core-image-minimal with some packages added - as for instance 
strace and valgrind (for armv7a).
Strange - yocto in older versions generates images with valgrind/strace .. 
without any complaints.
So both PC and image-recipe are same, but in Yocto 2.5 and 2.7 it works, in 3.0 
not ?!?

Sorry I am confused, do you mean python is missing in requested image or at 
host PC with Ubuntu 1804? If it is missing in image,
shouldn't it be included by dependencies automatically?

At UbuntuPC python 2.7 is installed:
python
Python 2.7.15+ (default, Oct 7 2019, 17:39:04)
[GCC 7.4.0] on linux2


I mean the host, as that's running code using the host python during the 
build.


Try this:

$ python3 -m distutils.sysconfig

If that does nothing then your Python is working.  If it fails then you 
need to install the full Python 3 on your machine, not just minimal.


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

Re: [yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

[Ross Burton]

On 30/10/2019 06:25, s...@gmx.li wrote:

Build of image failed, I got strange and long error messages like:

| from distutils.sysconfig import parse_makefile
| ModuleNotFoundError: No module named 'distutils.sysconfig'
| configure: error: Python failed to run; see above error.



a) What goes wrong here and how can this be avoid?


distutils.sysconfig is part of the standard Python library.  What 
distribution are you using?  It's possible that you've only got a 
'minimal' Python installed instead of the full thing.



b) How do I found which module is responsible. There is nothing about 
strace/valgrind mentioned in the log. I just had to build all my additional 
packets of my image manually to find the triggers for this icu-native.


The recipe responsible is icu-native.  Something in your build depends 
on this, such as boost-native maybe.


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

Re: [yocto] systemd Version Going Backwards on Warrior

[Ross Burton]

On 29/10/2019 04:41, Robert Joslyn wrote:

On Mon, 2019-10-28 at 19:06 +, Ross Burton wrote:

On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote:

I'm using buildhistory in one of my builds that creates a package
feed, and a recent update to systemd on warrior triggered version-
going-backwards errors:

ERROR: systemd-conf-241+AUTOINC+511646b8ac-r0 do_packagedata: QA
Issue: Package version for package systemd-conf-src went backwards
which would break package feeds from (0:241+0+c1f8ff8d0d-r0 to
0:241+0+511646b8ac-r0) [version-going-backwards]

Should PE have been updated at the same time due to the hash making
the version number go backwards? I can send a patch if that's all
that's missing. Or is a PR server enough to prevent this? My debug
builds do not use a PR server, but my production builds do use a PR
server.


If you're using feeds, you need to use a PR server.  This is *exactly*
what they are for.

>


The part I wasn't sure about was if the PR server helped in the case where
PV went backwards. I know it works when PV stays the same but the package
was rebuilt. But if it keeps the versions going forward no matter how PV
changes, then I should be good. I should probably setup a separate PR
server on my debug builds to avoid this kind of error.


If the PV actually goes backwards then the PR service isn't useful, as 
PV sorts before PR.


However in this case the problem is that SRCREV should have a 
incrementing counter (the +0+ should be +1+ in the rebuild) which I 
believe comes from the PR service.  I may be wrong...


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

Re: [yocto] systemd Version Going Backwards on Warrior

[Ross Burton]

On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote:

I'm using buildhistory in one of my builds that creates a package feed, and a 
recent update to systemd on warrior triggered version-going-backwards errors:

ERROR: systemd-conf-241+AUTOINC+511646b8ac-r0 do_packagedata: QA Issue: Package 
version for package systemd-conf-src went backwards which would break package 
feeds from (0:241+0+c1f8ff8d0d-r0 to 0:241+0+511646b8ac-r0) 
[version-going-backwards]

Should PE have been updated at the same time due to the hash making the version 
number go backwards? I can send a patch if that's all that's missing. Or is a 
PR server enough to prevent this? My debug builds do not use a PR server, but 
my production builds do use a PR server.


If you're using feeds, you need to use a PR server.  This is *exactly* 
what they are for.


Ross

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

Re: [yocto] [psplash][PATCH] Adding SPDX license identifier to psplash

[Ross Burton]

On 23/10/2019 09:00, Yann CARDAILLAC wrote:

Hi,

If you have any advice please feel free to ask.

I've put GPLV2 or later whenever it was mentioned and GPLV2 where nothing was
saying otherwise.


I'd say the license was intended to be uniform, so if there are mentions 
of v2-or-later then make it all or-later.


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

Re: [yocto] [meta-mingw][PATCH 1/3] libxml2: Remove python support

[Ross Burton]

On 28/10/2019 15:58, Joshua Watt wrote:

Python doesn't cross compile for MinGW, so remove it as a dependency
from the mingw32 nativesdk build


+1 please push
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Reducing the size of the image by optimizing python

[Ross Burton]

On 19/10/2019 13:45, Abhi Arora wrote:

IMAGE_INSTALL_append = " \
     python3 \




This is installing "all of python".  If you want to trim your Python 
installation then don't do that, instead determine what libraries you 
*actually* need and explicitly add those.


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

Re: [yocto] trouble with rootfs generation with mxnet package

[Ross Burton]

On 17/10/2019 03:45, karthik poduval wrote:

Upon looking at the
build/tmp/work/aarch64-xilinx-linux/mxnet/1.5.0-r0/packages-split
directory
I find that the mxnet sub directory is empty, mxnet-dev,
mxnet-staticdev  have libmxnet.so and libmxnet.a respectively under
usr/lib.


Don't set PACKAGES, as that's the default anyway.

So it *looks* like the mxnet recipe doesn't ship versioned libraries, 
which is very bad form for something from Apache.  If this is the case 
then read 
https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries.


If they do ship versioned libraries (by which I mean the library is 
libxmnet.so.1.2.3 or similar) then remove FILES and INSANE_SKIP, and let 
the packaging happen normally.


You've likely got the library package renamer enabled (it's on out of 
the box) so the resulting package will be libmxnet1 or similar, 
depending on the soname of the library.


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

Re: [yocto] NooB: qemu-native compile error during bitbake core-image-sato

[Ross Burton]

On 14/10/2019 22:32, myken wrote:
For future reference, how could I have found this answer? I searched 
like crazy but never found any reference that qemu is "old" and my 
kernel is "new".


By recognising where the failure was, knowing that glibc changed, and 
that qemu needs to be fixed, then finding the relevant fixes already 
existed in qemu.


Running unsupported distros means discovering stuff like this.  :)

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

Re: [yocto] NooB: qemu-native compile error during bitbake core-image-sato

[Ross Burton]

On 14/10/2019 17:20, p...@iae.nl wrote:

Hello list,

First time here so, hi there :-) I'm new to yocto but not new to linux.

I'm following the Yocto Project Quick Build manual 
(https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html)
on an Arch (Manjaro) machine (uname -r: 4.19.79-1-MANJARO). I know 
Manjaro is not an official supported distribution but I'm hopping on 
some help nevertheless.


My build stops at:
 >> bitbake core-image-sato

Build Configuration:
BB_VERSION   = "1.42.0"
BUILD_SYS    = "x86_64-linux"
NATIVELSBSTRING  = "manjaro"
TARGET_SYS   = "i586-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "2.7.1"
TUNE_FEATURES    = "m32 i586"
TARGET_FPU   = ""
meta
meta-poky
meta-yocto-bsp   = 
"my-yocto-2.7.1:38d5c8ea98cfa49825c473eba8984c12edf062be"


WARNING: Your host glibc verson (2.30) is newer than that in uninative 
(2.29). Disabling uninative so that sstate is not corrupted.


ERROR: qemu-native-3.1.0-r0 do_compile: oe_runmake failed
ERROR: qemu-native-3.1.0-r0 do_compile: Function failed: do_compile (log 
file is located at 
poky/build/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/temp/log.do_compile.1259)
ERROR: Logfile of failure stored in: 
poky/build/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/temp/log.do_compile.1259


One of the errors in the log.do_compile.1259 file (file attached):
poky/build/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/qemu-3.1.0/linux-user/syscall.c:253:16: 
error: static declaration of ‘gettid’ follows non-static declaration

   253 | _syscall0(int, gettid)
OR
poky/build/tmp/work/x86_64-linux/qemu-native/3.1.0-r0/qemu-3.1.0/linux-user/ioctls.h:223:9: 
error: ‘SIOCGSTAMPNS’ undeclared here (not in a function); did you mean 
‘SIOCGSTAMP_OLD’?

   223 |   IOCTL(SIOCGSTAMPNS, IOC_R, MK_PTR(MK_STRUCT(STRUCT_timespec)))


I do not know enough to understand where this error comes from. But I 
suspect it may have to do with the warning I got just before the failure:


Is there a way to tell the build system to ignore the newer version 
glibc? And use the 2.29 version.

Or can someone help me to debug this error?


You're trying to build an older qemu against a very new kernel.  If you 
can, grab the warrior branch from git instead of using the 2.7.1 release 
as that has the fix in.  Alternatively, cherry-pick this commit:


http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0570ef5a5e180f7504df970645d1fcce6310b828

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

[yocto] [PATCH release-tools] README: add section on contributing patches

[Ross Burton]

Signed-off-by: Ross Burton 
---
 README | 21 -
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/README b/README
index ae92709..5a545ce 100644
--- a/README
+++ b/README
@@ -59,7 +59,7 @@ them, and the meta-intel release process, are not covered 
here.
 
 
 Yocto Release Process
-===
+=
 
 This section deals with the Yocto release process as it pertains to the tools 
in
 this repo. There are other release activities that happen which outside the
@@ -110,3 +110,22 @@ repackage the :wq
 logging.info('Generating the master md5sum table.')
 gen_rel_md5(RELEASE_DIR, REL_MD5_FILE)
 logging.info('Successful.')
+
+
+Contributing
+
+
+This module is owned by Vineela Tummalapalli .
+
+Patches should be sent via git-send-email to the yocto@yoctoproject.org 
mailing list with
+[release-tools] in the subject, CC'd to Vineela.
+
+The following commands will configure this if ran inside a clone of 
release-tools:
+
+$ git config  --local --add format.subjectprefix 'PATCH release-tools'
+$ git config  --local --add sendemail.to yocto@yoctoproject.org
+$ git config  --local --add sendemail.cc vineela.tummalapa...@intel.com
+
+Then sending a patch is as simple as:
+
+$ git send-email origin/master
-- 
2.20.1

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

Re: [yocto] Force do_package_index

[Ross Burton]

On 10/10/2019 16:35, Mauro Ziliani wrote:

How to force the execuction o do_package_index over an image recipe?


Are you intending to use the deploy directory as a package feed? 
"bitbake package-index" for that.


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

[yocto] [PATCH][yocto-docs] ref-system-requirements: update support distribution list

[Ross Burton]

Add Fedora 30 and Ubuntu 19.04.

Swap openSUSE 42.3 for Leap 15.1.

Remove huge comment of old distributions.

Signed-off-by: Ross Burton 
---
 .../ref-manual/ref-system-requirements.xml| 54 ++-
 1 file changed, 4 insertions(+), 50 deletions(-)

diff --git a/documentation/ref-manual/ref-system-requirements.xml 
b/documentation/ref-manual/ref-system-requirements.xml
index 51995309d..9c2198a76 100644
--- a/documentation/ref-manual/ref-system-requirements.xml
+++ b/documentation/ref-manual/ref-system-requirements.xml
@@ -89,65 +89,19 @@
 
 
 Ubuntu 16.04 (LTS)
-Ubuntu 18.04
+Ubuntu 18.04 (LTS)
+Ubuntu 19.04
 Fedora 28
 Fedora 29
+Fedora 30
 CentOS 7.x
 Debian GNU/Linux 8.x (Jessie)
 Debian GNU/Linux 9.x 
(Stretch)
 Debian GNU/Linux 10.x 
(Buster)
-OpenSUSE 42.3
+OpenSUSE Leap 15.1
 
 
 
-
-
-
-
 
 While the Yocto Project Team attempts to ensure all Yocto Project
 releases are one hundred percent compatible with each officially
-- 
2.20.1

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

Re: [yocto] Downloading Git Archives

[Ross Burton]

On 27/09/2019 05:33, Chuck Wolber wrote:
I was hoping that there was an equally simple way of grabbing git 
repository packages from an Internet connected host without having a 
bitbake build cache them for me.


The easy way is to get bitbake to do it for you.  A git mirror tarball 
is just a clone with a specific name and path, but the easy solution is 
definitely to run bitbake --c fetchall on a machine with connectivity 
and expose the DL_DIR to the builders.


This is what the yocto autobuilder does, by the way.  The workers don't 
have connectivity to the outside internet, so the master does a fetchall 
with the proxies configured to populate DL_DIR before the workers do the 
actual build.


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

Re: [yocto] Nothing PROVIDES 'python3-dev'

[Ross Burton]

On 24/09/2019 10:36, Damien LEFEVRE wrote:

Hi,

Migrating from poky:pyro to poky:warrior.

It looks like the python3-dev package is generated from 
python3-manifest.json:


     "dev": {
         "cached": [],
         "files": [
             "${base_libdir}/*.a",
             "${base_libdir}/*.o",
             "${bindir}/python*-config",
             "${datadir}/aclocal",
             "${datadir}/pkgconfig",
             "${includedir}",
             "${libdir}/*.a",
             "${libdir}/*.la",
             "${libdir}/*.o",
             "${libdir}/lib*${SOLIBSDEV}",
             "${libdir}/pkgconfig"
         ],
         "rdepends": [
             "core"
         ],
         "summary": "Python development package"
     },

and this is used in python3_3.7.2.bb .

Still I get this error: Nothing PROVIDES 'python3-dev'


Are you trying to 'bitbake python3-dev'?  You bitbake a recipe, not a 
package, so 'bitbake python3'.


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

Re: [yocto] "bitbake core-image-sato" yields "No package 'gdk-x11-3.0' found" build failure

[Ross Burton]

On 23/09/2019 15:26, Jean-Baptiste MARIE wrote:
Indeed wayland is enabled in my distro features, so my question is more: 
is there any reason to remove x11 from package config when "wayland" is 
enabled as a distro feature (but maybe it is no longer a question to be 
addressed ot yocto community)? As Ross mentioned, there can both be built.


That's a question for the maintainers of your BSP, they did that for a 
reason.  Plain oe-core will enable both if the DISTRO has both x11 and 
wayland enabled.


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

Re: [yocto] "bitbake core-image-sato" yields "No package 'gdk-x11-3.0' found" build failure

[Ross Burton]

On 23/09/2019 13:48, Jean-Baptiste MARIE wrote:

PACKAGECONFIG_remove_imxgpu2d = " \
     ${@bb.utils.contains("DISTRO_FEATURES", "wayland", "x11", "", d)} \
"

I do not see any reason why gdk-x11-3.0 would not be built


So if Wayland is enabled, then it disables X11.  Do you have Wayland 
enabled?  I wonder why the BSP does this: you can build both just fine.


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

Re: [yocto] Debug-files in SDK

[Ross Burton]

On 23/09/2019 10:19, Teemu K wrote:

One question is that is there a way to make package that would contain
only dpg-pkgs and src-pkgs? Ie. it'd be like 'debug-addition' for SDK?
I know how to install those things to target, but how to get them to a
package (or in separate directory) to host.


This is where you'd use an Extensible SDK instead of a traditional SDK, 
where you can install packages into the sysroot after installation.


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

Re: [yocto] [meta-gplv2][master][warrior][PATCH] tar: Make it build with GCC 8.3

[Ross Burton]

Missing an upstream-status, but good to push when that's fixed.

Ross

On 18/09/2019 16:48, Peter Kjellerstedt wrote:

From: Joakim Roubert 

This avoids the following error:

   lib/argp-parse.c: In function 'argp_version_parser':
   lib/argp-parse.c:158:2: error: format not a string literal and no
   format arguments [-Werror=format-security]
 __argp_error (state, dgettext (state->root_argp->argp_domain,
 ^~~~

Signed-off-by: Joakim Roubert 
Signed-off-by: Peter Kjellerstedt 
---
  ...-lib-argp-parse.c-Fix-compiler-error.patch | 34 +++
  recipes-extended/tar/tar_1.17.bb  |  1 +
  2 files changed, 35 insertions(+)
  create mode 100644 
recipes-extended/tar/tar/0001-lib-argp-parse.c-Fix-compiler-error.patch

diff --git 
a/recipes-extended/tar/tar/0001-lib-argp-parse.c-Fix-compiler-error.patch 
b/recipes-extended/tar/tar/0001-lib-argp-parse.c-Fix-compiler-error.patch
new file mode 100644
index 000..3de9fd1
--- /dev/null
+++ b/recipes-extended/tar/tar/0001-lib-argp-parse.c-Fix-compiler-error.patch
@@ -0,0 +1,34 @@
+From 153c0aab9e2a4a97b1a2c6b530594cd9a211e9ec Mon Sep 17 00:00:00 2001
+From: Joakim Roubert 
+Date: Thu, 6 Dec 2018 10:33:14 +0100
+Subject: [PATCH] lib/argp-parse.c: Fix compiler error
+
+This avoids the following error:
+
+  lib/argp-parse.c: In function 'argp_version_parser':
+  lib/argp-parse.c:158:2: error: format not a string literal and no
+  format arguments [-Werror=format-security]
+__argp_error (state, dgettext (state->root_argp->argp_domain,
+^~~~
+
+Signed-off-by: Joakim Roubert 
+---
+ lib/argp-parse.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/lib/argp-parse.c b/lib/argp-parse.c
+index a7de729..09511ba 100644
+--- a/lib/argp-parse.c
 b/lib/argp-parse.c
+@@ -155,7 +155,7 @@ argp_version_parser (int key, char *arg, struct argp_state 
*state)
+   else if (argp_program_version)
+   fprintf (state->out_stream, "%s\n", argp_program_version);
+   else
+-  __argp_error (state, dgettext (state->root_argp->argp_domain,
++  __argp_error (state, "%s", dgettext (state->root_argp->argp_domain,
+  "(PROGRAM ERROR) No version known!?"));
+   if (! (state->flags & ARGP_NO_EXIT))
+   exit (0);
+--
+2.11.0
+
diff --git a/recipes-extended/tar/tar_1.17.bb b/recipes-extended/tar/tar_1.17.bb
index b9ca206..1ee5e34 100644
--- a/recipes-extended/tar/tar_1.17.bb
+++ b/recipes-extended/tar/tar_1.17.bb
@@ -8,6 +8,7 @@ PR = "r3"
  SRC_URI += "file://m4extensions.patch \
  file://gcc43build.patch \
  file://avoid_heap_overflow.patch \
+file://0001-lib-argp-parse.c-Fix-compiler-error.patch \
  "
  
  SRC_URI[md5sum] = "c6c4f1c075dbf0f75c29737faa58f290"




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

Re: [yocto] Auto-remove empty package from rootfs

[Ross Burton]

On 20/09/2019 07:12, Vignesh Rajendran (RBEI/ECF3) wrote:

Hello All,

I have a feeling that the empty packages are really not useful inside 
rootfs/sysroot either dependency with other packages, isn’t it?


Is there already a way in Yocto to remove/avoid empty packages from rootfs?


An empty package by definition doesn't have any impact on the rootfs, 
because it's empty.  The majority of empty packages are used for their 
dependency management: package groups are just empty packages which have 
dependencies.


If you know of any empty packages which have no dependencies, feel free 
to submit a patch to remove them from the metadata.


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

Re: [yocto] [PATCH] kernel.fitimage.bbclass: remove ramdisk_ctype

[Ross Burton]

This should go to the oe-core list, 
openembedded-c...@lists.openembedded.org.


Thanks,
Ross

On 19/09/2019 09:13, Heiko Schocher wrote:

set in the ramdisk node the compression property
always to "none", as U-Boot nowadays since commit:

b1307f884a91 ("fit: Support compression for non-kernel components (e.g. FDT)")

decompress non kernel components. Setting compression
to the used comression algorithm now, will end in
fail of your kernel boot with the ramdisk.

This issue is fixed since commit:

bddd98573465 ("fit: Do not automatically decompress ramdisk images")

which now prints a warning in U-Boot, instead of decompressing
the ramdisk, but we should setup compression property correct.

Signed-off-by: Heiko Schocher 
---

  meta/classes/kernel-fitimage.bbclass | 21 +
  1 file changed, 1 insertion(+), 20 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index b51882dce4..1bcb09c598 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -207,7 +207,6 @@ EOF
  fitimage_emit_section_ramdisk() {
  
  	ramdisk_csum="${FIT_HASH_ALG}"

-   ramdisk_ctype="none"
ramdisk_loadline=""
ramdisk_entryline=""
  
@@ -218,24 +217,6 @@ fitimage_emit_section_ramdisk() {

ramdisk_entryline="entry = <${UBOOT_RD_ENTRYPOINT}>;"
fi
  
-	case $3 in

-   *.gz)
-   ramdisk_ctype="gzip"
-   ;;
-   *.bz2)
-   ramdisk_ctype="bzip2"
-   ;;
-   *.lzma)
-   ramdisk_ctype="lzma"
-   ;;
-   *.lzo)
-   ramdisk_ctype="lzo"
-   ;;
-   *.lz4)
-   ramdisk_ctype="lz4"
-   ;;
-   esac
-
cat << EOF >> ${1}
  ramdisk@${2} {
  description = "${INITRAMFS_IMAGE}";
@@ -243,7 +224,7 @@ fitimage_emit_section_ramdisk() {
  type = "ramdisk";
  arch = "${UBOOT_ARCH}";
  os = "linux";
-compression = "${ramdisk_ctype}";
+compression = "none";
  ${ramdisk_loadline}
  ${ramdisk_entryline}
  hash@1 {



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

Re: [yocto] Changing HOST_CC_ARCH temporarily in recipe

[Ross Burton]

On 18/09/2019 09:26, Damien LEFEVRE wrote:
I have a package which requires to first build a x64 binary which is 
then used to compile the target platform binaries.


The way I got away with it was to build that host binary from 
do_configure_prepend() and then continue with the build procedure.


I recently upgraded to GCC7 + warrior and now building the host binary 
from do_configure_prepend fails due to this error:

testCCompiler.c:1:0: error: bad value (armv8-a+crc) for -march= switch

I figured that the arch switch (building for tegra) is defined 
in HOST_CC_ARCH as:
-march=armv8-a+crc -fstack-protector-strong  -D_FORTIFY_SOURCE=2 
-Wformat -Wformat-security -Werror=format-security


If I clear HOST_CC_ARCH in my recipe file, do_configure_prepend succeeds 
but of course the rest of the build will fail.


So i'm trying to do something like this:
do_configure_prepend(){
     export HOST_CC_ARCH_BACKUP="${HOST_CC_ARCH}"
     HOST_CC_ARCH=""
     echo "HOST_CC_ARCH before cmake: ${HOST_CC_ARCH}"
     CC="${BUILD_CC}" CXX="${BUILD_CXX}" CCFLAGS="${BUILD_CFLAGS}" 
  CXXFLAGS="${BUILD_CPPFLAGS} -std=c++11" LDFLAGS="${BUILD_LDFLAGS}" 
cmake ${S}

     make
     HOST_CC_ARCH="${HOST_CC_ARCH_BACKUP}"
}


Two solutions:
1) Work around the problem by manually building the tool yourself.  This 
should be done in do_compile_prepend so that it isn't newer than the 
makefiles, which would cause it to be regenerated.


There's no need to mess around with HOST_CC_ARCH. That is only used in 
CC/CXX/FC/CPP, and you should be using BUILD_CC etc anyway.  This 
*should* work:


do_compile_prepend() {
  CC="${BUILD_CC}" CPP=... CFLAGS=... CXXFLAGS=... LDFLAGS=... make 
[target]

}

(expand the ..., I'm lazy)

If HOST_CC_ARCH is being used then there's only a limited number of 
variables that use it, so override the right ones. May be CPP, may be 
CXX. Looking at the makefile will tell you. Always just build exactly 
what you need with the native compiler, not more.


However the proper solution is
2) fix the cmakefiles to work in cross builds.  CMake actually makes 
this even harder than autotools which is quite an achievement: 
https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/CrossCompiling#using-executables-in-the-build-created-during-the-build. 
 Quite likely easier to port to Meson, where you just set the native 
property on a binary target.


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

Re: [yocto] [EXTERNAL] Patch a package with condition

[Ross Burton]

On 13/09/2019 17:38, Smith, Virgil (US) wrote:
While you cannot **enforce** a change for one package/in another recipe 
file based on whether another package is included in an image, you can 
have recipes (and their bbappends) respond to configuration settings.  
Two such mechanisms are FEATURES and OVERRIDES.  In this particular case 
I would probably use EXTRA_IMAGE_FEATURES from local.conf (or maybe 
DISTRO_FEATURES or IMAGE_FEATURES directly if making a distro or an 
image recipe).


https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-extend-customimage-imagefeatures

https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-FEATURE_PACKAGES

In your example Package-B.bb do something like (needs testing, search 
the manual for similar snippets, …)


SRC_URI_append = "${@bb.utils.contains('IMAGE_FEATURES', 'myfeature', ' 
file://0001-add-new-line.patch', '', d)}"


The huge caveat here is that typically it's images that set 
IMAGE_FEATURES, so this won't work in the general case.


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

Re: [yocto] Patch a package with condition

[Ross Burton]

On 13/09/2019 06:55, PRASANTH R wrote:
I need to patch my custom recipe, let say "Package-A.bb" in which I need 
to add a patch to the test recipe if the yocto build has a specific 
package like let's say if "Package-B" is available patch should be 
applied for Package-A.bb

I am trying with below step in Package-A.bb
SRC_URI_append_Package-B = " file://0001-add-new-line.patch"

But it doesn't work, I could see this SRC_URI_append_* works only for 
some specific tokens like board name, Architecture, library or 
native-class as such


Have u come across the scenario to make a dependency in patching with 
reference to another package? which way I can use this?


You can't patch a recipe depending on whether another recipe is going to 
be built, because the process is that recipes produce packages, and 
packages built images.


So you're building two images, one of which contains Package-A and the 
other contains Package-A and Package-B.  Bitbake will only build those 
recipes once.


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

Re: [yocto] Debug-files in SDK

[Ross Burton]

On 12/09/2019 11:13, Teemu K wrote:

Hi,

I'm not entirely sure if this is bug or feature.

I've created sdk to my image with populate_sdk - command. I noticed
that in the SDK the x86_64 - directory is 384MB and that contains all
the toolchains etc., but the target side
(cortexa9hf-neon-poky-linux-gnueabi) is 5.7GB. Majority of it is in
.debug - directories.

What causes the confusion here is that I haven't enabled debug-symbols
in my local.conf and I don't have any other debug stuff enabled there
either. Are those the debug-symbols that can be used to debug software
on target with GDB for example? I thought that debug symbol
information needs to be separately enabled.

If they are not, then can I get rid of them somehow?


SDKIMAGE_FEATURES ??= "dev-pkgs dbg-pkgs src-pkgs 
${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation', 'doc-pkgs', 
'', d)}"


SDKs by default contain debug symbols, and yes they can be used with gdb 
to debug on target.


If you don't want them in the SDK, remove dbg-pkgs (and src-pkgs whilst 
you're there) from SDKIMAGE_FEATURES.


Ross

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

Re: [yocto] assembler error: missing immediate expression at operand 1 -- `dsb`

[Ross Burton]

On 11/09/2019 15:51, Pandey, Kamal wrote:

I was trying to compile the rpmsg-lite library provided by NXP for my ZC102 
board. While compiling I was getting the error as follows:


Try asking NXP directly.

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

[yocto] [yocto-autobuilder-helper][PATCH] config.json: for API documentation builds bitbake world instead of core-image-sato

[Ross Burton]

Signed-off-by: Ross Burton 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index a92adba..7723285 100644
--- a/config.json
+++ b/config.json
@@ -741,7 +741,7 @@
 ]
 },
 "step3" : {
-"BBTARGETS" : "core-image-sato:do_populate_sdk",
+"BBTARGETS" : "world",
 "extravars" : [
 "DISTRO_FEATURES_append = ' api-documentation'"
 ]
-- 
2.20.1

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

Re: [yocto] [poky] Want to create a x11 image of less than 100 MB with bitbake

[Ross Burton]

On 04/09/2019 09:33, Kamal Jagesia wrote:

 > I need your help to create a small Embedded Linux Image less than 100
 > MB with x11 libraries.
 > I have been trying to do this with core-image-x11 but I need to
 > eliminate packages like bluez5 (Bluetooth) from poky bitbake build.
 > Kindly let me know how to do this .


If you don't need large-scale features like Bluetooth then you can 
remove them from DISTRO_FEATURES so they won't be built or installed.


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

Re: [yocto] WARNING: bluez5-5.50-r0 do_fetch: Failed to fetch URL file://variscite-bt.conf

[Ross Burton]

That file isn't part of oe-core, given the name you should ask the 
variscite-bsp-platform maintainers.


Ross

On 27/08/2019 06:51, Zoran Stojsavljevic wrote:

BTW, I have created the complete description of this problem!
https://github.com/ZoranStojsavljevic/imx6-sabre-automotive-bsp/tree/master/Issues

Best Regards,
Zoran
___

On Mon, Aug 26, 2019 at 5:23 PM Zoran Stojsavljevic 
mailto:zoran.stojsavlje...@gmail.com>> 
wrote:


Hello Folks,

While doing the following YOCTO build:

http://variwiki.com/index.php?title=Yocto_Build_Release=RELEASE_MORTY_V1

Actually, using the latest available tag:
thud-fslc-4.14.78-mx6ul-v1.1


 From https://github.com/varigit/variscite-bsp-platform/tags

I've got the following error, while compiling for both:
bitbake -k fsl-image-gui
bitbake -k fsl-image-qt5

Seems, that the local file: file://variscite-bt.conf is somehow
missing?!

I can add this file artificially, but, the question is: why this
file is missing???
___

Transcript follows:
bluez5-5.50-r0 do_fetch: Failed to fetch variscite-bt.conf
https://pastebin.com/U9LRtNwr

Thank you,
Zoran
___




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

Re: [yocto] Building SDK for macOS

[Ross Burton]

On 20/08/2019 10:13, Ross Burton wrote:

On 20/08/2019 09:53, Andy Pont wrote:
This may be a really dumb question but is it possible to generate an 
SDK from a Yocto build that will allow cross compilation of an 
application to be done on a machine running macOS?


Yes, with caveats: http://git.yoctoproject.org/cgit/cgit.cgi/meta-darwin

The caveats are that it's not especially pretty as you can't just 
download macOS headers, and hasn't been used since 2015 so might need a 
little updating.


Did a little poking.

The need to build a SDK tarball on an existing macOS could probably be 
removed by using one of the convenient tarballs from 
https://github.com/phracker/MacOSX-SDKs/releases.


The SDK is 32-bit, which is going to be an issue on modern macOS systems.

The layer has several versioned bbappends which need updating to work 
with recent releases.


None of this is insurmountable, meta-darwin has been used for products 
in the past and with a little effort can be made to do so again.


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

Re: [yocto] Building SDK for macOS

[Ross Burton]

On 20/08/2019 09:53, Andy Pont wrote:
This may be a really dumb question but is it possible to generate an SDK 
from a Yocto build that will allow cross compilation of an application 
to be done on a machine running macOS?


Yes, with caveats: http://git.yoctoproject.org/cgit/cgit.cgi/meta-darwin

The caveats are that it's not especially pretty as you can't just 
download macOS headers, and hasn't been used since 2015 so might need a 
little updating.


I do wonder if https://github.com/darlinghq/darling has sufficient 
headers/libraries to build what we need, instead of asking you to copy 
pieces from a macOS install.


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

Re: [yocto] Replace busybox by bash

[Ross Burton]

On 06/08/2019 13:34, JH wrote:

The busybox is too simple, my application heavy based on shell
scripts, I have been thinking to dig out the busybox and replace it by
bash, has anyone remove the busybox to use bash as default shell? How
large size will be increased and what will be any side effect?


Removing busybox is not trivial, but you can just install 
bash/coreutils/etc as required.


Yes it's bigger, but you want the full tools.  No side effects.

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

[yocto] [PATCH][yocto-docs] ref-system-requirements: add Debian 10 to supported distribution list

[Ross Burton]

Debian 10 is a supported distribution now, so add it to the documentation.

Signed-off-by: Ross Burton 
---
 documentation/ref-manual/ref-system-requirements.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/documentation/ref-manual/ref-system-requirements.xml 
b/documentation/ref-manual/ref-system-requirements.xml
index 239dd84bbdd..51995309d4f 100644
--- a/documentation/ref-manual/ref-system-requirements.xml
+++ b/documentation/ref-manual/ref-system-requirements.xml
@@ -95,6 +95,7 @@
 CentOS 7.x
 Debian GNU/Linux 8.x (Jessie)
 Debian GNU/Linux 9.x 
(Stretch)
+Debian GNU/Linux 10.x 
(Buster)
 OpenSUSE 42.3
 
 
-- 
2.20.1

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

[yocto] [meta-security][PATCH v2] apparmor: fix Python install paths when target libdir != native libdir

[Ross Burton]

setuptools will install into what python3-native thinks $libdir is, which may
not match the target $libdir.  Pass in libdir as appropriate to force the
correct paths.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb  |  5 ++--
 recipes-security/AppArmor/files/py-libdir.patch | 40 +
 2 files changed, 43 insertions(+), 2 deletions(-)
 create mode 100644 recipes-security/AppArmor/files/py-libdir.patch

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index efa93e6..073b62d 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -18,6 +18,7 @@ SRC_URI = " \
file://disable_perl_h_check.patch \
file://crosscompile_perl_bindings.patch \
file://tool-paths.patch \
+   file://py-libdir.patch \
file://apparmor.rc \
file://functions \
file://apparmor \
@@ -79,9 +80,9 @@ do_install () {
install -d ${D}/${INIT_D_DIR}
install -d ${D}/lib/apparmor

-   oe_runmake -C ${B}/libraries/libapparmor DESTDIR="${D}" install
+   oe_runmake -C ${B}/libraries/libapparmor DESTDIR="${D}" 
PYLIBDIR=${PYTHON_SITEPACKAGES_DIR} install
oe_runmake -C ${B}/binutils DESTDIR="${D}" install
-   oe_runmake -C ${B}/utils DESTDIR="${D}" install
+   oe_runmake -C ${B}/utils DESTDIR="${D}" 
PYLIBDIR=${PYTHON_SITEPACKAGES_DIR} install
oe_runmake -C ${B}/parser DESTDIR="${D}" install
oe_runmake -C ${B}/profiles DESTDIR="${D}" install
 
diff --git a/recipes-security/AppArmor/files/py-libdir.patch 
b/recipes-security/AppArmor/files/py-libdir.patch
new file mode 100644
index 000..2b88e54
--- /dev/null
+++ b/recipes-security/AppArmor/files/py-libdir.patch
@@ -0,0 +1,40 @@
+Let the user override the Python libdir so it goes to the right place, as
+python3-native's idea of $libdir may not match the target's $libdir.
+
+Upstream-Status: Pending
+Signed-off-by: Ross Burton 
+
+diff --git a/libraries/libapparmor/swig/python/Makefile.am 
b/libraries/libapparmor/swig/python/Makefile.am
+index 421acba9..d2b842a6 100644
+--- a/libraries/libapparmor/swig/python/Makefile.am
 b/libraries/libapparmor/swig/python/Makefile.am
+@@ -14,7 +14,7 @@ all-local: libapparmor_wrap.c setup.py
+   $(PYTHON) setup.py build
+ 
+ install-exec-local:
+-  $(PYTHON) setup.py install --root="/$(DESTDIR)" --prefix="$(prefix)"
++  $(PYTHON) setup.py install --root="/$(DESTDIR)" --prefix="$(prefix)" 
--install-lib="$(PYLIBDIR)"
+ 
+ clean-local:
+   if test -x "$(PYTHON)"; then $(PYTHON) setup.py clean; fi
+diff --git a/utils/Makefile b/utils/Makefile
+index 68f8c376..025f9da5 100644
+--- a/utils/Makefile
 b/utils/Makefile
+@@ -42,6 +42,7 @@ DESTDIR=/
+ BINDIR=${DESTDIR}/usr/sbin
+ CONFDIR=${DESTDIR}/etc/apparmor
+ PYPREFIX=/usr
++PYLIBDIR=$PYPREFIX/lib
+ 
+ PYFLAKES=pyflakes
+ 
+@@ -60,7 +61,7 @@ install: ${MANPAGES} ${HTMLMANPAGES}
+   $(MAKE) install_manpages DESTDIR=${DESTDIR}
+   $(MAKE) -C vim install DESTDIR=${DESTDIR}
+   ln -sf aa-status.8 ${DESTDIR}/${MANDIR}/man8/apparmor_status.8
+-  ${PYTHON} ${PYSETUP} install --prefix=${PYPREFIX} --root=${DESTDIR} 
--version=${VERSION}
++  ${PYTHON} ${PYSETUP} install --prefix=${PYPREFIX} 
--install-lib=${PYLIBDIR} --root=${DESTDIR} --version=${VERSION}
+ 
+ .PHONY: clean
+ ifndef VERBOSE
-- 
2.11.0

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

[yocto] [meta-security][PATCH] apparmor: fix Python install paths when target libdir != native libdir

[Ross Burton]

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb  |  4 ++--
 recipes-security/AppArmor/files/py-libdir.patch | 13 +
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 1e3a223..073b62d 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -80,9 +80,9 @@ do_install () {
install -d ${D}/${INIT_D_DIR}
install -d ${D}/lib/apparmor

-   oe_runmake -C ${B}/libraries/libapparmor DESTDIR="${D}" install
+   oe_runmake -C ${B}/libraries/libapparmor DESTDIR="${D}" 
PYLIBDIR=${PYTHON_SITEPACKAGES_DIR} install
oe_runmake -C ${B}/binutils DESTDIR="${D}" install
-   oe_runmake -C ${B}/utils DESTDIR="${D}" PYLIBDIR=${libdir} install
+   oe_runmake -C ${B}/utils DESTDIR="${D}" 
PYLIBDIR=${PYTHON_SITEPACKAGES_DIR} install
oe_runmake -C ${B}/parser DESTDIR="${D}" install
oe_runmake -C ${B}/profiles DESTDIR="${D}" install
 
diff --git a/recipes-security/AppArmor/files/py-libdir.patch 
b/recipes-security/AppArmor/files/py-libdir.patch
index fc617fb..2b88e54 100644
--- a/recipes-security/AppArmor/files/py-libdir.patch
+++ b/recipes-security/AppArmor/files/py-libdir.patch
@@ -4,6 +4,19 @@ python3-native's idea of $libdir may not match the target's 
$libdir.
 Upstream-Status: Pending
 Signed-off-by: Ross Burton 
 
+diff --git a/libraries/libapparmor/swig/python/Makefile.am 
b/libraries/libapparmor/swig/python/Makefile.am
+index 421acba9..d2b842a6 100644
+--- a/libraries/libapparmor/swig/python/Makefile.am
 b/libraries/libapparmor/swig/python/Makefile.am
+@@ -14,7 +14,7 @@ all-local: libapparmor_wrap.c setup.py
+   $(PYTHON) setup.py build
+ 
+ install-exec-local:
+-  $(PYTHON) setup.py install --root="/$(DESTDIR)" --prefix="$(prefix)"
++  $(PYTHON) setup.py install --root="/$(DESTDIR)" --prefix="$(prefix)" 
--install-lib="$(PYLIBDIR)"
+ 
+ clean-local:
+   if test -x "$(PYTHON)"; then $(PYTHON) setup.py clean; fi
 diff --git a/utils/Makefile b/utils/Makefile
 index 68f8c376..025f9da5 100644
 --- a/utils/Makefile
-- 
2.11.0

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

[yocto] [meta-security][PATCH 11/11] apparmor: backport a patch to fix tool paths instead of sedding

[Ross Burton]

Sedding is ugly, and as upstream have already fixed this cherry-pick the patch
instead.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb   |  3 +-
 recipes-security/AppArmor/files/tool-paths.patch | 37 
 2 files changed, 38 insertions(+), 2 deletions(-)
 create mode 100644 recipes-security/AppArmor/files/tool-paths.patch

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index ac03a56..efa93e6 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -17,6 +17,7 @@ SRC_URI = " \

http://archive.ubuntu.com/ubuntu/pool/main/a/${BPN}/${BPN}_${PV}.orig.tar.gz \
file://disable_perl_h_check.patch \
file://crosscompile_perl_bindings.patch \
+   file://tool-paths.patch \
file://apparmor.rc \
file://functions \
file://apparmor \
@@ -56,8 +57,6 @@ do_configure() {
libtoolize --automake -c --force
automake -ac
./configure ${CONFIGUREOPTS} ${EXTRA_OECONF}
-   sed -i -e 's#^YACC.*#YACC := bison#' ${S}/parser/Makefile
-   sed -i -e 's#^LEX.*#LEX := flex#' ${S}/parser/Makefile
 }
 
 do_compile () {
diff --git a/recipes-security/AppArmor/files/tool-paths.patch 
b/recipes-security/AppArmor/files/tool-paths.patch
new file mode 100644
index 000..aaf08da
--- /dev/null
+++ b/recipes-security/AppArmor/files/tool-paths.patch
@@ -0,0 +1,37 @@
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From e7edd937adcbf1b3c8d38a31de5bacb2029b1965 Mon Sep 17 00:00:00 2001
+From: John Johansen 
+Date: Thu, 4 Oct 2018 23:15:28 -0700
+Subject: [PATCH] parser: fix Makefile hardcoded paths to flex and bison
+
+The hardcoded paths for flex and python can break builds on systems
+where those tools are stored in an alternate location. Use which
+to lookup where flex and bison are available.
+
+This fixes issue #4
+
+Signed-off-by: John Johansen 
+---
+ parser/Makefile | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/parser/Makefile b/parser/Makefile
+index 4d370c36..015c218d 100644
+--- a/parser/Makefile
 b/parser/Makefile
+@@ -27,9 +27,9 @@ INSTALL_CONFDIR=${DESTDIR}${CONFDIR}
+ LOCALEDIR=/usr/share/locale
+ MANPAGES=apparmor.d.5 apparmor.7 apparmor_parser.8 subdomain.conf.5
+ 
+-YACC  := /usr/bin/bison
++YACC  := bison
+ YFLAGS:= -d
+-LEX   := /usr/bin/flex
++LEX   := flex
+ LEXFLAGS = -B -v
+ WARNINGS = -Wall
+ EXTRA_WARNINGS = -Wsign-compare -Wmissing-field-initializers 
-Wformat-security -Wunused-parameter
+-- 
+2.11.0
-- 
2.11.0

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

[yocto] [meta-security][PATCH 10/11] apparmor: if Perl is disabled remove perl-using scripts

[Ross Burton]

aa-notify uses the Perl bindings, so isn't usable when perl is disabled.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 92602f3..ac03a56 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -86,6 +86,11 @@ do_install () {
oe_runmake -C ${B}/parser DESTDIR="${D}" install
oe_runmake -C ${B}/profiles DESTDIR="${D}" install
 
+   # If perl is disabled this script won't be any good
+   if ! ${@bb.utils.contains('PACKAGECONFIG','perl','true','false', d)}; 
then
+   rm -f ${D}${sbindir}/aa-notify
+   fi
+
if test -z "${HTTPD}" ; then
oe_runmake -C ${B}/changehat/mod_apparmor DESTDIR="${D}" install
fi
-- 
2.11.0

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

[yocto] [meta-security][PATCH 09/11] apparmor: systemd.bbclas is useful even when disabled

[Ross Burton]

The systemd bbclass will remove any systemd files that have been installed if
systemd is disabled, so always install the files and always inherit.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 10 +++---
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 39c45e5..92602f3 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -29,8 +29,7 @@ SRC_URI[sha256sum] = 
"8a2b0cd083faa4d0640f579024be3a629faa7db3b99540798a1a050e2e
 
 PARALLEL_MAKE = ""
 
-inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan manpages
-inherit 
${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
+inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan manpages systemd
 
 PACKAGECONFIG ??= "python perl"
 PACKAGECONFIG[manpages] = "--enable-man-pages, --disable-man-pages"
@@ -101,11 +100,8 @@ do_install () {
 
install ${WORKDIR}/apparmor ${D}/${INIT_D_DIR}/apparmor
install ${WORKDIR}/functions ${D}/lib/apparmor
-   if [ "${VIRTUAL-RUNTIME_init_manager}" = "systemd" ]; then
-   install -d ${D}${systemd_system_unitdir}
-   install ${WORKDIR}/apparmor.service \
-   ${D}${systemd_system_unitdir}
-   fi
+   install -d ${D}${systemd_system_unitdir}
+   install ${WORKDIR}/apparmor.service ${D}${systemd_system_unitdir}
 }
 
 do_compile_ptest () {
-- 
2.11.0

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

[yocto] [meta-security][PATCH 08/11] apparmor: remove pointless ALLOW_EMPTY

[Ross Burton]

${PN} has content, so there's no need to set ALLOW_EMPTY_${PN}.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index b5ac613..39c45e5 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -148,8 +148,6 @@ PACKAGES += "mod-${PN}"
 FILES_${PN} += "/lib/apparmor/ ${sysconfdir}/apparmor 
${PYTHON_SITEPACKAGES_DIR}"
 FILES_mod-${PN} = "${libdir}/apache2/modules/*"
 
-ALLOW_EMPTY_${PN} = "1"
-
 RDEPENDS_${PN} += "bash lsb"
 RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3 
python3-modules','', d)}"
 RDEPENDS_${PN}_remove += 
"${@bb.utils.contains('PACKAGECONFIG','perl','','perl', d)}"
-- 
2.11.0

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

[yocto] [meta-security][PATCH 07/11] apparmor: no need to conditionalise PACKAGES

[Ross Burton]

A package with no content is not generated, so there's no need to conditionalise
assignments to PACKAGES.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 529414f..b5ac613 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -143,7 +143,7 @@ SYSTEMD_PACKAGES = "${PN}"
 SYSTEMD_SERVICE_${PN} = "apparmor.service"
 SYSTEMD_AUTO_ENABLE = "disable"
 
-PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'apache2', 'mod-${PN}', '', 
d)}"
+PACKAGES += "mod-${PN}"
 
 FILES_${PN} += "/lib/apparmor/ ${sysconfdir}/apparmor 
${PYTHON_SITEPACKAGES_DIR}"
 FILES_mod-${PN} = "${libdir}/apache2/modules/*"
-- 
2.11.0

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

[yocto] [meta-security][PATCH 06/11] apparmor: use manpages class

[Ross Burton]

The manpages class handles enabling/disabling the man pages based on the
api-documentation DISTRO_FEATURE, and ensures that mandb is called.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 6434e42..529414f 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -29,11 +29,11 @@ SRC_URI[sha256sum] = 
"8a2b0cd083faa4d0640f579024be3a629faa7db3b99540798a1a050e2e
 
 PARALLEL_MAKE = ""
 
-inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan
+inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan manpages
 inherit 
${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
 
-PACKAGECONFIG ?="man python perl"
-PACKAGECONFIG[man] = "--enable-man-pages, --disable-man-pages"
+PACKAGECONFIG ??= "python perl"
+PACKAGECONFIG[manpages] = "--enable-man-pages, --disable-man-pages"
 PACKAGECONFIG[python] = "--with-python, --without-python, python3 swig-native"
 PACKAGECONFIG[perl] = "--with-perl, --without-perl, perl perl-native 
swig-native"
 PACKAGECONFIG[apache2] = ",,apache2,"
-- 
2.11.0

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

[yocto] [meta-security][PATCH 05/11] apparmor: remove redundant S

[Ross Burton]

This is the default value, so remove it.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 303d5c7..6434e42 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -32,8 +32,6 @@ PARALLEL_MAKE = ""
 inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan
 inherit 
${@bb.utils.contains('VIRTUAL-RUNTIME_init_manager','systemd','systemd','', d)}
 
-S = "${WORKDIR}/apparmor-${PV}"
-
 PACKAGECONFIG ?="man python perl"
 PACKAGECONFIG[man] = "--enable-man-pages, --disable-man-pages"
 PACKAGECONFIG[python] = "--with-python, --without-python, python3 swig-native"
-- 
2.11.0

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

[yocto] [meta-security][PATCH 04/11] apparmor: enable static libraries neatly

[Ross Burton]

No need to fiddle with the configure arguments as we can just neuter
disable-static.inc.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index 2cf5b7d..303d5c7 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -50,8 +50,7 @@ python() {
 raise bb.parse.SkipRecipe('Requires meta-webserver to be present.')
 }
 
-CONFIGUREOPTS_remove = "--disable-static"
-EXTRA_OECONF_append = " --enable-static"
+DISABLE_STATIC = ""
 
 do_configure() {
cd ${S}/libraries/libapparmor
-- 
2.11.0

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

[yocto] [meta-security][PATCH 03/11] apparmor: add missing bash dependency

[Ross Burton]

testsuite/parser/tst/minimize.sh is a bash script, so until it is reviewed add a
bash dependency to apparmor-ptest.

Signed-off-by: Ross Burton 
---
 recipes-security/AppArmor/apparmor_2.12.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/AppArmor/apparmor_2.12.bb 
b/recipes-security/AppArmor/apparmor_2.12.bb
index e3f8dc9..2cf5b7d 100644
--- a/recipes-security/AppArmor/apparmor_2.12.bb
+++ b/recipes-security/AppArmor/apparmor_2.12.bb
@@ -156,4 +156,4 @@ ALLOW_EMPTY_${PN} = "1"
 RDEPENDS_${PN} += "bash lsb"
 RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3 
python3-modules','', d)}"
 RDEPENDS_${PN}_remove += 
"${@bb.utils.contains('PACKAGECONFIG','perl','','perl', d)}"
-RDEPENDS_${PN}-ptest += "perl coreutils dbus-lib"
+RDEPENDS_${PN}-ptest += "perl coreutils dbus-lib bash"
-- 
2.11.0

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

[yocto] [meta-security][PATCH 02/11] README: remove Saul from maintainers

[Ross Burton]

Signed-off-by: Ross Burton 
---
 README | 1 -
 1 file changed, 1 deletion(-)

diff --git a/README b/README
index c15fea9..5abb0e2 100644
--- a/README
+++ b/README
@@ -65,7 +65,6 @@ $ git config format.subjectPrefix meta-security][PATCH
 Now you can just do 'git send-email origin/master' to send all local patches.
 
 Maintainers:Armin Kuster 
-Saul Wold 
 
 
 License
-- 
2.11.0

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

[yocto] [meta-security][PATCH 01/11] README: add git-config tips

[Ross Burton]

Signed-off-by: Ross Burton 
---
 README | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/README b/README
index e238271..c15fea9 100644
--- a/README
+++ b/README
@@ -57,6 +57,13 @@ Send pull requests, patches, comments or questions to 
yocto@yoctoproject.org
 When sending single patches, please using something like:
 'git send-email -1 --to yocto@yoctoproject.org 
--subject-prefix=meta-security][PATCH'
 
+These values can be set as defaults for this repository:
+
+$ git config sendemail.to yocto@yoctoproject.org
+$ git config format.subjectPrefix meta-security][PATCH
+
+Now you can just do 'git send-email origin/master' to send all local patches.
+
 Maintainers:Armin Kuster 
 Saul Wold 
 
-- 
2.11.0

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

[yocto] [PATCH meta-mingw] packagegroup-sdk-host: add Make

[Ross Burton]

Make is useful, so add it to the SDK.

Signed-off-by: Ross Burton 
---
 recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend 
b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
index ad69b13..a9a51a6 100644
--- a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
+++ b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
@@ -2,4 +2,5 @@ RDEPENDS_${PN}_mingw32 = "\
 nativesdk-pkgconfig \
 nativesdk-libtool \
 nativesdk-qemu \
+nativesdk-make \
 "
-- 
2.11.0

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

[yocto] [PATCH pseudo] Makefile: add -lm when linking to sqlite3

[Ross Burton]

If sqlite3 is built with FTS5 then it needs log() from libm.so.  This is pulled
in automatically when dynamically linking as usual, or if static linking via
pkg-config. However as pseudo will link directly to libsqlite3.a this potential
linkage is lost and the build will fail with undefined symbols.

Solve this by always linking to libm.
---
 Makefile.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile.in b/Makefile.in
index ad6541b..28b5ecb 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -73,7 +73,7 @@ WRAPOBJS=pseudo_wrappers.o
 
 # needed for anything that links with pseduo_client.o, pretty much
 CLIENT_LDFLAGS=-ldl -lpthread
-DB_LDFLAGS=@SQLITE_LDARG@ -lpthread
+DB_LDFLAGS=@SQLITE_LDARG@ -lpthread -lm
 
 PSEUDO=$(BIN)/pseudo
 PSEUDODB=$(BIN)/pseudodb
-- 
2.11.0

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

[yocto] [PATCH pseudo 2/2] pseudo_client: move fallthrough comment to silence compiler warning

[Ross Burton]

---
 pseudo_client.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pseudo_client.c b/pseudo_client.c
index 5604cbf..e2ea715 100644
--- a/pseudo_client.c
+++ b/pseudo_client.c
@@ -1783,7 +1783,8 @@ pseudo_client_op(pseudo_op_t op, int access, int fd, int 
dirfd, const char *path
break;
case OP_OPEN:
pseudo_client_path(fd, path);
-   case OP_EXEC: /* fallthrough */
+   /* fallthrough */
+   case OP_EXEC:
do_request = pseudo_client_logging;
break;
case OP_CLOSE:
-- 
2.11.0

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

[yocto] [PATCH pseudo 1/2] pseudo_db: add missing stdint include

[Ross Burton]

---
 pseudo_db.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pseudo_db.c b/pseudo_db.c
index 0994048..31f4dc4 100644
--- a/pseudo_db.c
+++ b/pseudo_db.c
@@ -18,6 +18,7 @@
  *
  */
 #include 
+#include 
 #include 
 #include 
 #include 
-- 
2.11.0

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

[yocto] [PATCH meta-gplv2 2/2] coreutils: remove obsolete patches

[Ross Burton]

No point fixing small problems with the man pages build if we later disable them
entirely.

Signed-off-by: Ross Burton 
---
 .../coreutils-6.9/fix_for_manpage_building.patch   | 85 --
 .../coreutils/coreutils-6.9/man-touch.patch| 24 --
 recipes-core/coreutils/coreutils_6.9.bb|  2 -
 3 files changed, 111 deletions(-)
 delete mode 100644 
recipes-core/coreutils/coreutils-6.9/fix_for_manpage_building.patch
 delete mode 100644 recipes-core/coreutils/coreutils-6.9/man-touch.patch

diff --git 
a/recipes-core/coreutils/coreutils-6.9/fix_for_manpage_building.patch 
b/recipes-core/coreutils/coreutils-6.9/fix_for_manpage_building.patch
deleted file mode 100644
index e0d600a..000
--- a/recipes-core/coreutils/coreutils-6.9/fix_for_manpage_building.patch
+++ /dev/null
@@ -1,85 +0,0 @@
-Upstream-Status: Inappropriate [legacy version]
-
-Use native coreutils binaries to build manpages in cross environment.
-This avoids man page build issues like this:
-
-| Making all in man
-| make[1]: Entering directory 
`/build_disk/poky_build/build1/tmp/work/i586-poky-linux/coreutils-6.9-r0/coreutils-6.9/man'
-| Updating man page cut.1
-| Updating man page dir.1
-| Updating man page expand.1
-| Updating man page fold.1
-| Updating man page install.1
-| Updating man page join.1
-| Updating man page pr.1
-| Updating man page ls.1
-| Updating man page sort.1
-| Updating man page unexpand.1
-| Updating man page uniq.1
-| Updating man page who.1
-| Updating man page vdir.1
-| help2man: can't get `--help' info from dir.td/dir
-| help2man: can't get `--help' info from cut.td/cut
-| make[1]: *** [dir.1] Error 126
-| make[1]: *** Waiting for unfinished jobs
-| help2man: can't get `--help' info from fold.td/fold
-| help2man: can't get `--help' info from install.td/install
-| help2man: can't get `--help' info from expand.td/expand
-| help2man: can't get `--help' info from join.td/join
-| make[1]: *** [cut.1] Error 126
-| make[1]: *** [fold.1] Error 126
-| make[1]: *** [install.1] Error 126
-| help2man: can't get `--help' info from sort.td/sort
-| make[1]: *** [expand.1] Error 126
-| help2man: can't get `--help' info from pr.td/pr
-| make[1]: *** [join.1] Error 126
-| help2man: can't get `--help' info from ls.td/ls
-| help2man: can't get `--help' info from unexpand.td/unexpand
-| help2man: can't get `--help' info from uniq.td/uniq
-| help2man: can't get `--help' info from who.td/who
-| make[1]: *** [sort.1] Error 126
-| make[1]: *** [pr.1] Error 126
-| help2man: can't get `--help' info from vdir.td/vdir
-| make[1]: *** [ls.1] Error 126
-| make[1]: *** [uniq.1] Error 126
-| make[1]: *** [unexpand.1] Error 126
-| make[1]: *** [who.1] Error 126
-| make[1]: *** [vdir.1] Error 126
-| make[1]: Leaving directory 
`/build_disk/poky_build/build1/tmp/work/i586-poky-linux/coreutils-6.9-r0/coreutils-6.9/man'
-| make: *** [all-recursive] Error 1
-| FATAL: oe_runmake failed
-| ERROR: Function 'do_compile' failed (see 
/build_disk/poky_build/build1/tmp/work/i586-poky-linux/coreutils-6.9-r0/temp/log.do_compile.12780
 for further information)
-NOTE: package coreutils-6.9-r0: task do_compile: Failed
-ERROR: Task 8 
(/home/nitin/prj/poky.git/meta/recipes-core/coreutils/coreutils_6.9.bb, 
do_compile) failed with exit code '1'
-
-
-This patch is made for gplv2 coreutils the recipe
-Nitin A Kamble 
-2011/03/17
-
-Index: man/Makefile.am
-===
 a/man.orig/Makefile.am
-+++ b/man/Makefile.am
-@@ -167,7 +167,7 @@ mapped_name = `echo $*|sed 's/install/gi
-   $(PERL) -- $(srcdir)/help2man   \
---source='$(PACKAGE_STRING)'   \
---include=$(srcdir)/$*.x   \
--   --output=$t/$@ $t/$*;  \
-+   --output=$t/$@ $*; \
-  }\
-   && sed 's|$*\.td/||g' $t/$@ > $@\
-   && chmod a-w $@ \
-Index: man/Makefile.in
-===
 a/man.orig/Makefile.in
-+++ b/man/Makefile.in
-@@ -865,7 +865,7 @@ yes.1: $(common_dep)   $(srcdir)/yes.x 
.
-   $(PERL) -- $(srcdir)/help2man   \
---source='$(PACKAGE_STRING)'   \
---include=$(srcdir)/$*.x   \
--   --output=$t/$@ $t/$*;  \
-+   --output=$t/$@ $*; \
-  }\
-   && sed 's|$*\.td/||g' $t/$@ > $@\
-   && chmod a-w $@ \
diff --git a/recipes-core/coreutils/coreutils-6.9/man-touch.patch 
b/recipes-core/coreutils/coreutils-6.9/man-touch.patch

[yocto] [PATCH meta-gplv2 1/2] coreutils: don't build su

[Ross Burton]

Previously we built su but didn't package it because util-linux is the preferred
provider.  However with glibc 2.28 libcrypt has been removed so su doesn't
build.  Instead of depending on virtual/crypt, lets just not build su at all.

Signed-off-by: Ross Burton 
---
 recipes-core/coreutils/coreutils-6.9/no-su.patch | 56 
 recipes-core/coreutils/coreutils_6.9.bb  |  5 +--
 2 files changed, 57 insertions(+), 4 deletions(-)
 create mode 100644 recipes-core/coreutils/coreutils-6.9/no-su.patch

diff --git a/recipes-core/coreutils/coreutils-6.9/no-su.patch 
b/recipes-core/coreutils/coreutils-6.9/no-su.patch
new file mode 100644
index 000..47339e5
--- /dev/null
+++ b/recipes-core/coreutils/coreutils-6.9/no-su.patch
@@ -0,0 +1,56 @@
+Newer versions of su don't provide su as util-linux is the preferred provider,
+so don't build it.
+
+Upstream-Status: Inappropriate
+Signed-off-by: Ross Burton 
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 863a32b5a..28c060898 100644
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -16,7 +16,7 @@
+ ## along with this program; if not, write to the Free Software Foundation,
+ ## Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ 
+-EXTRA_PROGRAMS = chroot df hostid nice pinky stty su uname uptime users who
++EXTRA_PROGRAMS = chroot df hostid nice pinky stty uname uptime users who
+ 
+ bin_SCRIPTS = groups
+ bin_PROGRAMS = [ chgrp chown chmod cp dd dircolors du \
+@@ -131,8 +131,6 @@ RELEASE_YEAR = \
+   chmod +x $@-t
+   mv $@-t $@
+ 
+-all-local: su$(EXEEXT)
+-
+ installed_su = $(DESTDIR)$(bindir)/`echo su|sed '$(transform)'`
+ 
+ setuid_root_mode = a=rx,u+s
+@@ -146,27 +144,6 @@ INSTALL_SU = \
+   echo " chmod $(setuid_root_mode) $(installed_su)"; \
+   chmod $(setuid_root_mode) $(installed_su)
+ 
+-install-root: su$(EXEEXT)
+-  @$(INSTALL_SU)
+-
+-install-exec-local: su$(EXEEXT)
+-  @TMPFILE=$(DESTDIR)$(bindir)/.su-; \
+-  rm -f $$TMPFILE; \
+-  echo > $$TMPFILE; \
+-## See if we can create a setuid root executable in $(bindir).
+-## If not, then don't even try to install su.
+-  can_create_suid_root_executable=no; \
+-  chown root $$TMPFILE > /dev/null 2>&1 \
+-&& chmod $(setuid_root_mode) $$TMPFILE > /dev/null 2>&1 \
+-&& can_create_suid_root_executable=yes; \
+-  rm -f $$TMPFILE; \
+-  if test $$can_create_suid_root_executable = yes; then \
+-$(INSTALL_SU); \
+-  else \
+-echo "WARNING: insufficient access; not installing su"; \
+-echo "NOTE: to install su, run 'make install-root' as root"; \
+-  fi
+-
+ uninstall-local:
+ # Remove su only if it's one we installed.
+   @if grep '$(GNU_PACKAGE)' $(installed_su) > /dev/null 2>&1; then \
diff --git a/recipes-core/coreutils/coreutils_6.9.bb 
b/recipes-core/coreutils/coreutils_6.9.bb
index 0d236b2..ae941fd 100644
--- a/recipes-core/coreutils/coreutils_6.9.bb
+++ b/recipes-core/coreutils/coreutils_6.9.bb
@@ -28,6 +28,7 @@ SRC_URI = "${GNU_MIRROR}/coreutils/${BP}.tar.bz2 \
file://loadavg.patch \
file://no-man.patch \
file://build-don-t-need-charset.alias-when-building-for-mus.patch \
+   file://no-su.patch \
"
 
 SRC_URI[md5sum] = "c9607d8495f16e98906e7ed2d9751a06"
@@ -78,10 +79,6 @@ do_install() {
# in update-alternatives to fail, therefore use lbracket - the name used
# for the actual source file.
mv ${D}${bindir}/[ ${D}${bindir}/lbracket.${BPN}
-
-   # Newer versions of coreutils do not include su, to mimic this behavior
-   # we simply remove it.
-   rm -f ${D}${bindir}/su
 }
 
 inherit update-alternatives
-- 
2.11.0

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

[yocto] [PATCH meta-gplv2] bc: add

[Ross Burton]

Add 1.06 from oe-core as bc 1.07 is GPLv3.

Signed-off-by: Ross Burton 
---
 recipes-extended/bc/bc_1.06.bb| 26 +
 recipes-extended/bc/files/fix-segment-fault.patch | 28 +++
 2 files changed, 54 insertions(+)
 create mode 100644 recipes-extended/bc/bc_1.06.bb
 create mode 100644 recipes-extended/bc/files/fix-segment-fault.patch

diff --git a/recipes-extended/bc/bc_1.06.bb b/recipes-extended/bc/bc_1.06.bb
new file mode 100644
index 000..d8c8a86
--- /dev/null
+++ b/recipes-extended/bc/bc_1.06.bb
@@ -0,0 +1,26 @@
+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/recipes-extended/bc/files/fix-segment-fault.patch 
b/recipes-extended/bc/files/fix-segment-fault.patch
new file mode 100644
index 000..20c0da2
--- /dev/null
+++ b/recipes-extended/bc/files/fix-segment-fault.patch
@@ -0,0 +1,28 @@
+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.11.0

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

[yocto] [PATCH][meta-mingw] libsdl2: add bbappend to fix build with mingw

[Ross Burton]

We need to disable X11 as we do with libsdl1, and also convince libtool to stop
trying to be clever so the build doesn't break.

Signed-off-by: Ross Burton 
---
 recipes-graphics/libsdl2/libsdl2_%.bbappend | 10 ++
 1 file changed, 10 insertions(+)
 create mode 100644 recipes-graphics/libsdl2/libsdl2_%.bbappend

diff --git a/recipes-graphics/libsdl2/libsdl2_%.bbappend 
b/recipes-graphics/libsdl2/libsdl2_%.bbappend
new file mode 100644
index 000..97fd96e
--- /dev/null
+++ b/recipes-graphics/libsdl2/libsdl2_%.bbappend
@@ -0,0 +1,10 @@
+PACKAGECONFIG_remove_mingw32_class-nativesdk = "x11"
+
+# libtool doesn't think it can link windres output (COFF) with libtool objects
+# (COFF) , but it can.  This might be because file misidentifies version.o:
+#
+# version.o: Targa image data - Map (0) 1 x 65536 x 0 +862 "\004\001.rsrc"
+#
+# Telling libtool to be dumb and just pass the input to the underlying tools
+# works fine.
+EXTRA_OECONF_append_mingw32 = " lt_cv_deplibs_check_method=pass_all"
-- 
2.11.0

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

[yocto] [PATCH][pseudo] makewrappers: use correct except syntax

[Ross Burton]

except Exception(e): causes a NameError if an exception is caught.
---
 makewrappers | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/makewrappers b/makewrappers
index fa514ba..1927f75 100755
--- a/makewrappers
+++ b/makewrappers
@@ -578,7 +578,7 @@ def process_wrapfuncs(port):
 func.directory = directory
 funcs[func.name] = func
 sys.stdout.write(".")
-except Exception(e):
+except Exception as e:
 print("Parsing failed:", e)
 exit(1)
 funclist.close()
-- 
2.11.0

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

[yocto] [PATCH V2][meta-mingw] machine-sdk: split out common configuration

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 conf/machine-sdk/i686-mingw32.conf  | 36 +
 conf/machine-sdk/include/mingw32-common.inc | 36 +
 conf/machine-sdk/x86_64-mingw32.conf| 36 +
 3 files changed, 38 insertions(+), 70 deletions(-)
 create mode 100644 conf/machine-sdk/include/mingw32-common.inc

diff --git a/conf/machine-sdk/i686-mingw32.conf 
b/conf/machine-sdk/i686-mingw32.conf
index f85b05d..5090168 100644
--- a/conf/machine-sdk/i686-mingw32.conf
+++ b/conf/machine-sdk/i686-mingw32.conf
@@ -1,37 +1,3 @@
 SDK_ARCH = "i686"
-SDK_OS = "mingw32"
 
-GCCTHREADS_mingw32 = "win32"
-
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
-PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
-
-USE_NLS_mingw32 = "no"
-
-FILES_${PN}-staticdev_append_mingw32 = " ${libdir}/*.lib"
-ALLOW_EMPTY_${PN}_mingw32 = "1"
-
-# Do what amounts to a NOOP
-SDK_PACKAGING_FUNC = "do_compile"
-
-# Causes an endless loop
-#SDKTAROPTS_append = " -h --hard-dereference"
-
-SDKUSE_NLS = "no"
-SDKIMAGE_LINGUAS = ""
-SDK_DEPENDS_remove = "nativesdk-glibc-locale"
-
-SDKPKGSUFFIX = "nativesdk-mingw32"
-
-MACHINEOVERRIDES .= ":sdkmingw32"
-
-export WINDRES = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
-export RC = "${WINDRES}"
-
-BB_HASHBASE_WHITELIST_append = " WINDRES RC"
-
-# Needed to override no-static-libs.inc
-DISABLE_STATIC_mingw32 = ""
+require conf/machine-sdk/include/mingw32-common.inc
diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
new file mode 100644
index 000..53bac4c
--- /dev/null
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -0,0 +1,36 @@
+SDK_OS = "mingw32"
+
+GCCTHREADS_mingw32 = "win32"
+
+PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
+PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
+
+USE_NLS_mingw32 = "no"
+
+FILES_${PN}-staticdev_append_mingw32 = " ${libdir}/*.lib"
+ALLOW_EMPTY_${PN}_mingw32 = "1"
+
+# Do what amounts to a NOOP
+SDK_PACKAGING_FUNC = "do_compile"
+
+# Causes an endless loop
+#SDKTAROPTS_append = " -h --hard-dereference"
+
+SDKUSE_NLS = "no"
+SDKIMAGE_LINGUAS = ""
+SDK_DEPENDS_remove = "nativesdk-glibc-locale"
+
+SDKPKGSUFFIX = "nativesdk-mingw32"
+
+MACHINEOVERRIDES .= ":sdkmingw32"
+
+export WINDRES = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
+export RC = "${WINDRES}"
+
+BB_HASHBASE_WHITELIST_append = " WINDRES RC"
+
+# Needed to override no-static-libs.inc
+DISABLE_STATIC_mingw32 = ""
diff --git a/conf/machine-sdk/x86_64-mingw32.conf 
b/conf/machine-sdk/x86_64-mingw32.conf
index ec801c3..fc53822 100644
--- a/conf/machine-sdk/x86_64-mingw32.conf
+++ b/conf/machine-sdk/x86_64-mingw32.conf
@@ -1,37 +1,3 @@
 SDK_ARCH = "x86_64"
-SDK_OS = "mingw32"
 
-GCCTHREADS_mingw32 = "win32"
-
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
-PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
-
-USE_NLS_mingw32 = "no"
-
-FILES_${PN}-staticdev_append_mingw32 = " ${libdir}/*.lib"
-ALLOW_EMPTY_${PN}_mingw32 = "1"
-
-# Do what amounts to a NOOP
-SDK_PACKAGING_FUNC = "do_compile"
-
-# Causes an endless loop
-#SDKTAROPTS_append = " -h --hard-dereference"
-
-SDKUSE_NLS = "no"
-SDKIMAGE_LINGUAS = ""
-SDK_DEPENDS_remove = "nativesdk-glibc-locale"
-
-SDKPKGSUFFIX = "nativesdk-mingw32"
-
-MACHINEOVERRIDES .= ":sdkmingw32"
-
-export WINDRES = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
-export RC = "${WINDRES}"
-
-BB_HASHBASE_WHITELIST_append = " WINDRES RC"
-
-# Needed to override no-static-libs.inc
-DISABLE_STATIC_mingw32 = ""
+require conf/machine-sdk/include/mingw32-common.inc
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw 2/2] machine-sdk: set the nativesdk libc to libc-mingw

[Ross Burton]

We need to set this so that the override for nativesdk builds using MinGW don't
think they're using glibc.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 conf/machine-sdk/include/mingw32-common.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
index 53bac4c..07b103a 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -1,4 +1,5 @@
 SDK_OS = "mingw32"
+NATIVESDKLIBC = "libc-mingw"
 
 GCCTHREADS_mingw32 = "win32"
 
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw 1/2] machine-sdk: split out common configuration

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 conf/machine-sdk/i686-mingw32.conf  | 36 +
 conf/machine-sdk/include/mingw32-common.inc | 36 +
 2 files changed, 37 insertions(+), 35 deletions(-)
 create mode 100644 conf/machine-sdk/include/mingw32-common.inc

diff --git a/conf/machine-sdk/i686-mingw32.conf 
b/conf/machine-sdk/i686-mingw32.conf
index f85b05d..5090168 100644
--- a/conf/machine-sdk/i686-mingw32.conf
+++ b/conf/machine-sdk/i686-mingw32.conf
@@ -1,37 +1,3 @@
 SDK_ARCH = "i686"
-SDK_OS = "mingw32"
 
-GCCTHREADS_mingw32 = "win32"
-
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
-PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
-
-USE_NLS_mingw32 = "no"
-
-FILES_${PN}-staticdev_append_mingw32 = " ${libdir}/*.lib"
-ALLOW_EMPTY_${PN}_mingw32 = "1"
-
-# Do what amounts to a NOOP
-SDK_PACKAGING_FUNC = "do_compile"
-
-# Causes an endless loop
-#SDKTAROPTS_append = " -h --hard-dereference"
-
-SDKUSE_NLS = "no"
-SDKIMAGE_LINGUAS = ""
-SDK_DEPENDS_remove = "nativesdk-glibc-locale"
-
-SDKPKGSUFFIX = "nativesdk-mingw32"
-
-MACHINEOVERRIDES .= ":sdkmingw32"
-
-export WINDRES = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
-export RC = "${WINDRES}"
-
-BB_HASHBASE_WHITELIST_append = " WINDRES RC"
-
-# Needed to override no-static-libs.inc
-DISABLE_STATIC_mingw32 = ""
+require conf/machine-sdk/include/mingw32-common.inc
diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
new file mode 100644
index 000..53bac4c
--- /dev/null
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -0,0 +1,36 @@
+SDK_OS = "mingw32"
+
+GCCTHREADS_mingw32 = "win32"
+
+PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
+PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
+
+USE_NLS_mingw32 = "no"
+
+FILES_${PN}-staticdev_append_mingw32 = " ${libdir}/*.lib"
+ALLOW_EMPTY_${PN}_mingw32 = "1"
+
+# Do what amounts to a NOOP
+SDK_PACKAGING_FUNC = "do_compile"
+
+# Causes an endless loop
+#SDKTAROPTS_append = " -h --hard-dereference"
+
+SDKUSE_NLS = "no"
+SDKIMAGE_LINGUAS = ""
+SDK_DEPENDS_remove = "nativesdk-glibc-locale"
+
+SDKPKGSUFFIX = "nativesdk-mingw32"
+
+MACHINEOVERRIDES .= ":sdkmingw32"
+
+export WINDRES = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
+export RC = "${WINDRES}"
+
+BB_HASHBASE_WHITELIST_append = " WINDRES RC"
+
+# Needed to override no-static-libs.inc
+DISABLE_STATIC_mingw32 = ""
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] diffutils: update sdiff kill() patch to be a backport

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 .../diffutils/diffutils/sdiff-no-kill.patch| 30 --
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch 
b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
index 70e7caf..c9fbc24 100644
--- a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
+++ b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
@@ -1,18 +1,32 @@
-"kill" is not supported by mingw, so compile conditionally,
-(same condition as another instance of "kill" in the source code).
+Upstream-Status: Backport
+Signed-off-by: Ross Burton <ross.bur...@intel.com>
 
-Upstream-Status: Pending
-Signed-off-by: Juro Bystricky <juro.bystri...@intel.com>
+From 56225ecca4f9598c0c9dbd7c46a51dd4816a383f Mon Sep 17 00:00:00 2001
+From: Paul Eggert <egg...@cs.ucla.edu>
+Date: Fri, 20 Apr 2018 13:39:15 -0700
+Subject: sdiff: port to mingw
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
 
+Problem reported by Ross Burton (Bug#31218).
+* src/sdiff.c (checksigs): Use ‘raise’, not ‘kill’.
+---
+ src/sdiff.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sdiff.c b/src/sdiff.c
+index 1b23a0c..b08bc74 100644
 --- a/src/sdiff.c
 +++ b/src/sdiff.c
-@@ -805,7 +805,9 @@
+@@ -805,7 +805,7 @@ checksigs (void)
  
/* Yield an exit status indicating that a signal was received.  */
untrapsig (s);
-+#if HAVE_WORKING_FORK
-   kill (getpid (), s);
-+#endif
+-  kill (getpid (), s);
++  raise (s);
  
/* That didn't work, so exit with error status.  */
exit (EXIT_TROUBLE);
+-- 
+cgit v1.0-41-gc330
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] libmpc: use wildcard version

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 recipes-support/libmpc/{libmpc_1.0.3.bbappend => libmpc_%.bbappend} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-support/libmpc/{libmpc_1.0.3.bbappend => libmpc_%.bbappend} 
(100%)

diff --git a/recipes-support/libmpc/libmpc_1.0.3.bbappend 
b/recipes-support/libmpc/libmpc_%.bbappend
similarity index 100%
rename from recipes-support/libmpc/libmpc_1.0.3.bbappend
rename to recipes-support/libmpc/libmpc_%.bbappend
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] binutils: generalise version wildcard

[Ross Burton]

Don't be overly specific by demanding 2.2%, 2.% is sufficient as this bbappend
simply changes some options.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 ...-cross-canadian_2.2%.bbappend => binutils-cross-canadian_2.%.bbappend} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-devtools/binutils/{binutils-cross-canadian_2.2%.bbappend => 
binutils-cross-canadian_2.%.bbappend} (100%)

diff --git a/recipes-devtools/binutils/binutils-cross-canadian_2.2%.bbappend 
b/recipes-devtools/binutils/binutils-cross-canadian_2.%.bbappend
similarity index 100%
rename from recipes-devtools/binutils/binutils-cross-canadian_2.2%.bbappend
rename to recipes-devtools/binutils/binutils-cross-canadian_2.%.bbappend
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] gcc-crosssdk: use _remove instead of oe.utils.str_filter_out

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 recipes-devtools/gcc/gcc-crosssdk_%.bbappend | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/recipes-devtools/gcc/gcc-crosssdk_%.bbappend 
b/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
index d52a16b..3411946 100644
--- a/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
+++ b/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
@@ -1,4 +1,3 @@
-EXTRA_OECONF_mingw32 := 
"${@oe.utils.str_filter_out('--with-linker-hash-style=${LINKER_HASH_STYLE}', 
'${EXTRA_OECONF}', d)}"
 PACKAGECONFIG_CONFARGS ?= ""
-EXTRA_OECONF_remove_mingw32 = "--enable-initfini-array"
+EXTRA_OECONF_remove_mingw32 = "--enable-initfini-array 
--with-linker-hash-style=${LINKER_HASH_STYLE}"
 EXTRA_OECONF_append_mingw32 = " --disable-initfini-array"
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] gcc-crosssdk: use oe.utils.str_filter_out

[Ross Burton]

oe_filter_out has been removed from oe-core so use the replacement function.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 recipes-devtools/gcc/gcc-crosssdk_%.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-devtools/gcc/gcc-crosssdk_%.bbappend 
b/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
index b3b843a..d52a16b 100644
--- a/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
+++ b/recipes-devtools/gcc/gcc-crosssdk_%.bbappend
@@ -1,4 +1,4 @@
-EXTRA_OECONF_mingw32 := 
"${@oe_filter_out('--with-linker-hash-style=${LINKER_HASH_STYLE}', 
'${EXTRA_OECONF}', d)}"
+EXTRA_OECONF_mingw32 := 
"${@oe.utils.str_filter_out('--with-linker-hash-style=${LINKER_HASH_STYLE}', 
'${EXTRA_OECONF}', d)}"
 PACKAGECONFIG_CONFARGS ?= ""
 EXTRA_OECONF_remove_mingw32 = "--enable-initfini-array"
 EXTRA_OECONF_append_mingw32 = " --disable-initfini-array"
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] machine-sdk: use gettext for libintl, not mingw-runtime

[Ross Burton]

The MinGW runtime doesn't provide libintl, so set gettext as the preferred
provider for libintl.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 conf/machine-sdk/i686-mingw32.conf   | 3 +--
 conf/machine-sdk/x86_64-mingw32.conf | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/conf/machine-sdk/i686-mingw32.conf 
b/conf/machine-sdk/i686-mingw32.conf
index d426fe3..cb08bee 100644
--- a/conf/machine-sdk/i686-mingw32.conf
+++ b/conf/machine-sdk/i686-mingw32.conf
@@ -6,7 +6,7 @@ GCCTHREADS_mingw32 = "win32"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
 PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
 PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
 
 USE_NLS_mingw32 = "no"
@@ -33,4 +33,3 @@ BB_HASHBASE_WHITELIST_append = " WINDRES RC"
 
 # Needed to override no-static-libs.inc
 DISABLE_STATIC_mingw32 = ""
-
diff --git a/conf/machine-sdk/x86_64-mingw32.conf 
b/conf/machine-sdk/x86_64-mingw32.conf
index b9706f9..8786413 100644
--- a/conf/machine-sdk/x86_64-mingw32.conf
+++ b/conf/machine-sdk/x86_64-mingw32.conf
@@ -6,7 +6,7 @@ GCCTHREADS_mingw32 = "win32"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = 
"nativesdk-mingw-w64-runtime"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial_mingw32 = 
"nativesdk-mingw-w64-runtime"
 PREFERRED_PROVIDER_virtual/nativesdk-libc = "nativesdk-mingw-w64-runtime"
-PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-mingw-w64-runtime"
+PREFERRED_PROVIDER_virtual/nativesdk-libintl = "nativesdk-gettext"
 PREFERRED_PROVIDER_virtual/nativesdk-libiconv = "nativesdk-libiconv"
 
 USE_NLS_mingw32 = "no"
@@ -33,4 +33,3 @@ BB_HASHBASE_WHITELIST_append = " WINDRES RC"
 
 # Needed to override no-static-libs.inc
 DISABLE_STATIC_mingw32 = ""
-
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] libgcrypt: generalise bbappend

[Ross Burton]

---
 .../libgcrypt/{libgcrypt_1.7.6.bbappend => libgcrypt_1.7.%.bbappend}  | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-support/libgcrypt/{libgcrypt_1.7.6.bbappend => 
libgcrypt_1.7.%.bbappend} (100%)

diff --git a/recipes-support/libgcrypt/libgcrypt_1.7.6.bbappend 
b/recipes-support/libgcrypt/libgcrypt_1.7.%.bbappend
similarity index 100%
rename from recipes-support/libgcrypt/libgcrypt_1.7.6.bbappend
rename to recipes-support/libgcrypt/libgcrypt_1.7.%.bbappend
-- 
2.11.0

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

[yocto] [PATCH][meta-mingw] gdb-cross-canadian: generalise wildcard to work for all versions

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 .../{gdb-cross-canadian_7.%.bbappend => gdb-cross-canadian_%.bbappend}| 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-devtools/gdb/{gdb-cross-canadian_7.%.bbappend => 
gdb-cross-canadian_%.bbappend} (100%)

diff --git a/recipes-devtools/gdb/gdb-cross-canadian_7.%.bbappend 
b/recipes-devtools/gdb/gdb-cross-canadian_%.bbappend
similarity index 100%
rename from recipes-devtools/gdb/gdb-cross-canadian_7.%.bbappend
rename to recipes-devtools/gdb/gdb-cross-canadian_%.bbappend
-- 
2.8.1

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

[yocto] [PATCH][opkg 2/2] conffile: gracefully handle deleted conffiles in conffile_has_been_modified

[Ross Burton]

Handle conffiles that don't exist gracefully so that instead of showing an error
message from file_md5sum_alloc() a notice that the file has been deleted is
shown instead.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 libopkg/conffile.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/libopkg/conffile.c b/libopkg/conffile.c
index b2f2469..7b4b87b 100644
--- a/libopkg/conffile.c
+++ b/libopkg/conffile.c
@@ -51,6 +51,11 @@ int conffile_has_been_modified(conffile_t * conffile)
 }
 
 root_filename = root_filename_alloc(filename);
+if (!file_exists(root_filename)) {
+opkg_msg(INFO, "Conffile %s deleted\n", conffile->name);
+free(root_filename);
+return 1;
+}
 
 md5sum = file_md5sum_alloc(root_filename);
 
-- 
2.8.1

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

[yocto] [PATCH][opkg 1/2] opkg_cmd: only look at conffile status if we're going to output it

[Ross Burton]

The loop to compare the recorded conffile hash with their hash on disk is
outputted at level INFO but the loop was executed at level NOTICE and higher.

This means that if a conffile had been deleted the status operation would
produce error messages for output it isn't displaying.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 libopkg/opkg_cmd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libopkg/opkg_cmd.c b/libopkg/opkg_cmd.c
index ba57c6a..37416fd 100644
--- a/libopkg/opkg_cmd.c
+++ b/libopkg/opkg_cmd.c
@@ -638,7 +638,7 @@ static int opkg_info_status_cmd(int argc, char **argv, int 
installed_only)
 
 pkg_formatted_info(stdout, pkg);
 
-if (opkg_config->verbosity >= NOTICE) {
+if (opkg_config->verbosity >= INFO) {
 conffile_list_elt_t *iter;
 for (iter = nv_pair_list_first(>conffiles); iter;
  iter = nv_pair_list_next(>conffiles, iter)) {
-- 
2.8.1

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

[yocto] [PATCH][yocto-autobuilder] nightly-qa-extras: test the API documentation DISTRO_FEATURE

[Ross Burton]

Build the core-image-sato SDK with API documentation enabled to verify that this
doesn't regress.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-qa-extras.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/buildset-config.controller/nightly-qa-extras.conf 
b/buildset-config.controller/nightly-qa-extras.conf
index f796bb1..9f56f3b 100644
--- a/buildset-config.controller/nightly-qa-extras.conf
+++ b/buildset-config.controller/nightly-qa-extras.conf
@@ -19,5 +19,9 @@ steps: [{'SetDest':{}},
 'atextappend' : '\nROOT_HOME = "/root"\n'}},
 {'BuildImages': {'images': 'core-image-minimal'}},
 {'RunSanityTests': {'images': 'core-image-minimal'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'i686',
+'distro': 'poky', 'buildhistory' : False,
+'atextappend' : '\nDISTRO_FEATURES_append = " 
api-documentation"\n'}},
+{'BuildImages': {'images': 'core-image-sato:do_populate_sdk'}},
 {'DownloadErrorReports': {}},
 {'SendErrorReport': {}}]
-- 
2.8.1

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

[yocto] [PATCH][yocto-autobuilder] nightly-musl: build core-image-weston, only use ipkg

[Ross Burton]

Build core-image-weston for more coverage, and use ipkg explicitly as rpm is
known to break with musl.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-musl.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-musl.conf 
b/buildset-config.controller/nightly-musl.conf
index 9a82e6b..49ae91d 100644
--- a/buildset-config.controller/nightly-musl.conf
+++ b/buildset-config.controller/nightly-musl.conf
@@ -10,9 +10,10 @@ steps: [{'SetDest':{}},
 {'GetDistroVersion' : {'distro': 'poky'}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
 'buildhistory' : False, 'distro': 'poky',
+'packages': 'ipk',
 'atextappend' : '\nTCLIBC="musl"\n' }},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
-{'BuildImages': {'images':  'core-image-minimal 
core-image-full-cmdline core-image-sato'}},
+{'BuildImages': {'images':  'core-image-minimal 
core-image-full-cmdline core-image-sato core-image-weston'}},
 {'SendErrorReport': {}},
 {'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
 
-- 
2.7.0

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

[yocto] [PATCH][yocto-autobuilder] nightly-musl: also build core-image-weston

[Ross Burton]

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-musl.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-musl.conf 
b/buildset-config.controller/nightly-musl.conf
index 9a82e6b..5da90c3 100644
--- a/buildset-config.controller/nightly-musl.conf
+++ b/buildset-config.controller/nightly-musl.conf
@@ -12,7 +12,7 @@ steps: [{'SetDest':{}},
 'buildhistory' : False, 'distro': 'poky',
 'atextappend' : '\nTCLIBC="musl"\n' }},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
-{'BuildImages': {'images':  'core-image-minimal 
core-image-full-cmdline core-image-sato'}},
+{'BuildImages': {'images':  'core-image-minimal 
core-image-full-cmdline core-image-sato core-image-weston'}},
 {'SendErrorReport': {}},
 {'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
 
-- 
2.7.0

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

[yocto] [PATCH][yocto-autobuilder] nightly-checkuri: use a single bitbake thread

[Ross Burton]

To reduce the chance of errors due to FTP servers refusing multiple connections
at the same time reduce the number of bitbake threads to 1.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-checkuri.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-checkuri.conf 
b/buildset-config.controller/nightly-checkuri.conf
index b571429..37b8305 100644
--- a/buildset-config.controller/nightly-checkuri.conf
+++ b/buildset-config.controller/nightly-checkuri.conf
@@ -17,6 +17,6 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
 'distro': 'poky',
 'atextprepend': 'SOURCE_MIRROR_FETCH = "1"\n',
-'atextappend': 'do_checkuri_pn-lsof = ""\n'}},
+'atextappend': 'BB_NUMBER_THREADS = 
"1"\ndo_checkuri_pn-lsof = ""\n'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'universe -c checkuri'}}]
-- 
2.7.0

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

[yocto] [PATCH][yocto-autobuilder] nightly-world-lsb: blacklist qwt

[Ross Burton]

qwt (from meta-qt4) doesn't build without errors but gets pulled into world
poky-lsb builds.  Until this is fixed, blacklist it.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-world-lsb.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-world-lsb.conf 
b/buildset-config.controller/nightly-world-lsb.conf
index 7341f6c..df08e8d 100644
--- a/buildset-config.controller/nightly-world-lsb.conf
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -17,7 +17,7 @@ steps: [{'SetDest':{}},
 {'CheckForWorldLsb':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
 'buildhistory' : False, 'multilib': True,
-'atextprepend': 'QTDEMOS_remove = "qmmp"\n',
+'atextprepend': 'QTDEMOS_remove = 
"qmmp"\nPNBLACKLIST[qwt] = "already stripped errors"\n',
 'distro': 'poky-lsb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'world'}},
-- 
2.6.4

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

[yocto] [PATCH][yocto-autobuilder] nightly-checkuri.conf: exclude lsof, run against universe

[Ross Burton]

The lsof recipe needs to be excluded from our checkuri tests because the
upstream FTP server refuses to let the autobuilder machines connect to it.

Also run checkuri against universe instead of world to catch more variations on
recipe permuatations.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-checkuri.conf | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/buildset-config.controller/nightly-checkuri.conf 
b/buildset-config.controller/nightly-checkuri.conf
index 232f62c..b571429 100644
--- a/buildset-config.controller/nightly-checkuri.conf
+++ b/buildset-config.controller/nightly-checkuri.conf
@@ -16,6 +16,7 @@ steps: [{'SetDest':{}},
 {'GetDistroVersion' : {'distro': 'poky'}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
 'distro': 'poky',
-'atextprepend': 'SOURCE_MIRROR_FETCH = "1"\n'}},
+'atextprepend': 'SOURCE_MIRROR_FETCH = "1"\n',
+'atextappend': 'do_checkuri_pn-lsof = ""\n'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
-{'BuildImages': {'images': 'world -c checkuri'}}]
+{'BuildImages': {'images': 'universe -c checkuri'}}]
-- 
2.6.4

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

[yocto] [PATCH][meta-qt3] qt-x11-free: update SRC_URI

[Ross Burton]

ftp.trolltech.com doesn't exist anymore, so update SRC_URI to use qt.io.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 recipes-qt3/qt3/qt-x11-free_3.3.7.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-qt3/qt3/qt-x11-free_3.3.7.bb 
b/recipes-qt3/qt3/qt-x11-free_3.3.7.bb
index 89f976d..f90f9b9 100644
--- a/recipes-qt3/qt3/qt-x11-free_3.3.7.bb
+++ b/recipes-qt3/qt3/qt-x11-free_3.3.7.bb
@@ -5,7 +5,7 @@ PR = "${INC_PR}.1"
 LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=b07b0d5ac6b1822effe47173a1744433 \
 file://LICENSE.QPL;md5=b81b6b6fc04ed873adde5aa901c0613b"
 
-SRC_URI = "ftp://ftp.trolltech.com/qt/source/qt-x11-free-${PV}.tar.bz2 \
+SRC_URI = "http://download.qt.io/archive/qt/3/${BP}.tar.bz2 \
   file://configure.patch \
   file://no-examples.patch \
file://gcc4_1-HACK.patch \
-- 
2.6.4

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

[yocto] [PATCH][autobuilder 1/3] buildset-config.controller: remove unused meta-qt3 from buildsets

[Ross Burton]

Many buildsets pull in meta-qt3 but don't use it, so remove the layer from those
buildsets.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-arm.conf  | 3 ---
 buildset-config.controller/nightly-arm64.conf| 3 ---
 buildset-config.controller/nightly-deb-non-deb.conf  | 3 ---
 buildset-config.controller/nightly-deb.conf  | 3 ---
 buildset-config.controller/nightly-fsl-arm.conf  | 3 ---
 buildset-config.controller/nightly-fsl-ppc.conf  | 3 ---
 buildset-config.controller/nightly-ipk.conf  | 3 ---
 buildset-config.controller/nightly-mips.conf | 3 ---
 buildset-config.controller/nightly-mips64.conf   | 3 ---
 buildset-config.controller/nightly-multilib.conf | 3 ---
 buildset-config.controller/nightly-no-x11.conf   | 3 ---
 buildset-config.controller/nightly-non-gpl3.conf | 3 ---
 buildset-config.controller/nightly-oecore.conf   | 3 ---
 buildset-config.controller/nightly-ppc.conf  | 3 ---
 buildset-config.controller/nightly-rpm-non-rpm.conf  | 3 ---
 buildset-config.controller/nightly-rpm.conf  | 3 ---
 buildset-config.controller/nightly-world-lsb.conf| 3 ---
 buildset-config.controller/nightly-world-uclibc.conf | 3 ---
 buildset-config.controller/nightly-world.conf| 3 ---
 buildset-config.controller/nightly-x32.conf  | 3 ---
 buildset-config.controller/nightly-x86-64.conf   | 3 ---
 buildset-config.controller/nightly-x86.conf  | 3 ---
 buildset-config.controller/poky-tiny.conf| 3 ---
 buildset-config.controller/ptest-x86-64.conf | 3 ---
 buildset-config.controller/ptest-x86.conf| 3 ---
 buildset-config.old/minnow.conf  | 3 ---
 26 files changed, 78 deletions(-)

diff --git a/buildset-config.controller/nightly-arm.conf 
b/buildset-config.controller/nightly-arm.conf
index 5035bbc..f5d29a8 100644
--- a/buildset-config.controller/nightly-arm.conf
+++ b/buildset-config.controller/nightly-arm.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-arm64.conf 
b/buildset-config.controller/nightly-arm64.conf
index 634e75c..8c31fff 100644
--- a/buildset-config.controller/nightly-arm64.conf
+++ b/buildset-config.controller/nightly-arm64.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-deb-non-deb.conf 
b/buildset-config.controller/nightly-deb-non-deb.conf
index 2c2b6d3..716332c 100644
--- a/buildset-config.controller/nightly-deb-non-deb.conf
+++ b/buildset-config.controller/nightly-deb-non-deb.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-deb.conf 
b/buildset-config.controller/nightly-deb.conf
index f6ed955..fa8813c 100644
--- a/buildset-config.controller/nightly-deb.conf
+++ b/buildset-config.controller/nightly-deb.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-fsl-arm.conf 
b/buildset-config.controller/nightly-fsl-arm.conf
index e5ca381..d9e69d3 100644
--- a/buildset-config.controller/nightly-fsl-arm.conf
+++ b/buildset-config.controller/nightly-fsl-arm.conf
@@ -6,9 +6,6 @@ repos: [{'poky':
  'branch':'master'}},
 {'meta-fsl-arm':
 {'repourl':'git://git.yoctoproject.org/meta-fsl-arm',
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'S

[yocto] [PATCH][autobuilder 2/3] buildset-config.controller: don't specify test suites explicitly

[Ross Burton]

The autobuilder was specifying the test list explicitly in several buildsets
because in the past the SMART and RPM tests didn't skip automatically on non-RPM
images.  However we're removing the dmesg test as it is obsolete (replaced by
parselogs) but the autobuilder still attempts to run it.

Now that the RPM and SMART tests skip correctly, remove all explict test suite
lists and instead either let the image specify what test suites to run, or use
suitesappend.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-deb-non-deb.conf | 4 +---
 buildset-config.controller/nightly-deb.conf | 4 +---
 buildset-config.controller/nightly-ipk.conf | 4 +---
 buildset-config.controller/nightly-multilib.conf| 3 +--
 4 files changed, 4 insertions(+), 11 deletions(-)

diff --git a/buildset-config.controller/nightly-deb-non-deb.conf 
b/buildset-config.controller/nightly-deb-non-deb.conf
index 716332c..691ff01 100644
--- a/buildset-config.controller/nightly-deb-non-deb.conf
+++ b/buildset-config.controller/nightly-deb-non-deb.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'deb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images': 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images': 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-deb.conf 
b/buildset-config.controller/nightly-deb.conf
index fa8813c..4d2fd8c 100644
--- a/buildset-config.controller/nightly-deb.conf
+++ b/buildset-config.controller/nightly-deb.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'deb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images': 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images': 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-ipk.conf 
b/buildset-config.controller/nightly-ipk.conf
index ba78f8c..797a622 100644
--- a/buildset-config.controller/nightly-ipk.conf
+++ b/buildset-config.controller/nightly-ipk.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'ipk'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images' : 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images' : 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-multilib.conf 
b/buildset-config.controller/nightly-multilib.conf
index a836974..6bd68f0 100644
--- a/buildset-config.controller/nightly-multilib.conf
+++ b/buildset-config.controller/nightly-multilib.conf
@@ -32,8 +32,7 @@ steps: [{'SetDest':{}},
 'distro': 'poky', 'packages' : 'ipk',
 'atextappend' : '\nIMAGE_INSTALL_append = " 
lib32-connman-gnome"\n'}},
 {'BuildImages': {'images': 'core-image-sato'}},
-{'RunSanityTests': {'images': 'core-image-sato',
-'suites' : 'ping ssh connman xorg multilib dmesg 
auto'}},
+{'RunSanityTests': {'images': 'core-image-sato', 'suitesappend' : 
'multilib'}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686',
 'buildhistory' : False, 'm

[yocto] [PATCH][autobuilder 3/3] nightly-multilib: improve multilib build determinism

[Ross Burton]

There are patches for oe-core which improve the behaviour of multilib images but
show that the RPM-based multilib image construction was working more by luck
than anything else.

Explicitly set RPM_PREFER_ARCH_ELF="1" to prefer 32-bit binaries when both
options are being installed.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 buildset-config.controller/nightly-multilib.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildset-config.controller/nightly-multilib.conf 
b/buildset-config.controller/nightly-multilib.conf
index 6bd68f0..7cf75c3 100644
--- a/buildset-config.controller/nightly-multilib.conf
+++ b/buildset-config.controller/nightly-multilib.conf
@@ -24,7 +24,7 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
 'buildhistory' : False, 'multilib': 'lib32',
 'distro': 'poky',
-'atextappend' : '\nIMAGE_INSTALL_append = " 
lib32-connman-gnome"\n'}},
+'atextappend' : '\nRPM_PREFER_ELF_ARCH = 
"1"\nIMAGE_INSTALL_append = " lib32-connman-gnome"\n'}},
 {'BuildImages': {'images': 'core-image-sato'}},
 {'RunSanityTests': {'images': 'core-image-sato', 'suitesappend' : 
'multilib'}},
 {'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
-- 
2.1.4

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

[yocto] [PATCH][yocto-autobuilder] buildset-config.controller: don't specify test suites explicitly

[Ross Burton]

The autobuilder was specifying the test list explicitly in several buildsets
because in the past the SMART and RPM tests didn't skip automatically on non-RPM
images.  However we're removing the dmesg test as it is obsolete (replaced by
parselogs) but the autobuilder still attempts to run it.

Now that the RPM and SMART tests skip correctly, remove all explict test suite
lists and instead either let the image specify what test suites to run, or use
suitesappend.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 buildset-config.controller/nightly-deb-non-deb.conf | 4 +---
 buildset-config.controller/nightly-deb.conf | 4 +---
 buildset-config.controller/nightly-ipk.conf | 4 +---
 buildset-config.controller/nightly-multilib.conf| 3 +--
 4 files changed, 4 insertions(+), 11 deletions(-)

diff --git a/buildset-config.controller/nightly-deb-non-deb.conf 
b/buildset-config.controller/nightly-deb-non-deb.conf
index 716332c..691ff01 100644
--- a/buildset-config.controller/nightly-deb-non-deb.conf
+++ b/buildset-config.controller/nightly-deb-non-deb.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'deb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images': 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images': 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-deb.conf 
b/buildset-config.controller/nightly-deb.conf
index fa8813c..4d2fd8c 100644
--- a/buildset-config.controller/nightly-deb.conf
+++ b/buildset-config.controller/nightly-deb.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'deb'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images': 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images': 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-ipk.conf 
b/buildset-config.controller/nightly-ipk.conf
index ba78f8c..797a622 100644
--- a/buildset-config.controller/nightly-ipk.conf
+++ b/buildset-config.controller/nightly-ipk.conf
@@ -11,7 +11,5 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False, 'packages': 'ipk'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'RunSanityTests': {'images' : 'core-image-minimal'}},
-{'RunSanityTests': {'images' : 'core-image-sato', 'suites' : 'ping ssh 
auto'}},
-{'RunSanityTests': {'images' : 'core-image-sato-sdk', 'suites' : 'ping 
ssh df connman syslog xorg scp vnc date perl ldd gcc kernelmodule dmesg 
python'}},
+{'RunSanityTests': {'images' : 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
 {'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly-multilib.conf 
b/buildset-config.controller/nightly-multilib.conf
index a836974..6bd68f0 100644
--- a/buildset-config.controller/nightly-multilib.conf
+++ b/buildset-config.controller/nightly-multilib.conf
@@ -32,8 +32,7 @@ steps: [{'SetDest':{}},
 'distro': 'poky', 'packages' : 'ipk',
 'atextappend' : '\nIMAGE_INSTALL_append =  
lib32-connman-gnome\n'}},
 {'BuildImages': {'images': 'core-image-sato'}},
-{'RunSanityTests': {'images': 'core-image-sato',
-'suites' : 'ping ssh connman xorg multilib dmesg 
auto'}},
+{'RunSanityTests': {'images': 'core-image-sato', 'suitesappend' : 
'multilib'}},
 {'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686',
 'buildhistory' : False, 'multilib': 'lib64',
 'distro

[yocto] [PATCH][yocto-autobuilder 2/2] buildset-config.controller: don't build Qt3 images

[Ross Burton]

Qt3 is incredibly old and not required by LSB 5, so now is time to remove it
from the autobuilder.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 buildset-config.controller/minnow-lsb.conf  | 5 +
 buildset-config.controller/nightly-arm-lsb.conf | 5 +
 buildset-config.controller/nightly-fsl-arm-lsb.conf | 9 +++--
 buildset-config.controller/nightly-fsl-ppc-lsb.conf | 5 +
 buildset-config.controller/nightly-mips-lsb.conf| 5 +
 buildset-config.controller/nightly-ppc-lsb.conf | 5 +
 buildset-config.controller/nightly-x86-64-lsb.conf  | 5 +
 buildset-config.controller/nightly-x86-lsb.conf | 5 +
 buildset-config.controller/nightly.conf | 5 +
 9 files changed, 11 insertions(+), 38 deletions(-)

diff --git a/buildset-config.controller/minnow-lsb.conf 
b/buildset-config.controller/minnow-lsb.conf
index ea65e84..c8ec405 100644
--- a/buildset-config.controller/minnow-lsb.conf
+++ b/buildset-config.controller/minnow-lsb.conf
@@ -4,9 +4,6 @@ repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
  'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
- 'branch':'master'}},
 {'meta-intel':
 {'repourl':'git://git.yoctoproject.org/meta-intel',
  'branch':'master'}},
@@ -20,7 +17,7 @@ steps: [{'SetDest':{}},
 {'CreateAutoConf': {'machine': 'minnow', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky-lsb', 'emgd': 'True', 'pvr': 'False', 'atextappend': 
'\nNOISO=1\nCORE_IMAGE_EXTRA_INSTALL += dmidecode pciutils ethtool 
alsa-utils\n'}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer': True, 
'bspprovider': 'intel','layerdirs': ['meta-minnow', 'meta-intel', 
'meta-intel/meta-tlk']}},
 {'CheckForMinnow':{}},
-{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk core-image-lsb-qt3'}},
+{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk'}},
 {'PublishLayerTarballs':{}},
 {'SendErrorReport': {}},
 {'PublishArtifacts': {'artifacts': ['conf', 'minnow', 'md5sums']}}]
diff --git a/buildset-config.controller/nightly-arm-lsb.conf 
b/buildset-config.controller/nightly-arm-lsb.conf
index f950b6d..f7b98eb 100644
--- a/buildset-config.controller/nightly-arm-lsb.conf
+++ b/buildset-config.controller/nightly-arm-lsb.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
@@ -16,7 +13,7 @@ steps: [{'SetDest':{}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
 {'SyncPersistDB' : {'distro' : 'poky-lsb'}},
 {'GetBitbakeVersion': {}},
-{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk core-image-lsb-qt3'}},
+{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk'}},
 {'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' : 'i686', 
'distro': 'poky-lsb'}},
 {'BuildImages': {'images': 'core-image-lsb core-image-lsb-sdk'}},
 {'SyncPersistDB' : {'commit' : True, 'distro':'poky-lsb'}},
diff --git a/buildset-config.controller/nightly-fsl-arm-lsb.conf 
b/buildset-config.controller/nightly-fsl-arm-lsb.conf
index 4599247..8380b84 100644
--- a/buildset-config.controller/nightly-fsl-arm-lsb.conf
+++ b/buildset-config.controller/nightly-fsl-arm-lsb.conf
@@ -6,9 +6,6 @@ repos: [{'poky':
  'branch':'master'}},
 {'meta-fsl-arm':
 {'repourl':'git://git.yoctoproject.org/meta-fsl-arm',
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
@@ -20,17 +17,17 @@ steps: [{'SetDest':{}},
 'devkernel' : False}},
 {'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer' : True, 
'bspprovider' : 'fsl-arm'}},
 {'GetBitbakeVersion': {}},
-{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk core-image-lsb-qt3'}},
+{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev 
core-image-lsb-sdk'}},
 {'CreateAutoConf': {'machine': 'imx6qsabresd', 'SDKMACHINE' : 'x86_64',
 'distro': 'poky-lsb', 'buildhistory' : False,
 'atextprepend': 'ACCEPT_FSL_EULA = 1\n',
 'devkernel' : False}},
-{'BuildImages': {'images

[yocto] [PATCH][yocto-autobuilder 1/2] buildset-config.controller: remove unused meta-qt3 from buildsets

[Ross Burton]

Many buildsets pull in meta-qt3 but don't use it, so remove the layer from those
buildsets.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 buildset-config.controller/minnow.conf   | 3 ---
 buildset-config.controller/nightly-arm.conf  | 3 ---
 buildset-config.controller/nightly-arm64.conf| 3 ---
 buildset-config.controller/nightly-deb-non-deb.conf  | 3 ---
 buildset-config.controller/nightly-deb.conf  | 3 ---
 buildset-config.controller/nightly-fsl-arm.conf  | 3 ---
 buildset-config.controller/nightly-fsl-ppc.conf  | 3 ---
 buildset-config.controller/nightly-ipk.conf  | 3 ---
 buildset-config.controller/nightly-mips.conf | 3 ---
 buildset-config.controller/nightly-mips64.conf   | 3 ---
 buildset-config.controller/nightly-multilib.conf | 3 ---
 buildset-config.controller/nightly-no-x11.conf   | 3 ---
 buildset-config.controller/nightly-non-gpl3.conf | 3 ---
 buildset-config.controller/nightly-oecore.conf   | 3 ---
 buildset-config.controller/nightly-ppc.conf  | 3 ---
 buildset-config.controller/nightly-rpm-non-rpm.conf  | 3 ---
 buildset-config.controller/nightly-rpm.conf  | 3 ---
 buildset-config.controller/nightly-world-lsb.conf| 3 ---
 buildset-config.controller/nightly-world-uclibc.conf | 3 ---
 buildset-config.controller/nightly-world.conf| 3 ---
 buildset-config.controller/nightly-x32.conf  | 3 ---
 buildset-config.controller/nightly-x86-64.conf   | 3 ---
 buildset-config.controller/nightly-x86.conf  | 3 ---
 buildset-config.controller/poky-tiny.conf| 3 ---
 buildset-config.controller/ptest-x86-64.conf | 3 ---
 buildset-config.controller/ptest-x86.conf| 3 ---
 26 files changed, 78 deletions(-)

diff --git a/buildset-config.controller/minnow.conf 
b/buildset-config.controller/minnow.conf
index 401727a..69eefd5 100644
--- a/buildset-config.controller/minnow.conf
+++ b/buildset-config.controller/minnow.conf
@@ -4,9 +4,6 @@ repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
  'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
- 'branch':'master'}},
 {'meta-intel':
 {'repourl':'git://git.yoctoproject.org/meta-intel',
  'branch':'master'}},
diff --git a/buildset-config.controller/nightly-arm.conf 
b/buildset-config.controller/nightly-arm.conf
index ae73381..d5bc41d 100644
--- a/buildset-config.controller/nightly-arm.conf
+++ b/buildset-config.controller/nightly-arm.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-arm64.conf 
b/buildset-config.controller/nightly-arm64.conf
index 0b15ec8..16a35fb 100644
--- a/buildset-config.controller/nightly-arm64.conf
+++ b/buildset-config.controller/nightly-arm64.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-deb-non-deb.conf 
b/buildset-config.controller/nightly-deb-non-deb.conf
index 2c2b6d3..716332c 100644
--- a/buildset-config.controller/nightly-deb-non-deb.conf
+++ b/buildset-config.controller/nightly-deb-non-deb.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch':'master'}}]
 steps: [{'SetDest':{}},
 {'CheckOutLayers': {}},
diff --git a/buildset-config.controller/nightly-deb.conf 
b/buildset-config.controller/nightly-deb.conf
index f6ed955..fa8813c 100644
--- a/buildset-config.controller/nightly-deb.conf
+++ b/buildset-config.controller/nightly-deb.conf
@@ -3,9 +3,6 @@ builders: 'example-worker'
 repos: [{'poky':
 {'repourl':'git://git.yoctoproject.org/poky',
  'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
- 'branch':'master'}},
-{'meta-qt3':
-{'repourl':'git://git.yoctoproject.org/meta-qt3',
  'branch

[yocto] [PATCH][autobuilder] grid_macros: update error reporting service URL

[Ross Burton]

The Error Reporting Service was rewritten and the URLs are different.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 .../buildbot/status/web/templates/grid_macros.html   |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/status/web/templates/grid_macros.html
 
b/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/status/web/templates/grid_macros.html
index 0479927..83cc874 100644
--- 
a/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/status/web/templates/grid_macros.html
+++ 
b/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/status/web/templates/grid_macros.html
@@ -26,7 +26,7 @@
   {%- else %}br/bCommit: /blatest{% endif %}
   {%- if ss.branch %} in {{ ss.branch|e }}{% endif %}
   {%- if ss.hasPatch %} [patch]{% endif -%}
-  (a 
href=http://errors.yoctoproject.org/Errors/Search/Args/?items=10query={{ss.revision}};errors/a)
+  (a 
href=http://errors.yoctoproject.org/Errors/Latest/?type=commitfilter={{ss.revision}};errors/a)
 br/
 {%- endfor %}
   /td
-- 
1.7.10.4

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

[yocto] [autobuilder][PATCH] buildset-config.controller: add nightly-arm64 target

[Ross Burton]

This is based on the nightly-arm target with the beaglebone builds removed.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 buildset-config.controller/nightly-arm64.conf |   27 +
 1 file changed, 27 insertions(+)
 create mode 100644 buildset-config.controller/nightly-arm64.conf

diff --git a/buildset-config.controller/nightly-arm64.conf 
b/buildset-config.controller/nightly-arm64.conf
new file mode 100644
index 000..7c2524b
--- /dev/null
+++ b/buildset-config.controller/nightly-arm64.conf
@@ -0,0 +1,27 @@
+[nightly-arm64]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}},
+{'meta-qt3':
+{'repourl':'git://git.yoctoproject.org/meta-qt3',
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : True}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'SyncPersistDB' : {'distro' : 'poky'}},
+{'BuildImages': {'images': 'core-image-sato core-image-sato-dev 
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
+{'RunSanityTests': {'images': 'core-image-minimal core-image-sato 
core-image-sato-sdk'}},
+{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' : 'i686', 
'distro': 'poky', 'buildhistory' : False}},
+{'BuildToolchainImages': {}},
+{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky', 'buildhistory' : False}},
+{'BuildToolchainImages': {}},
+{'SyncPersistDB' : {'commit' : True, 'distro':'poky'}},
+{'PublishLayerTarballs':{}},
+{'SendErrorReport': {}},
+{'PublishArtifacts': {'artifacts': ['qemuarm64', 'ipk', 'toolchain', 
'md5sums']}}]
+
-- 
1.7.10.4

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

[yocto] [PATCH] dev-manual: use ##OEROOT## instead of ##COREBASE##

[Ross Burton]

The variable ##COREBASE## has been deprecated, so use ##OEROOT## instead.

Signed-off-by: Ross Burton ross.bur...@intel.com
---
 documentation/dev-manual/dev-manual-common-tasks.xml |   12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml 
b/documentation/dev-manual/dev-manual-common-tasks.xml
index 7fa9149..9fadd7b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4980,15 +4980,15 @@
  BBFILES ?= 
 
  BBLAYERS ?=  \
-   ##COREBASE##/meta \
-   ##COREBASE##/meta-yocto \
-   ##COREBASE##/meta-yocto-bsp \
-   ##COREBASE##/meta-mylayer \
+   ##OEROOT##/meta \
+   ##OEROOT##/meta-yocto \
+   ##OEROOT##/meta-yocto-bsp \
+   ##OEROOT##/meta-mylayer \

 
  BBLAYERS_NON_REMOVABLE ?=  \
-   ##COREBASE##/meta \
-   ##COREBASE##/meta-yocto \
+   ##OEROOT##/meta \
+   ##OEROOT##/meta-yocto \

 /literallayout
 Creating and providing an archive of the
-- 
1.7.10.4

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