Re: [OE-core] [PATCH 09/17] valgrind: Define __UCLIBC__ for uclibc based systems

On Mon, Dec 21, 2015 at 12:38 PM, Andre McCurdy wrote: > On Sat, Dec 19, 2015 at 3:52 PM, Khem Raj wrote: >> Helps configure valgrind for uclibc targets otherwise it tries to assume >> funcitons that are implemented in glibc like __free_res > > This is

Re: [OE-core] [PATCH 09/17] valgrind: Define __UCLIBC__ for uclibc based systems

On Sat, Dec 19, 2015 at 3:52 PM, Khem Raj wrote: > Helps configure valgrind for uclibc targets otherwise it tries to assume > funcitons that are implemented in glibc like __free_res This is going to conflict with the valgrind version update patches already posted to the list.

Re: [OE-core] [PATCH 2/6] lttng-modules: fix build issue against kernel 4.4

On Mon, Dec 21, 2015 at 6:39 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 12/21/2015 01:27 PM, Otavio Salvador wrote: > > Commit logs are suppose to have the information useful to understand >> the reason of the change. Latest hides all behind it and does not >>

Re: [OE-core] [PATCH] libdrm: Upgrade to 2.4.65

Buildhistory-diff says: packages/corei7-64-poky-linux/libdrm/libdrm: PKG changed from libdrm2 to libdrm [default] - may indicate debian renaming failure There's a new library (libdrm_amdgpu.so) which needs to be split out. To be honest the splitting should be automated instead of done manually

[OE-core] [PATCH] directfb.inc: enable bfd linker workaround for all arm targets

Although the gold linker problems with DirectFB have only so far been observed with armv7a, they could potentially affect future arm targets too. Since there's no particular downside to using the bfd linker for DirectFB, apply the workaround to all arm targets. Signed-off-by: Andre McCurdy

[OE-core] [PATCH] conf/local.conf.sample: comment out ASSUME_PROVIDED=libsdl-native

