Re: [OE-core] [PATCH 1/1] sstate.bbclass: fix parallel building issue

On Wed, Aug 14, 2013 at 01:28:53PM +0800, Rongqing Li wrote: > > > On 08/14/2013 03:02 AM, Saul Wold wrote: > > On 08/13/2013 01:20 AM, rongqing...@windriver.com wrote: > >> From: "Roy.Li" > >> > >> sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then > >> sstate_create_package

Re: [OE-core] [dylan]devshell: broken

On Wed, Aug 14, 2013 at 7:54 AM, Andre wrote: > bitbake -c devshell seems to have stopped working (tested with xterm > and mate-terminal) in dylan since this commit: > > a749f06 terminal: Run command using a wrapper script > > It looks like the run.do_devshell. script is generated but then > fa

[OE-core] [dylan]devshell: broken

bitbake -c devshell seems to have stopped working (tested with xterm and mate-terminal) in dylan since this commit: a749f06 terminal: Run command using a wrapper script It looks like the run.do_devshell. script is generated but then fails to run when passed to a terminal. A possible clue is th

Re: [OE-core] [PATCH 1/1] sstate.bbclass: fix parallel building issue

On 08/14/2013 03:02 AM, Saul Wold wrote: On 08/13/2013 01:20 AM, rongqing...@windriver.com wrote: From: "Roy.Li" sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then sstate_create_package will store SSTATE_BUILDDIR into a archive file by tar, but once other packages install

Re: [OE-core] [PATCH 1/1] coreutils: allow for acl support

> -Original Message- > From: Saul Wold [mailto:s...@linux.intel.com] > Sent: Tuesday, August 13, 2013 2:48 PM > To: Slater, Joseph > Cc: openembedded-core@lists.openembedded.org > Subject: Re: [OE-core] [PATCH 1/1] coreutils: allow for acl support > > On 08/13/2013 02:20 PM, Joe Slater w

Re: [OE-core] Yocto toolchain for Windows

Hi Richard, I've tried the sdk on windows and here're the issues that I've run into: 1. in our sysroot all the libraries have .so we need to change them to .dll 2. seems the cross compiler i586-poky-linux-gcc.exe relies on libiconv-2.dll, so I manually installed that dll. 3. Now when I run i586-p

Re: [OE-core] [PATCH 1/1] coreutils: allow for acl support

On 08/13/2013 02:20 PM, Joe Slater wrote: CQID: 430353 Define PACKAGECONFIG info for acl assuming it might be a DISTRO_FEATURE. Thanks for the Patch! Will you be doing the same for the GPLv2 version? I guess this means we should be expecting a set of patches to enable other recipes that ha

[OE-core] [PATCH 1/1] coreutils: allow for acl support

CQID: 430353 Define PACKAGECONFIG info for acl assuming it might be a DISTRO_FEATURE. Signed-off-by: Joe Slater --- meta/recipes-core/coreutils/coreutils_8.21.bb | 14 +++--- 1 files changed, 11 insertions(+), 3 deletions(-) diff --git a/meta/recipes-core/coreutils/coreutils_8.21.bb

Re: [OE-core] [PATCH 2/2 v3] meta-skeleton: Add busybox config fragment example

On Tue, 2013-08-13 at 11:01 -0700, Saul Wold wrote: > This shows an example of the config fragment support that > both the linux-yocto and busybox recipes use. This example > is specific to busybox. > > By adding busybox CONFIG options into a .cfg file and then > adding that .cfg file to SRC_URI t

Re: [OE-core] Yocto toolchain for Windows

On Aug 13, 2013, at 1:11 PM, Richard Purdie wrote: > On Tue, 2013-08-13 at 09:17 -0700, Khem Raj wrote: >> On Aug 12, 2013, at 6:34 AM, Francois Retief >> wrote: > >>> My understanding is that MinGW is the libc library for Win32 >>> environments. So we need to "replace" eglibc with mingw for

