- 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: Cr
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: upgrade to 2.5.0
- cpus.c-q
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 proposed weston-start, which is
>
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:
>> > f4b27072
>>
>>
>> Use this revision on commit log; latest is not accurate as it moves during
>> ti
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
--
___
Openembedded-core mailing list
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
>> cannot
>> see cpu usage or disk i/o
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]
Refer
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 r
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 struct needs to include sys/time.h and sprint
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
http://lists.openembedded.org/mai
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 typedefs defines in this header but does not i
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 meta/recipes-core/fts/fts/re
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
>> create mode 100644 meta/recipes-core/fts/fts/gc
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 += ${bindir}/*-config
so they we
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| 144 ++
.../libtir
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 files changed, 44 inse
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 pat
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(-)
rename meta/recipes-graphic
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; jurobystri..
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.
Ross, any thoughts
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 going to conflict with the valgrind version
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
1 file changed, 4 inser
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: Alexander Kanavin
> ---
> meta/classe
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 t
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
>> communica
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 i
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
---
m
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
http://git.pokylinux.org/cgit.
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 ---
1 file changed, 4 insertions(+
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
---
.../0001-build-use-pkg-config-to-
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 _appen
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
* 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
defa
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:
git://git.openembedded.o
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
---
meta/clas
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 s
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 a/meta/classes/populate_sdk_ext.bbclass
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 ++-
1 file changed, 2 insertions(+),
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, mea
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 tre
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 immediat
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.
Si
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
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 ---
scripts/lib/recipetool/create.py |
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 deletion(-)
diff --git a/scripts/li
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
---
scripts/lib/recipetool/create_buildsys_python.py | 5 -
1
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 ++--
1 file changed, 14
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
--- a/scripts/lib/devtool/standard.
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 detec
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 t
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 a
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 re
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 insertions(+), 13 deletions(-)
diff --git
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 a/scripts/lib/devtool/standard.py
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, 11 insertions(+), 4 deletions(-)
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.
Si
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
---
scripts/lib/devtool/st
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 b/scripts/lib/devtool/standard.
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
---
scripts/lib/devtool/standard.py | 11 +++
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
---
scripts/lib/devtool/standard.py | 12 +++-
1 file ch
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
---
scripts/devtool | 2 ++
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
---
scripts/l
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 files changed, 19 insertions(+), 1
* 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
---
scripts/lib/recipetool/create_buildsys.py | 38 +++
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 exi
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
meta/lib/oeqa/selftest/recipetool.py | 19 +++
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 mapp
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 th
Oops, sent to wrong list. resending...
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
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
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, do_configure
71 matches
Mail list logo