Ubuntu 15.10 and Debian testing can't build qemu-native against the host libsdl. Now that libsdl-native is buildable, comment out the ASSUME_PROVIDED which meant it wouldn't be used. [ YOCTO #8553 ] Signed-off-by: Ross Burton --- meta/conf/local.conf.sample | 8

Re: [OE-core] [PATCH 07/10] mirrors: replace references to archive.apache.org

On Wed, Dec 9, 2015 at 6:40 AM, Alexander Kanavin wrote: > archive.apache.org does not contain current releases, only historical ones, > so upstream checks aren't accurate. It's replaced with official mirrors > containing current versions. > > Signed-off-by:

Re: [OE-core] [PATCH] scripts/oe-selftest: Add support for selftest log with timestamp

On 19 December 2015 at 19:41, Costin Constantin < costin.c.constan...@intel.com> wrote: > +log_file = "oe-selftest-" + t.strftime("%Y-%m-%d_%H:%M:%S") + ".log" > +if os.path.exists("oe-selftest.log"): os.remove("oe-selftest.log") > +os.symlink(log_file, "oe-selftest.log") > Wouldn't

[OE-core] [PATCH 0/2] Patches for guile and bind

From: Kai Kang The following changes since commit 5f406915b5e26761faa4ea5e0edd887ac5ae6e2f: bitbake: toaster: remove 2 confusing parameters (2015-12-18 13:51:54 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/misc

[OE-core] [PATCH 2/2] bind: 9.10.2-P4 -> 9.10.3-P2

From: Kai Kang Upgrade bind from 9.10.2-P4 to 9.10.3-P2. * update context of 0001-build-use-pkg-config-to-find-libxml2.patch * add PACKAGECONFIGs readline and libedit. They provide same library, so should not be set at same time. Signed-off-by: Kai Kang

Re: [OE-core] [PATCH 08/17] fts: Add recipe

On Dec 21, 2015 4:15 AM, "Burton, Ross" wrote: > > > On 19 December 2015 at 23:52, Khem Raj wrote: >> >> create mode 100644 meta/recipes-core/fts/fts/fts-header-correctness.patch >> create mode 100644 meta/recipes-core/fts/fts/fts-uclibc.patch >>

Re: [OE-core] [meta-oe][PATCH v3 1/1] nodejs: cleanup and update

Oops, sent to wrong list. resending... -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 12/26] devtool: add: tweak help text

Add a few clarifying words. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/standard.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py index c11de9d..57175a4 100644 ---

[OE-core] [PATCH 06/26] recipetool: create: prevent attempting to unpack entire DL_DIR

If you specify a URL ending in /, BitBake's fetcher returns a localpath of ${DL_DIR}, and if you then try to unpack that it will attempt to copy the entire DL_DIR contents to the destination - which at least on my system filled my entire /tmp. Obviously we should fix the fetcher, but at least

[OE-core] [PATCH 15/26] scripts/lib/argparse_oe: handle intermixing of optional positional arguments

Python's argparse module can't handle when several optional positional arguments (set with nargs='?') are intermixed with other options. If the positional arguments aren't optional then this isn't an issue; thus when changing positional arguments to optional (as we are doing with devtool) we need

[OE-core] [PATCH 11/26] devtool: edit-recipe: add new subcommand

Add an "edit-recipe" subcommand that runs your default editor (as specified by the EDITOR environment variable) on the specified recipe in the workspace. Note that by default the recipe file itself must be in the workspace - i.e. as a result of "devtool add" or "devtool upgrade"; however there is

[OE-core] [PATCH 09/26] recipetool: create: support extracting name and version from build scripts

Some build systems (notably autotools) support declaring the name and version of the program being built; since we need those for the recipe we can attempt to extract them. It's a little fuzzy as they are often omitted or may not be appropriately formatted for our purposes, but it does work on a

[OE-core] [PATCH 13/26] devtool: split out function for naming bbappend

We're repeating this in a couple of places, so we might as well have a function to do it. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/__init__.py | 15 +++ scripts/lib/devtool/standard.py | 18 +- 2 files changed, 20

[OE-core] [PATCH 14/26] devtool: update-recipe: use correct method to get bbappend filename

The bbappend already exists at this point, so we know what its path is - there's no need to figure it out from scratch here. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/standard.py | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

[OE-core] [PATCH 07/26] recipetool: create: detect when specified URL returns a web page

If the user specifies a URL that just returns a web page, then it's probably incorrect (or broken); attempt to detect this and show an error if it's the case. Signed-off-by: Paul Eggleton --- scripts/lib/recipetool/create.py | 15 +++ 1 file changed,

[OE-core] [PATCH 18/26] devtool: add: allow specifying URL as positional argument

Having to specify -f is a little bit ugly when a URI is distinctive enough to recognise amongst the other positional parameters, so take it as an optional positional parameter. -f/--fetch is still supported, but deprecated. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 17/26] devtool: add: figure out recipe name from recipetool

recipetool create now has all the logic in it for auto-detecting the name and version, and using those in the file name - so we can make the name an optional parameter for devtool add and we pick up the file name that recipetool has used after the fact. Signed-off-by: Paul Eggleton

[OE-core] [PATCH 19/26] devtool: modify: default source tree path

As per the changes to "devtool add", make the source tree path optional and use the default path if none is specified. Signed-off-by: Paul Eggleton --- scripts/devtool | 4 scripts/lib/devtool/standard.py | 26 +++--- 2

[OE-core] [PATCH 26/26] oe-selftest: devtool: add more explicit check for ls output

test_devtool_deploy_target is failing on the Yocto Project autobuilder apparently when it attempts to cut out some fields from the list. It doesn't fail here and I can't see what the problem lines are, so add a check for lines with too few fields so we can get a look at them next time it fails.

[OE-core] [PATCH 16/26] devtool: add: allow source tree to be omitted

Assuming we're fetching source remotely (from a URI) we can default the source tree that will be extracted from it to a "sources" directory under the workspace in order to save the user specifying it if they don't have a preferred location. Signed-off-by: Paul Eggleton