Re: [OE-core] Yocto toolchain for Windows

On Tue, 2013-08-13 at 09:17 -0700, Khem Raj wrote: > On Aug 12, 2013, at 6:34 AM, Francois Retief > wrote: > > My understanding is that MinGW is the libc library for Win32 > > environments. So we need to "replace" eglibc with mingw for all code > > that execute on the Win32 platform. In the case

Re: [OE-core] Enabling x264 support in gstreamer

On Tue, Aug 13, 2013 at 08:36:09PM +0100, Phil Blundell wrote: > On Tue, 2013-08-13 at 13:26 -0600, Gary Thomas wrote: > > On 2013-08-13 11:36, Martin Jansa wrote: > > > On Tue, Aug 13, 2013 at 11:29:10AM -0600, Gary Thomas wrote: > > >> I see that some of the gstreamer recipes have changed so that

Re: [OE-core] Enabling x264 support in gstreamer

On Tuesday 13 August 2013 12:37:19 Mark Hatle wrote: > On 8/13/13 12:29 PM, Gary Thomas wrote: > > I see that some of the gstreamer recipes have changed so that x264 > > is now a PACKAGECONFIG option. However, I don't see anything that > > enables this option anywhere. > > > > How do I get x264 s

Re: [OE-core] Enabling x264 support in gstreamer

On Tuesday 13 August 2013 20:36:09 Phil Blundell wrote: > On Tue, 2013-08-13 at 13:26 -0600, Gary Thomas wrote: > > On 2013-08-13 11:36, Martin Jansa wrote: > > > On Tue, Aug 13, 2013 at 11:29:10AM -0600, Gary Thomas wrote: > > >> I see that some of the gstreamer recipes have changed so that x264 >

Re: [OE-core] Enabling x264 support in gstreamer

On Tue, 2013-08-13 at 13:26 -0600, Gary Thomas wrote: > On 2013-08-13 11:36, Martin Jansa wrote: > > On Tue, Aug 13, 2013 at 11:29:10AM -0600, Gary Thomas wrote: > >> I see that some of the gstreamer recipes have changed so that x264 > >> is now a PACKAGECONFIG option. However, I don't see anythin

Re: [OE-core] Enabling x264 support in gstreamer

On 2013-08-13 11:36, Martin Jansa wrote: On Tue, Aug 13, 2013 at 11:29:10AM -0600, Gary Thomas wrote: I see that some of the gstreamer recipes have changed so that x264 is now a PACKAGECONFIG option. However, I don't see anything that enables this option anywhere. How do I get x264 support bac

Re: [OE-core] [PATCH 1/1] sstate.bbclass: fix parallel building issue

On 08/13/2013 01:20 AM, rongqing...@windriver.com wrote: From: "Roy.Li" sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then sstate_create_package will store SSTATE_BUILDDIR into a archive file by tar, but once other packages install the same file into sysroot, the creating the

[OE-core] [V2][PATCH 1/1] openjade: do not produce shared libraries

CQID: 429576 openjade is the only one that uses the shared libraries and sometimes it cannot find them! Signed-off-by: Joe Slater --- .../openjade/openjade-native_1.3.2.bb | 29 ++- 1 files changed, 21 insertions(+), 8 deletions(-) diff --git a/meta/recipes-devto

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On Tue, Aug 13, 2013 at 2:11 PM, Saul Wold wrote: > This shows an example of the config fragment support that > both the linux-yocto and busybox recipes use. This example > is specific to busybox. > > By adding busybox CONFIG options into a .cfg file and then > adding that .cfg file to SRC_URI the

Re: [OE-core] [PATCH v2] linux-dtb: Use kernel build system to generate the dtb files

On 13-08-13 09:52 AM, Otavio Salvador wrote: As the Linux kernel, unconditionally, builds the dtc application and it is the compatible version with the DeviceTree files shipped within the kernel it is better to use it and the kernel build system to generate the dtb files. Some DeviceTree files r

