This sub-command creates a bbappend for the specified target and prints the
path to the bbappend. The -w argument, as with some of the other recipetool
commands, will make a version-independent bbappend.
Example usage: recipetool newappend meta-mylayer virtual/kernel
[YOCTO #7964]
From: Christopher Larson
It's quite common to need to copy files out of the devshell back to your
layers, but most of the variables referring to such paths are not exported
(and in some cases, should not be, as it'll affect buildsystems we run, e.g.
TOPDIR/BUILDDIR). To
From: Leonardo Sandoval
First two patches fix issues when using hostnames instead of IPs. Third patch
change the journal mode, allowing the DB to be hosted on a remote server and
network filesystems. Detail is given on each patch. Fixes 8258, 8560 and
From: Leonardo Sandoval
When starting the server using port=0, the server actually starts with a
different port, so print a message with this new value. When stopping the
server with port=0, advise the user which ports the server is listening to,
so
From: Leonardo Sandoval
In cases where hostname is given instead of an IP (i.e. localhost
instead of 127.0.0.1) when stopping the server with bitbake-prserv --stop,
the server shows a misleading message indicating that the daemon was not
found, where
From: Leonardo Sandoval
Disadvantages of WAL journal mode are explained on [1], but the
one affecting our case is "All processes using a database must be
on the same host computer; WAL does not work over a network filesystem".
Changing the Journal mode
On 09/16/2015 10:04 AM, Robert Yang wrote:
* This fixed:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
$ bitbake core-image-minimal -cpopulate_sdk
Install
The gtk+2 requires whether x11 or directfb to build, so we need enable
either of them. The cairo can be built without x11 or directfb, but gtk+
requires cairo, so enable x11 or directfb for cairo, too.
Signed-off-by: Robert Yang
---
meta/recipes-gnome/gtk+/gtk+.inc
Make package_qa_clean_path() return something like "work/path/to/file"
rather than "/work/path/to/file", the relative path is a little clear.
Signed-off-by: Robert Yang
---
meta/classes/insane.bbclass |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
* Ignore elf files because they usually contain build path:
- The path of the source file such as .c, these are usually happen
when separate B and S since we use absolute path to run configure
script, and then VPATH in Makefile will be an absolute path and
contains build path, we can
The libglu requires both opengl (depends on virtual/libgl) and x11
(needs libGL.so which is provided by mesa when x11 in DISTRO_FEATURES),
so let libsdl depends on libglu when both x11 and opengl in
DISTRO_FEATURES.
Signed-off-by: Robert Yang
---
Hi RP and Ross,
I had sent these patches before, but didn't get any feedback, now send
again, would you please take a look at them ?
The following two patches would make oe-core can do world build well
without x11 in DISTRO_FEATURES:
gtk+/cairo: enable x11 or directfb
libsdl: depends on libglu
On 2015年09月16日 03:00, Otavio Salvador wrote:
Hello folks,
It seems the commit:
try this patch
http://patchwork.openembedded.org/patch/103239/
-Roy
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
This patch brings the qemu networking setup for qemuzynq and
qemumicroblaze into feature parity with the other qemu machines.
Specifically enabling TAP interface attachcment and kernel command line
IP configuration.
Signed-off-by: Nathan Rossi
---
This patch set updates the runqemu scripts for qemuzynq and qemumicroblaze,
fixing support for network interfaces and configuing qemumicroblaze to use the
QEMU inbuilt device tree.
Nathan Rossi (2):
runqemu-internal: Fix qemu networking for qemuzynq an qemumicroblaze
runqemu-internal: For
Setup the qemumicroblaze machine to use the device tree provided by QEMU
instead of the device tree located in the images directory. Additionally
setup the default memory size to match the QEMU device tree.
Signed-off-by: Nathan Rossi
---
scripts/runqemu-internal | 4
On 2015-09-14 01:55 PM, Randy MacLeod wrote:
On 2015-09-09 12:09 PM, Reshetova, Elena wrote:
Maybe we have to fix gcc-source after all rather than use the
EXCLUDE_WORLD
change I made in:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
Should I file a bug about this for easy
this patch it will try to provide a virtual reference for the common utils.
instead of looking to hardcoded busybox, it wil be simple exchange between other
common utils like gnu core utils or toybox among others.
In order to enable its required to fill at the distro conf or local.conf
This recipe have a hardcoded dependency to busybox, in order to be able to have
a flexible selection,
instead of the hardcoded dependency,now is point to virtual reference anybox.
Signed-off-by: Alejandro Joya
---
This recipe have a hardcoded dependency to busybox, in order to be able to have
a flexible selection,
instead of the hardcoded dependency,now is point to virtual reference anybox.
Signed-off-by: Alejandro Joya
---
This recipe have a hardcoded dependency to busybox, in order to be able to have
a flexible selection,
instead of the hardcoded dependency,now is point to virtual reference anybox.
Signed-off-by: Alejandro Joya
---
When configure multilib, "bitbake -c populate_sdk" should
install all arch toolchains (for example, 32 and 64bit), but rpm not
handle the multilib requires correctly, for example:
lib32-packagegroup-core-standalone-sdk-target requires lib32-libc6, rpm
may pull in libc6 rather than lib32-libc6,
The skipped packages may be pulled in by another package, for example,
when libc6-dbg is already installed and should be skipped, but it would
be pulled in by libsegfault, this patch fixes the issue.
Signed-off-by: Robert Yang
---
scripts/oe-pkgdata-util |5 -
Fixed when:
$ bitbake lib32-core-image-minimal -cpopulate_sdk
Only 32 bit toolchain was installed but there were both
environment-setup-core2-64-poky-linux and
environment-setup-core2-64-pokymllib32-linux in extracted sdk, this was
becase multilib.bbclass mapped TOOLCHAIN_TARGET_TASK into only
Fixed when extract mutilib SDK like
poky-glibc-x86_64-lib32-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh:
Each time you wish to use the SDK in a new shell session, you need to
source the environment setup script e.g.
$ ./path/to/environment-setup-core2-64-pokymllib32-linux
There was no
Fixed when sh is bash:
$ sh
./tmp/deploy/sdk/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh
Poky (Yocto Project Reference Distro) SDK installer version 1.8+snapshot
===
Fixed when populate multlib sdk:
$ bitbake lib32-core-image-minimal -cpopulate_sdk
When extract sdk, there was a sysroots/core2-64-pokymllib32-linux, but the
SDKTARGETSYSROOT path in environment-setup-x86-pokymllib32-linux was
sysroots/core2-64-poky-linux, so it was incorrect, install sysroot to
* This fixed:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
$ bitbake core-image-minimal -cpopulate_sdk
Install
poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh,
then source
From: Roy Li
The Perf source code between Yocto and upstream are different, like below
commit is not in upstream, so broaden the "--root" replacement to Makefile*
commit 33e96fb1e2d77541e81eb341ccd3fbe9419e4c9a
Author: Tom Zanussi
On Mon, Sep 14, 2015 at 04:31:17PM +, Khem Raj wrote:
> The code is creating more abstract types which is nice however it should
> be using standard defines from stdint.h and not random defines to base
> its own type system
These types are not random. They are standard Linux kernel types used
This option is causing issues with python unicode support. Several unicode
related regression tests are currently failing (test_re and test_codecs for
example) and removing this option fixes these.
This configure option mostly seems to be historical. Discussion related to
python issue 9210
Hello folks,
It seems the commit:
commit 43f965061f8af4c4537e9d9c0257253e613a616d
Author: Roy Li
Date: Wed Aug 26 13:58:17 2015 +0800
perf: fix the install-python_ext
1. $(grep xxx xxx) never returns 0, it maybe return empty or string, and
can not
Hello all,
Currently to support 32b and 64b build for same core in Yocto, two separated
compilers need to be generated. Is there plan to support multilib build(32b and
64b) by single toolchain which is generated by Yocto in future?
Best Regards,
Zhenhua
--
Fixes b6e64de541b37 "Restore compatibility with previous UBI filesystems"
The multivolume UBI code creates symlinks for each volume. If the volume name
is empty, it will create a symlink that the rootfs code will attempt to
create again later, resulting in a crash like this (unless
On 08/19/2015 11:50 PM, akuster808 wrote:
If you happen to need to repost this series again, Ruby version has just
been updated. It includes: CVE-2015-3900 Request hijacking vulnerability
in RubyGems 2.4.6 and earlier.
Do we have any idea how long this will be before hitting master-next?
I am
On Thu, 2015-09-10 at 12:30 -0500, George McCollister wrote:
> If the path contains 'scripts' more than once the first occurrence
> will be
> incorrectly used. Use rfind instead of find to find the last
> occurrence.
>
> Signed-off-by: George McCollister
Patch
On Tue, 2015-09-08 at 17:22 -0700, Armin Kuster wrote:
> From: Armin Kuster
>
> three security fixes.
>
> CVE-2015-6563 (Low) openssh: Privilege separation weakness related to
> PAM support
> CVE-2015-6564 (medium) openssh: Use-after-free bug related to PAM
> support
>
On Mon, 2015-09-07 at 16:21 -0700, Armin Kuster wrote:
> From: Armin Kuster
>
> three security fixes.
>
> Signed-off-by: Armin Kuster
Patch queued in my joshuagl/fido-next tree - thanks!
Joshua
On Mon, 2015-09-14 at 12:04 +0200, Sona Sarmadi wrote:
> _asn1_extract_der_octet: prevent past of boundary access
>
> References:
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3622
> http://git.savannah.gnu.org/gitweb/?p=libtasn1.git;a=patch;
>
On Fri, 2015-09-04 at 14:22 +0200, Martin Jansa wrote:
> * useful when we need to overlay/extend intercept scripts from oe
> -core
>
> Signed-off-by: Martin Jansa
Patch queued in my joshuagl/fido-next tree - thanks!
Joshua
Thanks, I see what you mean. I'll repost a new patch after I've tested it.
> -Original Message-
> From: Phil Blundell [mailto:p...@pbcl.net]
> Sent: Monday, September 14, 2015 12:53 PM
> To: Khem Raj
> Cc: Bystricky, Juro; Purdie, Richard; openembedded-
> c...@lists.openembedded.org
>
On Thu, 2015-09-10 at 13:54 +0200, Martin Jansa wrote:
> * trying to pass foo="a b" through postinst_intercept ends
> with the actual script header to containing:
> b
> foo=a
> which fails because "b" command doesn't exist.
>
> Signed-off-by: Martin Jansa
Patch
On Thu, 2015-09-10 at 13:54 +0200, Martin Jansa wrote:
> * without this the output wasn't shown anywhere even when the bb.warn
> says:
> "See log for details!"
>
> Signed-off-by: Martin Jansa
Patch queued in my joshuagl/fido-next tree - thanks!
Joshua
On Mon, 2015-09-14 at 12:41 +0200, Andrew Shadura wrote:
> ---
> meta/recipes-core/dbus/dbus_1.10.0.bb | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/dbus/dbus_1.10.0.bb
> b/meta/recipes-core/dbus/dbus_1.10.0.bb
> index 31cbef0..e099f4b 100644
>
Hi,
I agree with Tanu. +1 enabling for user-session by default if systemd is
used.
Pau Espin Pedrol
mail/jabber: pespin.s...@gmail.com
http://blog.espeweb.net
2015-09-15 13:36 GMT+02:00 Tanu Kaskinen :
> On Mon, 2015-09-14 at 12:41 +0200, Andrew Shadura wrote:
> > ---
> >
Once the DUT is hanged during testing, currently all the following test
cases have to wait for default timeout to exit. Using this decorator the
user can choose a timeout at case by case basis and what happens when the
timeout is reached by overwriting the self.target.restart method.
[YOCTO
On Mon, Sep 14, 2015 at 11:33 PM, wrote:
> On Mon, Sep 14, 2015 at 04:31:17PM +, Khem Raj wrote:
>> The code is creating more abstract types which is nice however it should
>> be using standard defines from stdint.h and not random defines to base
>> its own type system
>
On Tue, Sep 15, 2015 at 12:42 AM, Erkka Kääriä
wrote:
> This option is causing issues with python unicode support. Several unicode
> related regression tests are currently failing (test_re and test_codecs for
> example) and removing this option fixes these.
>
> This
On Tue, 2015-09-15 at 14:53 +0200, Andrew Shadura wrote:
> On 15/09/15 13:36, Tanu Kaskinen wrote:
> > I think user-session should be enabled by default when systemd is in
> > DISTRO_FEATURES. Some services, e.g. PulseAudio, can fully enable their
> > systemd integration only if dbus is compiled
When testimage is run with -v switch now individual
test progress can be seen directly in bitbake console.
[YOCTO #6841]
Signed-off-by: Lucian Musat
---
meta/lib/oeqa/oetest.py | 13 +
1 file changed, 13 insertions(+)
diff --git a/meta/lib/oeqa/oetest.py
On 9/15/15 8:05 AM, Markus Lehtonen wrote:
> Some (host) systems only have a binary named 'gpg' (e.g. Fedora) while
> some only have 'gpg2' (Ubuntu) and others have both of them (openSUSE).
> Currently the behavior of rpm-native with regards to GnuPG depends on
> the host platform: rpm(-native) is
On 15/09/15 13:36, Tanu Kaskinen wrote:
> I think user-session should be enabled by default when systemd is in
> DISTRO_FEATURES. Some services, e.g. PulseAudio, can fully enable their
> systemd integration only if dbus is compiled with --enable-user
> -session.
I think so too, but I think it's
Some (host) systems only have a binary named 'gpg' (e.g. Fedora) while
some only have 'gpg2' (Ubuntu) and others have both of them (openSUSE).
Currently the behavior of rpm-native with regards to GnuPG depends on
the host platform: rpm(-native) is configured to use GnuPG binary of the
host system
Currently python-misc is not included even if python-modules is. This means
some python scripts fail even if python-modules is included in the image (for
example, get-pip.py at bootrap.pypa.io/get-pip.py). This patch adds python-misc
as runtime dependency for python-modules.
Signed-off-by:
On 9/15/15 3:23 AM, Luo Zhenhua wrote:
> Hello all,
>
>
>
> Currently to support 32b and 64b build for same core in Yocto, two separated
> compilers need to be generated. Is there plan to support multilib build(32b
> and
> 64b) by single toolchain which is generated by Yocto in future?
>
On 2015-09-15 07:05, Markus Lehtonen wrote:
Some (host) systems only have a binary named 'gpg' (e.g. Fedora) while
some only have 'gpg2' (Ubuntu) and others have both of them (openSUSE).
Currently the behavior of rpm-native with regards to GnuPG depends on
the host platform: rpm(-native) is
56 matches
Mail list logo