[OE-core] [PATCH 22/26] devtool: sync: tweak help / messages

Much of this was copy/pasted from the extract subcommand code; make it specific to sync. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/standard.py | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/scripts/lib/devtool/standard.py

[OE-core] [PATCH 21/26] devtool: reset: print message about leaving source tree behind

We deliberately leave the source tree alone when resetting in case it contains any work in progress belonging to the user; tell them that we're doing this so they aren't surprised about it still existing later on. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 20/26] devtool: status: list recipe file within workspace if one exists

If a recipe in the workspace actually exists as a file within the workspace (e.g. after doing "devtool add" or "devtool upgrade") then show the path to the recipe file on the status line for the recipe. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 23/26] recipetool: create: improve autotools support

* tar and binutils we can assume are there * libsocket is only relevant on BSD systems, so we can ignore it. * Detect more things implying gettext/intltool is needed * Detect glib-2.0 requirement. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 24/26] recipetool: create: fix error when extracting source to a specified directory

Having fetched the source and unpacked it to a temporary directory, we then move part of it to the destination directory, or if the source is at the top level we move the whole temporary directory, but in the latter case we were later attempting to delete the temporary directory which no longer

[OE-core] [PATCH 10/26] recipetool: create: basic extraction of name/version from filename

Often the filename (e.g. source tarball) contains the name and version of the software it contains. (This isn't intended to be exhaustive, just to catch the common case.) Signed-off-by: Paul Eggleton --- meta/lib/oeqa/selftest/devtool.py | 15 ---

[OE-core] [PATCH 03/26] recipetool: create: avoid traceback on fetch error

If a fetch error occurs, the fetcher already prints a reasonable error - we don't need the traceback as well, so catch that and exit if it occurs. Signed-off-by: Paul Eggleton --- scripts/lib/recipetool/create.py | 6 +- 1 file changed, 5 insertions(+), 1

[OE-core] [PATCH 05/26] recipetool: create: minor fix for potential issue in python handling

If SRC_URI happened not to be in the pre-generated lines then this code would error out. This is unlikely to happen with the way the create code is structured at the moment, but handle it just in case. Signed-off-by: Paul Eggleton ---

[OE-core] [PATCH 25/26] oe-selftest: add tests for simple devtool add / recipetool create URL case

Add an oe-selftest test case for the newly supported syntax with only the remote URL specified (auto-detecting name and version). Signed-off-by: Paul Eggleton --- meta/lib/oeqa/selftest/devtool.py| 63

[OE-core] [PATCH 08/26] recipetool: create: set up priority system for recipe handlers

Sometimes we want to force one handler to run before another; if the two handlers are in different plugins that's difficult without some kind of priority number, so add one and sort by it. Signed-off-by: Paul Eggleton --- scripts/lib/recipetool/create.py | 16

[OE-core] [PATCH 0/5] Extensible SDK improvements

Some tweaks and minor fixes for the extensible SDK. The following changes since commit 2a1edfd9cfa16ec334c0758b47677d4fee5e79a8: bitbake.conf: Add filename and lineno to BB_SIGNATURE_EXCLUDE_FLAGS (2015-12-22 00:01:31 +) are available in the git repository at:

[OE-core] [PATCH 3/5] classes/populate_sdk_ext: hide build configuration in devtool build* output

The configuration of the build system within the extensible SDK is fixed, so there's not a lot of point in showing it; plus it just gets in the way of the output that's interesting to the user in this context. So let's hide it within the extensible SDK. Signed-off-by: Paul Eggleton

[OE-core] [PATCH 2/5] classes/base: don't print header if BUILDCFG_HEADER not set

If we don't want a header printed at the start of task execution (which we'd prefer not to within the extensible SDK) we can accomplish that by clearing BUILDCFG_VARS and BUILDCFG_HEADER, but that was still printing a load of blank lines. To keep things simple, check if BUILDCFG_HEADER is set to

[OE-core] [PATCH 4/5] classes/populate_sdk_ext: error out of install if buildtools install fails