Re: [OE-core] [CONSOLIDATED PULL 00/24] Final Review & ACK

On 13 August 2013 18:49, Saul Wold wrote: > Richard: > > This will be ready to pull after Paul and Ross Ack. > > I fixed the groff patches for GPLv2 and updated Stefan's patch, > other than that no changes. Acked-By: Ross Burton Ross ___ Openembedded-

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On Tue, Aug 13, 2013 at 1:58 PM, Mark Hatle wrote: > On 8/13/13 12:40 PM, Laszlo Papp wrote: >> >> On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle > > wrote: >> >> On 8/13/13 12:23 PM, Laszlo Papp wrote: >> >> s/which files/which lines/ >> >> >> The ker

[OE-core] [PATCH 2/2 v3] meta-skeleton: Add busybox config fragment example

This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cfg file to SRC_URI the merge_config.sh script will correctly handle these CONFIG opt

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On 8/13/13 12:40 PM, Laszlo Papp wrote: On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle mailto:mark.ha...@windriver.com>> wrote: On 8/13/13 12:23 PM, Laszlo Papp wrote: s/which files/which lines/ The kernel configuration mechanism has a tool that will combine the original conf

[OE-core] [CONSOLIDATED PULL 00/24] Final Review & ACK

Richard: This will be ready to pull after Paul and Ross Ack. I fixed the groff patches for GPLv2 and updated Stefan's patch, other than that no changes. Sau! The following changes since commit 5c11cf4db8f43003fb7132b92a78659f70f07ce0: checkroot.sh: respect the value of ENABLE_ROOTFS_FSCK (20

[OE-core] [PATCH] qemu: Skip it for mips64 target

We should not skip it always since same recipes provide qemu-native too so user class-target override to make it only skip for target recipes Signed-off-by: Khem Raj --- meta/recipes-devtools/qemu/qemu.inc | 1 + meta/recipes-devtools/qemu/qemu_1.5.0.bb | 2 +- meta/recipes-devtools/qemu/qe

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On 08/13/2013 10:26 AM, Mark Hatle wrote: On 8/13/13 12:11 PM, Saul Wold wrote: This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cf

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle wrote: > On 8/13/13 12:23 PM, Laszlo Papp wrote: > >> s/which files/which lines/ >> > > The kernel configuration mechanism has a tool that will combine the > original configuration, and any listed configuration fragments (.cfg > files). It will combine

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On Tue, 2013-08-13 at 12:26 -0500, Mark Hatle wrote: > On 8/13/13 12:11 PM, Saul Wold wrote: > > This shows an example of the config fragment support that > > both the linux-yocto and busybox recipes use. This example > > is specific to busybox. > > > > By adding busybox CONFIG options into a .cfg

Re: [OE-core] Enabling x264 support in gstreamer

On 8/13/13 12:29 PM, Gary Thomas wrote: I see that some of the gstreamer recipes have changed so that x264 is now a PACKAGECONFIG option. However, I don't see anything that enables this option anywhere. How do I get x264 support back - it was working with Poky/Yocto just a few weeks back... No

Re: [OE-core] Enabling x264 support in gstreamer

On Tue, Aug 13, 2013 at 11:29:10AM -0600, Gary Thomas wrote: > I see that some of the gstreamer recipes have changed so that x264 > is now a PACKAGECONFIG option. However, I don't see anything that > enables this option anywhere. > > How do I get x264 support back - it was working with Poky/Yocto

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On 8/13/13 12:23 PM, Laszlo Papp wrote: s/which files/which lines/ The kernel configuration mechanism has a tool that will combine the original configuration, and any listed configuration fragments (.cfg files). It will combine these, and then filter them in such a way that last-in wins. S

[OE-core] Enabling x264 support in gstreamer

