[OE-core] [PATCH 0/1] ghostscript: upgrade to 9.07

From: Wenzong Fan Upgrade ghostscript from 9.05 to 9.07. Remove unuseful patch: * 0001-make-ghostscript-work-with-long-building-directory.patch Port applicable patches: * ghostscript-9.02-genarch.patch * ghostscript-9.02-parallel-make.patch * ghostscript-9.02-prevent_recompiling.pat

Re: [OE-core] [PATCH 1/3] sanity.bbclass: Check for the known broken version of make

On 6/24/13 5:09 PM, Saul Wold wrote: On 06/24/2013 07:45 AM, Mark Hatle wrote: See GNU Savannah bug 30612 -- make 3.82 is known to be broken. A number of vendors are providing a modified version, so checking for just the version string is not enough. We also need to check if the patch for the

Re: [OE-core] [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.

On 6/24/2013 11:23 PM, Richard Purdie wrote: On Mon, 2013-06-24 at 08:18 -0700, Saul Wold wrote: On 06/24/2013 12:45 AM, jhuang0 wrote: On 6/24/2013 3:23 PM, Paul Barker wrote: On 24 Jun 2013 07:28, mailto:jackie.hu...@windriver.com>> wrote: > > From: Jackie Huang mailto:jackie.hu...@w

Re: [OE-core] [PATCH 1/3] sanity.bbclass: Check for the known broken version of make

On 06/24/2013 07:45 AM, Mark Hatle wrote: See GNU Savannah bug 30612 -- make 3.82 is known to be broken. A number of vendors are providing a modified version, so checking for just the version string is not enough. We also need to check if the patch for the issue has been applied. We use a modi

[OE-core] OE Changelog since 2013-06-16 until 2013-06-23

Changelog since 2013-06-16 until 2013-06-23. Projects included in this report: bitbake: git://git.openembedded.org/bitbake openembedded-core: git://git.openembedded.org/openembedded-core meta-openembedded: git://git.openembedded.org/meta-openembedded meta-angstrom: git://github.com/Angstrom-distr

[OE-core] [danny][PATCH] classes/package_rpm: avoid bash being pulled in unnecessarily

The initial installation step for base-passwd, base-files and shadow will pull in bash if any of these packages depend on /bin/sh and a bash package has been built, which is undesirable if you are using busybox; so force the early installation of one or the other depending on which is going to be i

Re: [OE-core] [PATCH] buildtools-tarball: Change the way the SDK is sanitized

On Mon, Jun 24, 2013 at 9:10 AM, Hatle, Mark wrote: > Stupid phone will only allow me to top post. Anyway, that line was copied > out of the populate_sdk bbclass. So if it is a bash-ism then it needs to be > fixed there as well. > > > -Original Message- > *From: *Paul Eggleton [paul.eggle.

Re: [OE-core] [PATCH] buildtools-tarball: Change the way the SDK is sanitized

Stupid phone will only allow me to top post. Anyway, that line was copied out of the populate_sdk bbclass. So if it is a bash-ism then it needs to be fixed there as well. -Original Message- From: Paul Eggleton [paul.eggle...@linux.intel.com] Sent: M

Re: [OE-core] [PATCH] buildtools-tarball: Change the way the SDK is sanitized

On Monday 24 June 2013 16:31:13 Paul Eggleton wrote: > On Monday 24 June 2013 09:47:15 Mark Hatle wrote: > > + script=${1:-${SDK_OUTPUT}/${SDKPATH}/environment-setup-${SDK_SYS}} > > I could be wrong but I think this may be a bashism... Actually, I spoke too soon, it isn't. Ignore me... Cheers,

Re: [OE-core] [PATCH] buildtools-tarball: Change the way the SDK is sanitized

On Monday 24 June 2013 09:47:15 Mark Hatle wrote: > + script=${1:-${SDK_OUTPUT}/${SDKPATH}/environment-setup-${SDK_SYS}} I could be wrong but I think this may be a bashism... Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ O

Re: [OE-core] [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.

On Mon, 2013-06-24 at 08:18 -0700, Saul Wold wrote: > On 06/24/2013 12:45 AM, jhuang0 wrote: > > > > > > On 6/24/2013 3:23 PM, Paul Barker wrote: > >> On 24 Jun 2013 07:28, >> > wrote: > >> > > >> > From: Jackie Huang >> > >

Re: [OE-core] [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.

On 06/24/2013 12:45 AM, jhuang0 wrote: On 6/24/2013 3:23 PM, Paul Barker wrote: On 24 Jun 2013 07:28, mailto:jackie.hu...@windriver.com>> wrote: > > From: Jackie Huang mailto:jackie.hu...@windriver.com>> > > The code relies on hardware specific memory locations to access > and modify the

[OE-core] [PATCH] busybox: Add ptest

Install busybox test suite and run it as ptest. Signed-off-by: Anders Roxell Signed-off-by: Björn Stenberg --- meta/recipes-core/busybox/busybox.inc |2 +- meta/recipes-core/busybox/busybox_1.20.2.bb |7 +++ meta/recipes-core/busybox/files/run-ptest |7 +++ 3 files c

[OE-core] [PATCH] buildtools-tarball: Change the way the SDK is sanitized

The previous method of shrinking down the scale of the environment-setup file would not work properly when the target is configured with multilibs. In addition, the configured machine name and similar settings could leak into the SDK naming. This was resolved by clearing the SDK generated files a

[OE-core] [PATCH 3/3] buildtools-tarball: Add nativesdk-make

Recently it was discovered that many Fedora hosts have a broken version of make 3.82. Add make to the buildtools-tarball, as well ad modify make to support building a special nativesdk version. Signed-off-by: Mark Hatle --- meta/recipes-core/meta/buildtools-tarball.bb | 3 ++- meta/recipes-devt

[OE-core] [PATCH 0/3] Update the sanity check and make

The sanity check should also look for the broken version of make. Our version of make also happens to be broken, so fix that as well. And add nativesdk-make to the buildtools-tarball, to assist people with broken buildtools. (Note, current Fedora and CentOS machines contain the broken make as we

[OE-core] [PATCH 2/3] make: Fix second part of bug Savannah 30612

The Savannah bug 30612 describes two different issue. The first, previously fixed, errors parsing multiple objects in parenthesis. The second, (this issue), extra white space contained in the parenthesis. The fix was backported from the current make git tree: http://git.savannah.gnu.org/cgit/make

[OE-core] [PATCH 1/3] sanity.bbclass: Check for the known broken version of make

See GNU Savannah bug 30612 -- make 3.82 is known to be broken. A number of vendors are providing a modified version, so checking for just the version string is not enough. We also need to check if the patch for the issue has been applied. We use a modified version of the reproduced to check for

[OE-core] [PATCH] gcc: When cross compiling a target gcc, target flags may be used on the host

The original fix worked some of the time, but not on all machines. Fix this by applying the change in a different way. Following the example of the existing BUILD_CFLAGS. Below is the commit message from the original change to help explain why this is needed: Configure identifies a number of wa

[OE-core] [PATCH] systemtap: Systemtap can not be build w -O0 optimization

Systemtap will fail with: ../usr/include/features.h:330:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) Use the same technique that eglibc uses to catch and correct the optimization

[OE-core] [PATCH] linux-firmware: Package some iwlwifi firmware separately

Taken from meta-intel, might as well merge this into the core recipe. Signed-off-by: Richard Purdie --- diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb index 780cca8..f586321 100644 --- a/meta/recipes-kernel/linux-f

[OE-core] [PATCH 1/4] gst-plugins-bad: use correct option when enabling librsvg

Signed-off-by: Ross Burton --- meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb b/meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb index 80a

[OE-core] [PATCH 2/4] gst-plugins-bad: tremor was moved from here to -base

Signed-off-by: Ross Burton --- meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb b/meta/recipes-multimedia/gstreamer/gst-plugins-bad_0.10.23.bb index

[OE-core] [PATCH 0/4] GStreamer 0.10 improvements

Hi, Found these sitting in a branch that was never sent. Two small fixes and then element selection cleanup to use PACKAGECONFIG. Ross The following changes since commit edcbb79583e1577cb64d368e3902915dea50a96e: ref-manual: Added note about issues on supported distros (2013-06-21 14:26:31 +

[OE-core] [PATCH 4/4] gst-plugins-bad: element selection rationalisation

Using --with-plugins means you only get the elements you enable, so we were dropping vast numbers of useful plugins such as the MPEG muxers. Instead, follow gst-plugins-base by using PACKAGECONFIG to enable/disable plugins with optional dependencies. Signed-off-by: Ross Burton --- .../gstreamer

[OE-core] [PATCH 3/4] gst-plugins-base: element selection rationalisation

Use PACKAGECONFIG to control the X11 elements, and add statements for the elements that we don't always enable. Remove the freetype dependency as it's apparently (but not really) only needed by the examples. Signed-off-by: Ross Burton --- .../gstreamer/gst-plugins-base_0.10.36.bb

Re: [OE-core] [PATCH v6] systemd: added python-systemd package generation.

On Sun, Jun 23, 2013 at 01:21:07PM +0300, Yevhen Kyriukha wrote: > Oh, yes. > You should move "pythonnative python-dir" from DEPENDS and append to inherit. me? it's your patch, please send v7. > 2013/6/23 Martin Jansa : > > -DEPENDS = "kmod docbook-sgml-dtd-4.1-native intltool-native gperf-native

[OE-core] [PATCH v2] bash ptest: Sed away the Makefile dependency to remove error messages.

From: Björn Stenberg The bash Makefile defines a dependency on itself and tries to run configure, causing error messages when running ptest on target: make: *** No rule to make target `configure.in', needed by `configure'. make: *** No rule to make target `aclocal.m4', needed by `configure'. ma

Re: [OE-core] [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.

On 6/24/2013 3:23 PM, Paul Barker wrote: On 24 Jun 2013 07:28, mailto:jackie.hu...@windriver.com>> wrote: > > From: Jackie Huang mailto:jackie.hu...@windriver.com>> > > The code relies on hardware specific memory locations to access > and modify the keyboard repeat rate. It also requires

Re: [OE-core] [PATCH 1/1] Limit the kbdrate application to x86, mips and sparc.

On 24 Jun 2013 07:28, wrote: > > From: Jackie Huang > > The code relies on hardware specific memory locations to access > and modify the keyboard repeat rate. It also requires read/write > access to /dev/port which doesn't exist on every architecture's > root fs. The defect was raised for Qemu