If the installation of buildtools fails then we should fail the entire installation instead of blindly continuing on. Signed-off-by: Paul Eggleton --- meta/classes/populate_sdk_ext.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/5] classes/populate_sdk_ext: use uninative to set NATIVELSBSTRING

We inherit uninative in the extensible SDK configuration, and uninative sets NATIVELSBSTRING to a fixed value, so we don't need to force the value ourselves. Fixes [YOCTO #8662]. Signed-off-by: Paul Eggleton --- meta/classes/populate_sdk_ext.bbclass | 7 ++-

[OE-core] [PATCH 5/5] devtool: sdk-update: fix traceback without update server set

If the SDK update server hasn't been set in the config (when building the extensible SDK this would be set via SDK_UPDATE_URL) and it wasn't specified on the command line then we were failing with a traceback because we didn't pass the default value properly - None is interpreted as no default,

[OE-core] [meta-oe][PATCH v3 1/1] nodejs: cleanup and update

Remove old nodejs_0.4.12 and update nodejs_0.12.7 to the latest stable nodejs_4.2.3. Nodejs is picky about which architectures it supports. The supported arch mapping required some updating to bring it up to date with the current nodejs code. Add COMPATIBLE_MACHINE entries so it only builds for

[OE-core] [meta-oe][PATCH v3 0/1] nodejs cleanup and update

My third attempt to update and cleanup the nodejs recipes. This patch removes the older nodejs recipes and replaces them with a recipe for nodejs 4.2.3 (the latest stable at this time). Nodejs is picky about which architectures it supports. Add COMPATIBLE_MACHINE and cleanup the architecture

[OE-core] [PATCH 00/26] devtool/recipetool improvements

Apologies for the flood of patches today, this is the last one. There are quite a few changes here, but the common theme is making devtool (and recipetool) a bit easier to use, as well as making "devtool add" and "recipetool create" more effective at picking up things from the specified source

[OE-core] [PATCH 01/26] scripts: print usage in argparse-using scripts when a command-line error occurs

For scripts that use Python's standard argparse module to parse command-line arguments, create a subclass which will show the usage the usage information when a command-line parsing error occurs. The most common case would be when the script is run with no arguments; at least then the user

[OE-core] [PATCH 04/26] recipetool: create: fix do_install handling for makefile-only software

In my testing here it appears make -qn returns an error (exit code 2) whereas make -n doesn't; I can't immediately tell why based on the documentation. We don't actually care for it to be quiet since we're capturing the output, so let's just leave -q off and have this work properly as a result.

[OE-core] [PATCH 02/26] recipetool: create: handle https://....git URLs

When you grab a URL for a github repository you'll almost certainly find it in https://github.com/path/to/repository.git format; but bitbake's fetcher can't handle that because it'll see https:// at the start and assume it should use wget to fetch it. If the URL starts with http:// or https:// and

Re: [OE-core] [PATCH 1/2] buildhistory: fix not recording SDK information

On Tue, 22 Dec 2015 15:41:27 Paul Eggleton wrote: > After OE-Core revision baa4e43a29e45df17eaa3456acc179b08d571db6 we lost > recording SDK the contents in buildhistory. This was due to the > SDK_POSTPROCESS_COMMAND variable being set with = in > populate_sdk_base.bbclass which overwrote any value

[OE-core] [PATCH 1/2] buildhistory: fix not recording SDK information

After OE-Core revision baa4e43a29e45df17eaa3456acc179b08d571db6 we lost recording SDK the contents in buildhistory. This was due to the SDK_POSTPROCESS_COMMAND variable being set with = in populate_sdk_base.bbclass which overwrote any value set with += in buildhistory.bbclass; to fix it, use

[OE-core] [PATCH 0/2] SDK-related fixes for buildhistory

Fix a general regression in recording SDK information that happened during the jethro timeframe, and improve what we record for the extensible SDK. The following changes since commit 2a1edfd9cfa16ec334c0758b47677d4fee5e79a8: bitbake.conf: Add filename and lineno to BB_SIGNATURE_EXCLUDE_FLAGS

[OE-core] [PATCH 2/2] buildhistory: improve support for extensible SDK