I see that some of the gstreamer recipes have changed so that x264 is now a PACKAGECONFIG option. However, I don't see anything that enables this option anywhere. How do I get x264 support back - it was working with Poky/Yocto just a few weeks back... Note: I have imported meta-oe/recipes-multi

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

On 8/13/13 12:11 PM, Saul Wold wrote: This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cfg file to SRC_URI the merge_config.sh scrip

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

s/which files/which lines/ On Tue, Aug 13, 2013 at 6:23 PM, Laszlo Papp wrote: > How will this know which files exactly to disregard in the busybox include > file (".inc")? > > Could you please give that to the commit message as explanation? > > > On Tue, Aug 13, 2013 at 6:11 PM, Saul Wold wro

Re: [OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

How will this know which files exactly to disregard in the busybox include file (".inc")? Could you please give that to the commit message as explanation? On Tue, Aug 13, 2013 at 6:11 PM, Saul Wold wrote: > This shows an example of the config fragment support that > both the linux-yocto and bu

Re: [OE-core] [PATCH 2/2] meta-skeleton: Add busybox config fragment example

On Tue, 2013-08-13 at 09:44 -0700, Saul Wold wrote: > This shows an example of the config fragment support that > both the linux-yocto and busybox recipes use. This example > is specific to busybox. > > By adding busybox CONFIG options into a .cfg file and then > adding that .cfg file to SRC_URI t

[OE-core] [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example

This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cfg file to SRC_URI the merge_config.sh script will correctly handle these CONFIG opt

[OE-core] [PATCH 1/2] meta-skeleton: layer.conf should also have .bbappend in BBFILES

This will allow for an example recipe with a .bbappend to be found, such as busybox or kernel configure fragments. Signed-off-by: Saul Wold --- meta-skeleton/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-skeleton/conf/layer.conf b/meta-skeleton/conf/lay

[OE-core] [PATCH 2/2] meta-skeleton: Add busybox config fragment example

This shows an example of the config fragment support that both the linux-yocto and busybox recipes use. This example is specific to busybox. By adding busybox CONFIG options into a .cfg file and then adding that .cfg file to SRC_URI the merge_config.sh script will correctly handle these CONFIG opt

Re: [OE-core] Yocto toolchain for Windows

On Aug 12, 2013, at 6:34 AM, Francois Retief wrote: > Hi Krzysztof, > > My understanding is that MinGW is the libc library for Win32 environments. So > we need to "replace" eglibc with mingw for all code that execute on the Win32 > platform. In the case of OpenEmbedded, it is all packages th

Re: [OE-core] [PATCH v2] connman: fix systemd support for connman-* packages.

2013/8/13 Saul Wold : > On 08/13/2013 04:26 AM, Yevhen Kyriukha wrote: >> >> This patch fixes systemd's postinst/postrm script generation. >> >> Signed-off-by: Yevhen Kyriukha >> --- >> meta/recipes-connectivity/connman/connman.inc | 8 >> 1 file changed, 8 insertions(+) >> >> diff --g

Re: [OE-core] [PATCH v2] connman: fix systemd support for connman-* packages.

On 08/13/2013 04:26 AM, Yevhen Kyriukha wrote: This patch fixes systemd's postinst/postrm script generation. Signed-off-by: Yevhen Kyriukha --- meta/recipes-connectivity/connman/connman.inc | 8 1 file changed, 8 insertions(+) diff --git a/meta/recipes-connectivity/connman/connman.

Re: [OE-core] [CONSOLIDATED PULL 00/24] Review & ACK

On Tue, 2013-08-13 at 07:36 -0700, Saul Wold wrote: > Paul, Ross: > > We are still in Review and ACK mode, so please take a look at this. > > I have included the dpkg fix for Fedora 19. > > This also has some patch for the QA Tests and Paul's Gstreamer > patches. > Saul, you always move too

[OE-core] [PATCH v2] oeqa/utils/qemurunner: get ip old fashioned way and use tcp serial console

The way we read data from the serial console was unreliable and blocking (AutoBuilder seems to hit that often), so change the serial console type from unix socket to tcp and reverse the connection - don't let qemu act as server (wait for a connection). So now the serial console is used to save t

[OE-core] [CONSOLIDATED PULL 00/24] Review & ACK

Paul, Ross: We are still in Review and ACK mode, so please take a look at this. I have included the dpkg fix for Fedora 19. This also has some patch for the QA Tests and Paul's Gstreamer patches. Thanks Sau! The following changes since commit 5c11cf4db8f43003fb7132b92a78659f70f07ce0:

[OE-core] [PATCH v2] linux-dtb: Use kernel build system to generate the dtb files

As the Linux kernel, unconditionally, builds the dtc application and it is the compatible version with the DeviceTree files shipped within the kernel it is better to use it and the kernel build system to generate the dtb files. Some DeviceTree files rely on CPP and kernel headers to be able to gen

Re: [OE-core] [PATCH] linux-dtb: Use kernel build system to generate the dtb files

On 13-08-13 09:35 AM, Otavio Salvador wrote: On Tue, Aug 13, 2013 at 10:06 AM, Bruce Ashfield wrote: On 13-08-13 08:46 AM, Otavio Salvador wrote: On Tue, Aug 13, 2013 at 12:40 AM, Bruce Ashfield wrote: On 13-08-12 11:37 AM, Otavio Salvador wrote: As the Linux kernel, unconditionally, bu

Re: [OE-core] [PATCH] linux-dtb: Use kernel build system to generate the dtb files

On Tue, Aug 13, 2013 at 10:06 AM, Bruce Ashfield wrote: > On 13-08-13 08:46 AM, Otavio Salvador wrote: >> >> On Tue, Aug 13, 2013 at 12:40 AM, Bruce Ashfield >> wrote: >>> >>> On 13-08-12 11:37 AM, Otavio Salvador wrote: As the Linux kernel, unconditionally, builds the dtc applicat

Re: [OE-core] [PATCH] linux-dtb: Use kernel build system to generate the dtb files

On 13-08-13 08:46 AM, Otavio Salvador wrote: On Tue, Aug 13, 2013 at 12:40 AM, Bruce Ashfield wrote: On 13-08-12 11:37 AM, Otavio Salvador wrote: As the Linux kernel, unconditionally, builds the dtc application and it is the compatible version with the DeviceTree files shipped within the kern

Re: [OE-core] [PATCH] linux-dtb: Use kernel build system to generate the dtb files

On Tue, Aug 13, 2013 at 12:40 AM, Bruce Ashfield wrote: > On 13-08-12 11:37 AM, Otavio Salvador wrote: >> >> As the Linux kernel, unconditionally, builds the dtc application and >> it is the compatible version with the DeviceTree files shipped within >> the kernel it is better to use it and the ke

[OE-core] [PATCH v2] connman: fix systemd support for connman-* packages.

This patch fixes systemd's postinst/postrm script generation. Signed-off-by: Yevhen Kyriukha --- meta/recipes-connectivity/connman/connman.inc | 8 1 file changed, 8 insertions(+) diff --git a/meta/recipes-connectivity/connman/connman.inc b/meta/recipes-connectivity/connman/connman.in

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On Tue, Aug 13, 2013 at 11:35 AM, Jack Mitchell wrote: > On 13/08/13 11:19, Laszlo Papp wrote: > > I personally dislike top posting for a single entity in an email and I > > think that is "nigh unbearable". ;-) > > If you also have a dislike for top-posting, then why top-post?! > That is a clear

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On 13/08/13 11:19, Laszlo Papp wrote: > I personally dislike top posting for a single entity in an email and I > think that is "nigh unbearable". ;-) If you also have a dislike for top-posting, then why top-post?! > > More to the point, if there is no documentation, why is the bugreport > closed

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

