On Fri, 2016-02-05 at 21:04 +, Burton, Ross wrote:
> Hi,
>
> On 5 February 2016 at 20:55, Nicolas Dechesne <
> nicolas.deche...@linaro.org> wrote:
> > > Agreed - some may not want openssl at all and being able to
> > switch it for
> > > another alternative would be useful.
> >
> > sure. but,
Machine specific over-rides for mtx-1 (aka MeshCube) and
mtx-2 (aka SurfBox 2nd generation) don't belong in oe-core.
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl.inc | 4
1 file changed, 4 deletions(-)
diff --git a/meta/recipes-connectivity/openssl/openssl.inc
On Fri, Feb 5, 2016 at 3:26 PM, Burton, Ross wrote:
>
> On 5 February 2016 at 10:25, Jens Rehsack wrote:
>>
>> Add patch from commit 96b1b5c127e9e0e637aaf7948cf3330a94a5cd57 to
>> cross-localedef-native
>> to avoid broken images built with ENABLE_BINARY_LOCALE_GENERATION set to
>> 1:
>
>
> This i
The dependency on freetype was dropped shortly after the 1.7.1 release
so is no longer required for the git recipe.
http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=183610c035dd6955c9b3540b940aec50474af031
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gs
musl libc generates warnings if is included directly.
The warnings only cause problems for the git versions (-Werror is
turned off for GStreamer stable releases).
Signed-off-by: Andre McCurdy
---
.../avoid-including-sys-poll.h-directly.patch | 30 ++
.../gstreamer/gstr
musl libc generates warnings if is included directly.
The warnings only cause problems for the git versions (-Werror is
turned off for GStreamer stable releases), but since can
be conviently disabled via configure let's avoid it for all versions.
Signed-off-by: Andre McCurdy
---
meta/recipes-
Includes an important fix for:
https://bugzilla.gnome.org/show_bug.cgi?id=760938
The fix is not a simple backport to 1.7.1, so just update to latest
version from the current git master branch.
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_git.bb
v2 changes:
- Update comments to clarify why compiler warnings only need to be
fixed in git recipes.
- Move gstreamer1.0 fix into gstreamer1.0.inc (ie also apply to the
1.6.3 recipe).
- Move the gstreamer1.0-plugins-base freetype dependency into the
1.6.3 recipe.
Andre McCurdy (5):
musl libc generates warnings if is included directly.
The warnings only cause problems for the git versions (-Werror is
turned off for GStreamer stable releases).
Signed-off-by: Andre McCurdy
---
.../avoid-including-sys-poll.h-directly.patch | 44 ++
.../gstreamer/gstr
On Fri, Feb 5, 2016 at 1:04 PM, Burton, Ross wrote:
> Hi,
>
> On 5 February 2016 at 20:55, Nicolas Dechesne
> wrote:
>>
>> > Agreed - some may not want openssl at all and being able to switch it
>> > for
>> > another alternative would be useful.
>>
>> sure. but, then I have some questions..
>>
>>
Hi,
On 5 February 2016 at 20:55, Nicolas Dechesne
wrote:
> > Agreed - some may not want openssl at all and being able to switch it for
> > another alternative would be useful.
>
> sure. but, then I have some questions..
>
> 1. which one we default to? openssl?
>
> 2. which one we support, from c
gnome-mime-data is part of the GNOME 2 desktop, and the only dependency on it is
gnome-vfs which is in meta-gnome where this recipe should live.
Signed-off-by: Ross Burton
---
.../gnome/gnome-mime-data/pkgconfig.patch | 14 --
meta/recipes-gnome/gnome/gnome-mime-data_2.18
On Fri, Feb 5, 2016 at 9:46 PM, Burton, Ross wrote:
> On 5 February 2016 at 20:44, Khem Raj wrote:
>>
>> its added new to this version. May be packageconfig is better place
>> for --with-sha1 stuff
>
>
> Agreed - some may not want openssl at all and being able to switch it for
> another alternati
This recipe is very old, unmaintained, not used at all in OE-Core, and not
useful in a world that has moved to GTK+ 3 (even if Sato is slow at catching
up).
Signed-off-by: Ross Burton
---
meta-yocto/conf/distro/include/maintainers.inc | 1 -
meta/conf/distro/include/distro_alias.inc
On 5 February 2016 at 20:44, Khem Raj wrote:
> its added new to this version. May be packageconfig is better place
> for --with-sha1 stuff
>
Agreed - some may not want openssl at all and being able to switch it for
another alternative would be useful.
Ross
--
__
On Fri, Feb 5, 2016 at 12:40 PM, Nicolas Dechesne
wrote:
> * update SRC_URI and checksum.
> * use libcrypto for sha1 functions. In upstream commit a24bdce4, support for
> SHA-1 was copied from xserver repo, so let's use the same default for
> --with-sha1 option that we use in xserver recipe in
* update SRC_URI and checksum.
* use libcrypto for sha1 functions. In upstream commit a24bdce4, support for
SHA-1 was copied from xserver repo, so let's use the same default for
--with-sha1 option that we use in xserver recipe in OE core.
Signed-off-by: Nicolas Dechesne
---
meta/recipes-grap
On Fri, Feb 5, 2016 at 6:16 PM, Nicolas Dechesne
wrote:
> * update SRC_URI and checksum.
> * use libcrypto for sha1 functions. In upstream commit a24bdce4, support for
> SHA-1 was copied from xserver repo, so let's use the same default for
> --with-sha1 option that we use in xserver recipe in
Andre McCurdy (4):
gmp: move SRC_URI out of gmp.inc + minor reformatting
gmp: move BBCLASSEXTEND = "native nativesdk" from gmp.inc into 6.1.0 recipe
gmp.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5
gmp_4.2.1: fix build for MIPS
.../avoid-h-asm-constraint-for-MIPS.patch
The base SRC_URI in gmp.inc was wrong for gmp 4.2.1 and was not being
used by gmp 6.1.0. Remove it and make each recipe responsible for
defining its own SRC_URI.
Signed-off-by: Andre McCurdy
---
meta/recipes-support/gmp/gmp.inc | 11 ---
meta/recipes-support/gmp/gmp_4.2.1.bb | 7 ++
The original over-ride dates back to 2008:
http://git.openembedded.org/openembedded-core/commit/?id=b3dddcdde5d10f382f71413aad67f7ef2e2420a2
There are no obvious issues seen now when building either of the
current gmp recipes (4.2.1 or 6.1.0) in thumb2 for Cortex A15.
Signed-off-by: Andre McC
The h asm constrain (to extract the high part of a multiplication
result) has not been recognised since gcc 4.4:
https://gcc.gnu.org/gcc-4.4/changes.html
Drop the MIPS umul_ppmm() implementations which rely on "=h" and fall
back to the older implementations (which use explicit mfhi and mflo
ins
It's unlikely that native builds of gmp 4.2.1 (ie the last LGPLv2
version) would ever be required (and given that recent versions of gcc
require gmp >= 4.3.2, native builds of gmp 4.2.1 are unlikely to work
very well). Restrict native and nativesdk builds to gmp 6.1.0 only.
https://gcc.gnu.org/i
On Fri, Feb 5, 2016 at 6:55 AM, Martin Jansa wrote:
> On Thu, Feb 04, 2016 at 03:04:18PM -0800, Andre McCurdy wrote:
>> The dependency on freetype was dropped shortly after the 1.7.1 release
>>
>>
>> http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=183610c035dd6955c9b3540b940ae
On Fri, Feb 5, 2016 at 7:55 AM, Burton, Ross wrote:
>
> On 4 February 2016 at 23:04, Andre McCurdy wrote:
>>
>> musl libc generates warnings if is included directly.
>
> Are these not required for the versioned recipes?
Official releases of GStreamer don't enable -Werror, so the warnings
are on
On Fri, Feb 5, 2016 at 10:31 AM, Richard Purdie
wrote:
> On Fri, 2016-02-05 at 10:22 -0800, Khem Raj wrote:
>> On Fri, Feb 5, 2016 at 9:32 AM, Mike Crowe wrote:
>> > On Tue, 2016-02-02 at 14:49 +, Mike Crowe wrote:
>> > On Tue, 2016-02-02 at 21:04 +, Mike Crowe wrote:
>> > > > I've compil
Please send whatever you currently have, so I can test it in my world build
with more layers.
I've already included bitbake.conf change and e.g. pigz-native you listed
here is already failing so I doubt the build with test any reasonable
number of recipes if I let it run like this.
On Fri, Feb 5,
On Fri, 2016-02-05 at 10:22 -0800, Khem Raj wrote:
> On Fri, Feb 5, 2016 at 9:32 AM, Mike Crowe wrote:
> > On Tue, 2016-02-02 at 14:49 +, Mike Crowe wrote:
> > On Tue, 2016-02-02 at 21:04 +, Mike Crowe wrote:
> > > > I've compile-tested qemux86 and qemuarm for core-image-sato.
> > > > qemu
On Fri, Feb 5, 2016 at 9:32 AM, Mike Crowe wrote:
> On Tue, 2016-02-02 at 14:49 +, Mike Crowe wrote:
>> > > > [snip] Set EXTRA_OEMAKE = "" in bitbake.conf
>
> On Tuesday 02 February 2016 at 16:01:14 +, Richard Purdie wrote:
>> > > Which architectures did you test? Often, x86 is a bad choic
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/pigz/pigz.inc | 2 ++
1 file changed, 2 insert
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-gnome/gtk-theme-torturer/gtk-theme-torturer_git.bb | 2
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-support/ptest-runner/ptest-runner_2.0.bb | 2 ++
1 file
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-bsp/libacpi/libacpi_0.2.bb | 2 +-
1 file changed, 1 in
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/iputils/iputils_s20151218.bb | 2 ++
1 file ch
The openssl recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-bsp/pciutils/pciutils_3.4.1.bb | 2 +-
1 file ch
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/unzip/unzip_6.0.bb | 2 +-
1 file changed, 1 i
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-devtools/dmidecode/dmidecode_3.0.bb | 2 ++
1 file chan
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/ed/ed_1.9.bb | 2 ++
1 file changed, 2 inserti
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/sysklogd/sysklogd.inc | 2 ++
1 file changed,
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-devtools/fdisk/gptfdisk_1.0.1.bb | 2 ++
1 file changed
This series (sent only to openembedded-core) fixes various recipes
that rely on the current default value of
EXTRA_OEMAKE = "-e MAKEFLAGS=" to explicitly set that value in the
hope that bitbake.conf can set EXTRA_OEMAKE = "" in the future.
With these patches applied and bitbake.conf setting EXTRA_
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-extended/stat/stat_3.3.bb | 2 ++
1 file changed, 2 ins
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-bsp/apmd/apmd_3.2.2-15.bb | 2 ++
1 file changed, 2 ins
From: Mike Crowe
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-devtools/perl/perl-native_5.22.1.bb
The openssl recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta/recipes-connectivity/openssl/openssl.inc | 1 +
1 file c
When using the FSTYPE multiubi, make sure that each image build
has a unique config file. Without this there is a race condition
when building multiple images in a single bitbake command which
results in errors similar to:
ERROR: Error: The image creation script
'blah/tmp/work/blah/core-i
On Tue, 2016-02-02 at 14:49 +, Mike Crowe wrote:
> > > > [snip] Set EXTRA_OEMAKE = "" in bitbake.conf
On Tuesday 02 February 2016 at 16:01:14 +, Richard Purdie wrote:
> > > Which architectures did you test? Often, x86 is a bad choice here and
> > > we'd need something cross (arm/mips/ppc)
* update SRC_URI and checksum.
* use libcrypto for sha1 functions. In upstream commit a24bdce4, support for
SHA-1 was copied from xserver repo, so let's use the same default for
--with-sha1 option that we use in xserver recipe in OE core.
Signed-off-by: Nicolas Dechesne
---
meta/recipes-grap
From: Armin Kuster
CVE-2016-0755 curl: NTLM credentials not-checked for proxy connection re-use
Signed-off-by: Armin Kuster
---
meta/recipes-support/curl/curl/CVE-2016-0755.patch | 138 +
meta/recipes-support/curl/curl_7.44.0.bb | 3 +-
2 files changed, 140 inse
From: Armin Kuster
Signed-off-by: Armin Kuster
---
.../nettle/nettle-3.1.1/CVE-2015-8804.patch| 281 +
meta/recipes-support/nettle/nettle_3.1.1.bb| 1 +
2 files changed, 282 insertions(+)
create mode 100644 meta/recipes-support/nettle/nettle-3.1.1/CVE-2015
From: Armin Kuster
please consider these changes for the next next jethro-next
The following changes since commit 9cfb259d1bfe2d66801e0f15e7bb36a162f757ad:
socat: Security fix CVE-2016-2217 (2016-02-05 06:32:56 -0800)
are available in the git repository at:
git://git.yoctoproject.org/poky
From: Armin Kuster
Signed-off-by: Armin Kuster
---
.../nettle/nettle-3.1.1/CVE-2015-8803_8805.patch | 71 ++
meta/recipes-support/nettle/nettle_3.1.1.bb| 4 ++
2 files changed, 75 insertions(+)
create mode 100644
meta/recipes-support/nettle/nettle-3.1.1/CVE-2015
From: Armin Kuster
CVE-2016-0754 curl: remote file name path traversal in curl tool for Windows
Signed-off-by: Armin Kuster
---
meta/recipes-support/curl/curl/CVE-2016-0754.patch | 417 +
meta/recipes-support/curl/curl_7.44.0.bb | 3 +-
2 files changed, 419 inse
From: Christopher Larson
If this is set when nativesdk-python is not installed, it will break the host
python, so it's better to handle this in python.
Signed-off-by: Christopher Larson
---
meta/classes/toolchain-scripts.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/t
From: Christopher Larson
This ensures that the nativesdk python functions correctly without needing to
set PYTHONHOME in the sdk environment setup script.
Signed-off-by: Christopher Larson
---
meta/recipes-devtools/python/python_2.7.11.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Current Dev Position: YP 2.1 M3
Next Deadline: YP 2.1 M2 Target release date is February 12, 2016
SWAT team rotation: Alejandro Franco -> Juro
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* YP 2.1 M2-rc1 QA report has been published. The number of High
On 4 February 2016 at 23:04, Andre McCurdy wrote:
> musl libc generates warnings if is included directly.
>
Are these not required for the versioned recipes?
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://
On 5 February 2016 at 12:02, Andreas Müller
wrote:
> Will give the backport a test and hope I'll get i18n back for GTK (and
> most likely others).
>
FWIW I've tested and queued this for oe-core master too.
Ross
--
___
Openembedded-core mailing list
O
From: Armin Kuster
CVE-2015-8327 cups-filters: foomatic-rip did not consider the back tick as an
illegal shell escape character
this time with the recipe changes.
Signed-off-by: Armin Kuster
---
.../foomatic-filters-4.0.17/CVE-2015-8327.patch| 23 ++
.../foomatic/foom
From: Armin Kuster
libpng: Buffer overflow vulnerabilities in png_get_PLTE/png_set_PLTE functions
this patch fixes an incomplete patch in CVE-2015-8126
Signed-off-by: Armin Kuster
---
.../libpng/libpng-1.6.17/CVE-2015-8472.patch | 29 ++
meta/recipes-multimedia/libpn
From: Armin Kuster
this address both
Socat security advisory 7 and MSVR-1499: "Bad DH p parameter in OpenSSL"
and Socat security advisory 8: "Stack overflow in arguments parser
[Yocto # 9024]
Signed-off-by: Armin Kuster
---
.../socat/socat/CVE-2016-2217.patch| 372
From: Armin Kuster
libpng: Buffer overflow vulnerabilities in png_get_PLTE/png_set_PLTE functions
Signed-off-by: Armin Kuster
---
.../libpng/libpng-1.6.17/CVE-2015-8126_1.patch | 91 ++
.../libpng/libpng-1.6.17/CVE-2015-8126_2.patch | 134 +
.../libpng/
From: Armin Kuster
please consider these changes for Jethro next.
foomatic-filters: Security fixes CVE-2015-8327 is version 2 as the recipe was
not updated.
The following changes since commit ae1df825062fc841130622b8e154c6ed0f83f375:
foomatic-filters: Security fix CVE-2015-8560 (2016-02-04
On Thu, Feb 04, 2016 at 03:04:18PM -0800, Andre McCurdy wrote:
> The dependency on freetype was dropped shortly after the 1.7.1 release
>
>
> http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=183610c035dd6955c9b3540b940aec50474af031
>
> Signed-off-by: Andre McCurdy
> ---
> me
On 5 February 2016 at 13:32, Joshua G Lock
wrote:
> We could do with a convention for documenting this kind of trap (where
> a PACKAGECONFIG in foo requires one in bar).
>
> Maybe you could a comment here in this case?
>
Yeah fair point. Comment added in my branch.
Ross
--
___
On 5 February 2016 at 14:00, Markus Lehtonen <
markus.lehto...@linux.intel.com> wrote:
> +msgs.append("Please install python-pexpect that is needed by
> lcocal gpg signing.")
>
Isn't this only needed if signing RPMs? Hopefully in the future this class
will be used for more than RPM s
On 5 February 2016 at 10:25, Jens Rehsack wrote:
> Add patch from commit 96b1b5c127e9e0e637aaf7948cf3330a94a5cd57 to
> cross-localedef-native
> to avoid broken images built with ENABLE_BINARY_LOCALE_GENERATION set to 1:
>
This impacts master too, so I've merged this into ross/mut and endorse it
On 5 February 2016 at 10:26, Jens Rehsack wrote:
> +commit 3007f797a1a596e954f44879a5a7267966186ba4
> +Author: Mike Frysinger
> +Date: Fri Aug 28 17:08:49 2015 -0400
> +
> +getmntent: fix memory corruption w/blank lines [BZ #18887]
> +
> +The fix for BZ #17273 introduced a single byte
The configuration needed for different signing backends may vary
(although we currently support only one backend). Thus, do the actual
sanity checking of the configuration there.
Signed-off-by: Markus Lehtonen
---
meta/classes/sign_package_feed.bbclass | 14 ++
meta/classes/sign_rpm.
This way, one does not get a ton of identical error messages. But, only
one error message before all the recipes are parsed.
Signed-off-by: Markus Lehtonen
---
meta/classes/sign_package_feed.bbclass | 26 --
meta/classes/sign_rpm.bbclass | 26
Signed-off-by: Markus Lehtonen
---
meta/lib/oe/gpg_sign.py | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oe/gpg_sign.py b/meta/lib/oe/gpg_sign.py
index 8832ea9..ea35564 100644
--- a/meta/lib/oe/gpg_sign.py
+++ b/meta/lib/oe/gpg_sign.py
@@ -17,13 +17,17 @@
This patchset contains that should make sanity checking of rpm and package feed
signing more sane.
The following changes since commit 11a6227759515da433230eb44eca1a4cb2ac3b14:
e2fsprogs: Ensure we use the right mke2fs.conf when restoring from sstate
(2016-02-05 11:16:20 +)
are available
qemux86-64 looks a lot worse, because it's using slightly newer oe-core
revision than qemuarm and qemux86 builds did and not only kernel is failing
there, there is new/fixed QA check reporting many issues in package_qa.
== Tested changes (not included in master yet) - bitbake ==
c1ac873 world-imag
Take `pwd` to be . The %s path is relative to it. The value
of %s is "output_folder/build". The current code works as follows:
Changing directory to %s and finding the sources (after cd'ing) to cpio
with output redirection to %s/initrd.cpio triggers the following error
"Error: exec_cmd: cd output
On Fri, 2016-02-05 at 11:47 +, Ross Burton wrote:
> Instead of using the internal copy of libpcre, use one that we
> build. Note that
> this requires libpcre enables Unicode properties.
We could do with a convention for documenting this kind of trap (where
a PACKAGECONFIG in foo requires one
On Fri, Feb 5, 2016 at 1:02 PM, Andreas Müller
wrote:
> On Wed, Feb 3, 2016 at 3:50 PM, Richard Purdie
> wrote:
>> On Wed, 2016-02-03 at 12:49 +0100, Andreas Müller wrote:
>>> Hi,
>>>
>>> while testing libreoffice language packets I found that language
>>> settings for GTK based apps are broken.
On Wed, Feb 3, 2016 at 3:50 PM, Richard Purdie
wrote:
> On Wed, 2016-02-03 at 12:49 +0100, Andreas Müller wrote:
>> Hi,
>>
>> while testing libreoffice language packets I found that language
>> settings for GTK based apps are broken. Interestingly QT based
>> applications (tested with qtcreator an
Instead of using the internal copy of libpcre, use one that we build. Note that
this requires libpcre enables Unicode properties.
Signed-off-by: Ross Burton
---
meta/recipes-core/glib-2.0/glib.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/glib-2.0/glib.inc
b/meta
Python 3 resurrected the default to optimised patch, on the rationale that
embedded systems want all the performance they can get. Unfortunately the only
impact Python "optimisation" has is to remove all asserts which can be actively
harmful, so remove this patch.
Signed-off-by: Ross Burton
---
Enable Unicode properties by default, as they're useful and for example GLib
needs them. As there is an impact to code size add this as a PACKAGECONFIG so
tightly constrained environments can save space by potentially disabling them.
Also change --enable-utf8 to --enable-utf, as the former is a c
If we don't do this, we can use an mke2fs.conf from a different path which
may contain incompatible flags and lead to obtuse build failures such as:
Invalid filesystem option set:
has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
To fix this, wrap the mke2fs binary a
This if branch is causing the following error during do_rootfs:
"Exception: UnboundLocalError: local variable 'cfg_file' referenced
before assignment". This happends because the cfg_file variable is
defined at a deeper nesting level (just above the if branch).
Signed-off-by: Ioan-Adrian Ratiu
---
When building nativesdk recipes, we noticed paths going into .pc files
which should have been suppressed since these were standard library
search paths. pkgconfig-native sets these variables to sane values
for native recipes, we need it set to values for our specific library
paths in the nativesdk
Since default fstab contains empty lines, this might be a reasonable patch
long running services using getmntent.
This patch is backported from:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commit;h=3007f797a1a596e954f44879a5a7267966186ba4
Signed-off-by: Jens Rehsack
---
...ntent-fix-mem
Add patch from commit 96b1b5c127e9e0e637aaf7948cf3330a94a5cd57 to
cross-localedef-native
to avoid broken images built with ENABLE_BINARY_LOCALE_GENERATION set to 1:
$ sh -c "export LANG=de_DE; ls -la"
sh: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof
(_nl_value_type
Please backport the following from oe-core/master to jethro:
55a8df2056024acf714f47c85267c1eba8b7b6be
perl: Upgrade to 5.22.1
According to http://search.cpan.org/dist/perl-5.22.1/pod/perldelta.pod no
incompatible changes but a lot of serious bugs fixed.
Cheers
--
Jens Rehsack - rehs...@gmail.co
According to error messages from guruplug
[ 35.826441] btmrvl_sdio mmc0:0001:2: Direct firmware load for
mrvl/sd8688_helper.bin failed with error -2
[ 35.903291] Bluetooth: request_firmware(helper) failed, error code = -2
[ 35.909942] Bluetooth: Failed to download helper!
[ 36.052820] Blu
On 04/02/2016 12:21, "openembedded-core-boun...@lists.openembedded.org on
behalf of Richard Purdie"
wrote:
>On Thu, 2016-02-04 at 10:47 +, Elliot Smith wrote:
>> From: Belen Barros Pena
>>
>> It looks like the master branch will no longer build with the Fido
>> release, so remove all refe
88 matches
Mail list logo