* Ensure extensible SDK and standard SDK go into their own directories * Record extra extensible SDK variables * Write sstate-package-sizes.txt and sstate-task-sizes.txt files so you can analyse the size of the contents * Add BUILDHISTORY_SDK_FILES (similar to BUILDHISTORY_IMAGE_FILES) and

Re: [OE-core] [PATCH] archiver.bbclass: fix an exception of the mode configured

Ping On 2015年11月17日 13:31, Jian Liu wrote: Hi Ross, I check the values of d.getVarFlag('do_configure', 'task') and d.getVarFlag('do_unpack', 'task') for gcc-source. But it seems that both values are 1. I use the following command to get the values, os.system("echo 'do_unpack=%s,

Re: [OE-core] [<OE-core][PATCH v2 1/4] weston-init: Handle Weston startup correctly.

Hello Tom, On Sat, Dec 19, 2015 at 4:08 PM, Tom Hochstein wrote: > Can you be more explicit about what you mean by weston-launch wrapper? Do you > want to hide the current weston-launch binary and replace it by a new > weston-launch wrapper? What happens to my

Re: [OE-core] [PATCH V2] qemu: upgrade to 2.5.0

Fixed floating dependency on libgcrypt. Cristian Iorga Yocto Project Intel Corporation -Original Message- From: Iorga, Cristian Sent: Monday, December 21, 2015 1:24 PM To: openembedded-core@lists.openembedded.org Cc: Iorga, Cristian Subject: [PATCH V2] qemu:

[OE-core] [PATCH V2] qemu: upgrade to 2.5.0

- cpus.c-qemu_mutex_lock_iothread-fix-race-condition-a.patch removed, included upstream; - smc91c111_fix*.patch patches removed, included upstream; - trace-remove-malloc-tracing.patch patch removed, included upstream; - some configure options disappeared or changed name, updated. Signed-off-by:

[OE-core] [PATCH 1/2] guile: remove redundant replacement of .pc file

From: Kai Kang Remove redundant replacement of pkgconfig file and only modify the .pc file which is installed in ${D}. Replace /usr/bin with ${bindir} at same time. Signed-off-by: Kai Kang --- meta/recipes-devtools/guile/guile_2.0.11.bb | 19

[OE-core] [PATCH][fido][dizzy] bind: CVE-2015-8000

Fixes a denial of service in BIND. An error in the parsing of incoming responses allows some records with an incorrect class to be accepted by BIND instead of being rejected as malformed. This can trigger a REQUIRE assertion failure when those records are subsequently cached. [YOCTO #8838]

Re: [OE-core] [PATCH 2/6] lttng-modules: fix build issue against kernel 4.4

On 12/21/2015 01:27 PM, Otavio Salvador wrote: Commit logs are suppose to have the information useful to understand the reason of the change. Latest hides all behind it and does not communicate anything. I don't think expect people to read the code to know you bumped (and to which) revision is

Re: [OE-core] [master/jethro][PATCH] libxcb: Add a workaround for gcc5 bug on mips

On 21 December 2015 at 01:42, Khem Raj wrote: > This fixes build failure for libxcb on mips > My hero! Thanks Khem I just looked at the logs on the AB and was wondering why it looked like gcc was crashing. Ross -- ___

Re: [OE-core] [PATCH 08/17] fts: Add recipe

On 19 December 2015 at 23:52, Khem Raj wrote: > create mode 100644 meta/recipes-core/fts/fts/fts-header-correctness.patch > create mode 100644 meta/recipes-core/fts/fts/fts-uclibc.patch > create mode 100644 meta/recipes-core/fts/fts/gcc5.patch > create mode 100644

Re: [OE-core] [PATCH 2/6] lttng-modules: fix build issue against kernel 4.4

Hello Bruce, On Sat, Dec 19, 2015 at 3:44 PM, Bruce Ashfield wrote: > On Sat, Dec 19, 2015 at 5:05 AM, Otavio Salvador > wrote: >> >> On Fri, Dec 18, 2015 at 6:44 PM, Bruce Ashfield >> wrote: >> >

Re: [OE-core] [Toaster] FW: [PATCH 6/7] toaster: Update for buildstats changes

On 18/12/2015 10:56, "Richard Purdie" wrote: >On Fri, 2015-12-18 at 09:21 +, Barros Pena, Belen wrote: >> I applied the buildstats series on top of toaster-next, ran a build, >> and >> checked the build stats info. I can see time per task coming in. I >>

Re: [OE-core] [PATCH 01/17] powertop: Include right headers for timval struct

On 19 December 2015 at 23:52, Khem Raj wrote: > +From 0856d8145d187a7e5a49625247abe43a13f95acc Mon Sep 17 00:00:00 2001 > +From: Khem Raj > +Date: Tue, 15 Sep 2015 19:36:28 + > +Subject: [PATCH] include rquired headers for typedefs > + > +timeval

Re: [OE-core] [PATCH 03/17] blktrace: Include

On 19 December 2015 at 23:52, Khem Raj wrote: > +Status: Submitted > We have tooling around this tag, so please use Upstream-Status. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH 02/17] dhcp: Include sys/types.h for u_int* defs

On 19 December 2015 at 23:52, Khem Raj wrote: > +From 971491b6d7ab47d2f92f34269a129d0347fba15a Mon Sep 17 00:00:00 2001 > +From: Khem Raj > +Date: Mon, 14 Sep 2015 23:51:38 + > +Subject: [PATCH] include missing sys/types.h > + > +Code uses plain

[OE-core] [PATCH] libdrm: Upgrade to 2.4.65

Rebased patch to reflect changes in Makefile Signed-off-by: Saul Wold --- .../recipes-graphics/drm/libdrm/installtests.patch | 24 -- .../drm/{libdrm_2.4.62.bb => libdrm_2.4.65.bb} | 5 +++-- 2 files changed, 16 insertions(+), 13 deletions(-)

Re: [OE-core] [PATCH 2/2] oe-buildenv-internal: preserve existing BB_ENV_EXTRAWHITE

Thanks, it is a legitimate bug, certainly not intended. I already posted a patch to the mailing list last week. > -Original Message- > From: Andre McCurdy [mailto:armccu...@gmail.com] > Sent: Monday, December 14, 2015 3:47 PM > To: Bystricky, Juro > Cc: OE Core mailing list;

Re: [OE-core] [PATCH][jethro][fido][ 00/15] Libxml2: multiple security fixes

On 12/16/2015 01:05 PM, Joshua Lock wrote: > Hi Armin, > > On 05/12/15 19:35, Armin Kuster wrote: >> Each CVE is an independant patch so they can be easily merged to other >> distros >> and/or stable branches. > > As others have mentioned elsewhere I think this would be much nicer if > each

Re: [OE-core] [PATCH v1] ncurses: fixes wrong paths in BINCONFIG

On 20 December 2015 at 21:47, Khem Raj wrote: > This patch moved it to PN instead of PN-dev, now I wonder what happens > if you were to install PN and lib32-PN packages, I guess you might > have same problem > No it doesn't, binconfig.bbclass sets FILES_${PN}-dev +=

[OE-core] [PATCH 2/2 v2] rpcbind: Fix build with libtirpc 1.0.1

libtirpc 1.0.1 uses the SVC_XP_AUTH macro to access xp_auth. Update rpcbind to follow the same way. Signed-off-by: Maxin B. John --- ...ly-Don-t-use-the-xp_auth-pointer-directly.patch | 43 ++ meta/recipes-extended/rpcbind/rpcbind_0.2.3.bb | 1 + 2

[OE-core] [PATCH 1/2 v2] libtirpc: upgrade to 1.0.1

0.2.5 -> 1.0.1 Fixed build with uclibc and musl Signed-off-by: Maxin B. John --- ...d-missing-rwlock_unlocks-in-xprt_register.patch | 62 + .../libtirpc/libtirpc/Use-netbsd-queue.h.patch | 1579 .../libtirpc/remove-des-functionality.patch