I personally dislike top posting for a single entity in an email and I think that is "nigh unbearable". ;-) More to the point, if there is no documentation, why is the bugreport closed rather than forming it into a documentation bugreport? Also, I am still not sure we are on the same paper. You m

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

There's no magic involved in the python function: all it does is generate a config fragment which is then passed to merge_config.sh along with everything else. If you supply your own fragment as Ross suggested then it should override the values from the Python-generated one and everything ought to

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On 13/08/13 10:52, Laszlo Papp wrote: > As we have already discussed that, it is not any clear at all without > example. Yes, the end user does not really care about the internal > implementation of the feature > > Please provide useful examples and tutorials how to use a feature > especially

[OE-core] [PATCH 2/2] insane: don't abort if workdir is not TMPDIR/work

The BASE_WORKDIR variable can be used instead of enforcing WORKDIR being TMPDIR/work (and aborting the build if it isn't). Signed-off-by: Ross Burton --- meta/classes/insane.bbclass |5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/meta/classes/insane.bbclass b/meta/clas

[OE-core] [PATCH 1/2] bitbake.conf: define WORKDIR in terms of BASE_WORKDIR

To make it easier to move WORKDIR, define it using the new variable BASE_WORKDIR, which is the root of the work directory. Signed-off-by: Ross Burton --- meta/conf/bitbake.conf |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.con

[OE-core] [RFC][PATCH 0/2] WORKDIR and insane tweaks

Hi, Last night I was attempting a build with WORKDIR in a tmpfs to see what impact it made on build time (the results were fairly interesting, I'll write them up shortly). I noticed that to move WORKDIR I had to replicate the full WORKDIR path logic, which was a bit irritating but not that seriou

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

Why are you referring to defconfig when I mentioned several times, the problem is the inc file and a python function; i.e. not the kernel, nor the busybox config? On Tue, Aug 13, 2013 at 10:58 AM, Burton, Ross wrote: > On 13 August 2013 10:52, Laszlo Papp wrote: > > As we have already discussed

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On 13 August 2013 10:52, Laszlo Papp wrote: > As we have already discussed that, it is not any clear at all without > example. Yes, the end user does not really care about the internal > implementation of the feature > > Please provide useful examples and tutorials how to use a feature especi

[OE-core] [PATCH 1/1] dpkg: fix include header caused compile error

Build dpkg-native on Fedora 19, it fails with: /usr/include/c++/4.8.1/cstdlib: In function ‘long long int std::abs(long long int)’: /usr/include/c++/4.8.1/cstdlib:174:20: error: declaration of C function ‘long long int std::abs(long long int)’ conflicts with abs(long long __x) { return __buil

[OE-core] [PATCH 0/1] Fix dpkg-native compile fail on Fedora 19

The following changes since commit 16d522bcd1f1b7741577fa31fab7e2129da0cae9: maintainers.inc: reassign maintainers, remove obsolete recipes (2013-08-12 13:13:05 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/dpkg-native http://git.pokylinux.org

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

So, please show me how it works for this use case. Note this is note defconfig, and has not much relevance to the kernel which is apparently mentioned for some reason. diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc index acd2bfb..0e84f4c 100644 --- a/met

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

As we have already discussed that, it is not any clear at all without example. Yes, the end user does not really care about the internal implementation of the feature Please provide useful examples and tutorials how to use a feature especially when a user (and apparently others posting here)

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On 13 August 2013 08:32, Laszlo Papp wrote: > So, everyone suggested PACKAGECONFIG in here on the mailing list except Khem > whose reply I did not get. > > Yet, 4964 got closed by the "team". Could anyone please give a sane > description why and what would block the end users other than fork? Quo

[OE-core] [PATCH][V2] cogl: GL/GLX feature cleanup

Separate GL and GLX flags don't make sense, as on Linux GL means GLX and GLX means GL. So, default to GLESv2 and GLX if X11 is enabled. EGL on X11 doesn't have feature parity yet so leave it disabled by default. Signed-off-by: Ross Burton --- meta/recipes-graphics/cogl/cogl-1.0.inc | 17

[OE-core] [PATCH 0/1] sstate.bbclass: fix parallel building issue

From: "Roy.Li" The following changes since commit 8dbb6fdca32785d91d6380e3722720714f8140e8: man-pages: upgrade to 3.53 (2013-08-05 23:59:59 -0700) are available in the git repository at: git://git.pokylinux.org/poky-contrib roy/sstat http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=

[OE-core] [PATCH 1/1] sstate.bbclass: fix parallel building issue

From: "Roy.Li" sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then sstate_create_package will store SSTATE_BUILDDIR into a archive file by tar, but once other packages install the same file into sysroot, the creating the archive file will fail with below error: DEBUG: Execu

[OE-core] [PATCH_V3] systemtap: upgrade to 2.3

Disabled javac and jar. Signed-off-by: Cristiana Voicu --- meta/recipes-kernel/systemtap/systemtap_git.bb |6 +++--- meta/recipes-kernel/systemtap/systemtap_git.inc |4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/meta/recipes-kernel/systemtap/systemtap_git.bb b/

[OE-core] [PATCH 1/1] opkg.inc: remove the obsolete POSTLOG variable

From: Chen Qi With the current implementation of postinst logging mechanism, the location for log file is configured via the POSTINST_LOGFILE variable. The POSTLOG variable is obsolete now, thus removing it. Signed-off-by: Chen Qi --- meta/recipes-devtools/opkg/opkg.inc |2 -- 1 file chan

[OE-core] [PATCH 0/1] opkg.inc: remove the obsolete POSTLOG

From: Chen Qi The following changes since commit 16d522bcd1f1b7741577fa31fab7e2129da0cae9: maintainers.inc: reassign maintainers, remove obsolete recipes (2013-08-12 13:13:05 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/opkg-remove-POSTLOG

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

On Tue, Aug 13, 2013 at 8:32 AM, Laszlo Papp wrote: > So, everyone suggested PACKAGECONFIG in here on the mailing list except > Khem whose reply I did not get. > > Yet, 4964 got closed by the "team". Could anyone please give a sane > description why and what would block the end users other than f

Re: [OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

So, everyone suggested PACKAGECONFIG in here on the mailing list except Khem whose reply I did not get. Yet, 4964 got closed by the "team". Could anyone please give a sane description why and what would block the end users other than fork? On Tue, Aug 6, 2013 at 8:36 AM, Laszlo Papp wrote: > W

Re: [OE-core] [PATCH_V2] systemtap: upgrade to 2.3

Just saw that there is a little change for systemtap on master and this patch will fail. I will send a new version. Cristiana -Original Message- From: Voicu, Cristiana Sent: Tuesday, August 13, 2013 10:11 AM To: openembedded-core@lists.openembedded.org Cc: Voicu, Cristiana Subject: [PATC

[OE-core] [PATCH 0/1] oe/path.py: call /bin/cp directly

From: Wenzong Fan This avoids running cp with interactive mode on some hosts if defined: alias cp='cp -i' The following changes since commit 16d522bcd1f1b7741577fa31fab7e2129da0cae9: maintainers.inc: reassign maintainers, remove obsolete recipes (2013-08-12 13:13:05 +0100) are

[OE-core] [PATCH 1/1] oe/path.py: call /bin/cp directly

From: Wenzong Fan This avoids running cp with interactive mode if defined: alias cp='cp -i' Signed-off-by: Wenzong Fan --- meta/lib/oe/path.py |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py index da044ba..6933977 100644 ---

[OE-core] [PATCH_V2] systemtap: upgrade to 2.3

Disabled javac and jar. Signed-off-by: Cristiana Voicu --- meta/recipes-kernel/systemtap/systemtap_git.bb |6 +++--- meta/recipes-kernel/systemtap/systemtap_git.inc |4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/meta/recipes-kernel/systemtap/systemtap_git.bb b/