On Fri, 2016-06-17 at 14:42 -0700, Christopher Larson wrote:
> On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
> stephen.k.jol...@intel.com> wrote:
> > ·There is a multilib issue related to the layout of the
> > host libraries leaking into python’s build process which we’re
> > struggl
On Fri, Jun 17, 2016 at 2:42 PM, Christopher Larson
wrote:
> On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
> stephen.k.jol...@intel.com> wrote:
>
>> ·There is a multilib issue related to the layout of the host
>> libraries leaking into python’s build process which we’re struggling
On Fri, Jun 17, 2016 at 5:41 AM, Dmitriy Falko
wrote:
> Binutils as(sembler) trying to referency _obstack_free when building
> it for ARM uclibc(not cross compile version).
>
> Enables it(just alias to uclibc obstack_free) to fix build of binutils.
this is ok
>
> [YOCTO #9781]
>
> Signed-off-by:
On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
stephen.k.jol...@intel.com> wrote:
> ·There is a multilib issue related to the layout of the host
> libraries leaking into python’s build process which we’re struggling to
> debug
Could I get some details on this? I've seen something l
On Thu, Jun 16, 2016 at 2:04 AM, Patrick Ohly wrote:
> On Tue, 2016-06-14 at 16:18 +0100, Ross Burton wrote:
>> As rm_work is just cleanup it shouldn't starve more important tasks such as
>> do_compile of I/O, so use BB_TASK_IONICE_LEVEL to run the task in the idle
>> scheduler class.
>
> Whether
On 06/17/2016 05:56 AM, Andre McCurdy wrote:
On Thu, Jun 16, 2016 at 3:59 AM, Alexander Kanavin
wrote:
These recipes no longer seem to need full exclusion from security hardening.
Did you also confirm that for gcc 4.9 and 5.3?
I just did; they build with both.
Alex
--
__
Signed-off-by: Jussi Kukkonen
---
meta/recipes-devtools/qemu/qemu.inc| 2 +-
.../qemu/0001-configure-support-vte-2.91.patch | 79 ++
meta/recipes-devtools/qemu/qemu_2.6.0.bb | 1 +
3 files changed, 81 insertions(+), 1 deletion(-)
create mode 10
Always run the Makefile rule that modifies gdkx.h (for opengl
disabling), but only do the modification if the file is not
correct already.
Signed-off-by: Jussi Kukkonen
---
.../0001-Add-disable-opengl-configure-option.patch| 19 ++-
1 file changed, 10 insertions(+), 9 deletio
Qemu has a non-default PACKAGECONFIG "gtk+", the patch updates that
to work with gtk+3. Also included is a fix for the first bug I
already found in the gtk+3 "--disable-opengl" patch.
Have good weekend,
Jussi
The following changes since commit 7b9e1f5ad8a427356f2ec516b1718138a7d3c64e:
cmake.
On June 17, 2016 20:43:06 Jussi Kukkonen wrote:
> On 17 June 2016 at 16:33, Mark Asselstine
>
> wrote:
> > On June 16, 2016 18:10:09 Andre McCurdy wrote:
> > > On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross
> >
> > wrote:
> > > > On 16 June 2016 at 21:49, Mark Asselstine <
> >
> > mark.asselst.
On Fri, Jun 17, 2016 at 11:24 AM, Alexander Kanavin
wrote:
> On 06/17/2016 07:23 AM, Khem Raj wrote:
>>
>> mpg123 plugin moved from bad collection to ugly in 1.8
>> since mpg123 has commercial licence implications its best
>> to keep it with a knob.
>> +
>> +PACKAGECONFIG[mpg123] = "--enable-mpg12
On 17 June 2016 at 04:36, Chen Qi wrote:
> +DEPENDS = "libxslt-native libxslt-native xmlto-native
> docbook-xml-dtd4-native docbook-xsl-stylesheets-native intltool"
>
Can we not disable documentation?
> +SYSTEMD_SERVICE_${PN} = "systemd-bootchart.service"
> +SYSTEMD_AUTO_ENABLE_${PN} = "disabl
On 06/17/2016 06:36 AM, Chen Qi wrote:
ptest is disabled as the related codes are changed a lot, and the
related patches are removed.
Excuse me, but you should not remove ptest support altogether just
because upstream has rearranged it in the new version. Please figure it
out, rebase the patc
Causes ar to use zero for timestamps and uids/gids by default when
creating static archives, which helps make builds deterministic.
https://bugzilla.redhat.com/show_bug.cgi?id=1124342
https://wiki.debian.org/ReproducibleBuilds/TimestampsInStaticLibraries
Signed-off-by: Andre McCurdy
---
met
On 06/17/2016 07:23 AM, Khem Raj wrote:
mpg123 plugin moved from bad collection to ugly in 1.8
since mpg123 has commercial licence implications its best
to keep it with a knob.
+
+PACKAGECONFIG[mpg123] = "--enable-mpg123,--disable-mpg123,mpg123"
This patch is not necessary as gstreamer1.0-plug
On 06/17/2016 05:39 AM, Andre McCurdy wrote:
Typically these warnings come from assembler and can't be fixed via
CFLAGS. If this one _can_ be fixed via CFLAGS then it suggests a bug
in the Epiphany build somewhere (e.g. reusing an object file intended
for a static lib in an .so). Maybe it's bette
On 06/17/2016 05:38 AM, Andre McCurdy wrote:
SECURITY_CFLAGS ?= "-fstack-protector-strong -pie -fpie ${lcl_maybe_fortify}
${SECURITY_STRINGFORMAT}"
-SECURITY_NO_PIE_CFLAGS ?= "-fstack-protector-strong ${lcl_maybe_fortify}
${SECURITY_STRINGFORMAT}"
+SECURITY_NO_PIE_CFLAGS ?= "-fPIC -fstack-prot
On 17 June 2016 at 16:33, Mark Asselstine
wrote:
> On June 16, 2016 18:10:09 Andre McCurdy wrote:
> > On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross
> wrote:
> > > On 16 June 2016 at 21:49, Mark Asselstine <
> mark.asselst...@windriver.com>
> > >
> > > wrote:
> > >> While waiting to hear back abo
On Fri, Jun 17, 2016 at 8:47 AM, Ed Bartosh
wrote:
> Setting rpath causes clash of host and sdk libc and makes
> pseudo to crash with relocation error: libpthread.so.0:
> symbol __libc_vfork, version GLIBC_PRIVATE not defined
> in file libc.so.6 with link time reference
>
> Removing rpath
On Fri, 2016-06-17 at 17:13 +0100, Richard Purdie wrote:
> On Fri, 2016-06-17 at 17:19 +0300, Maxin B. John wrote:
> > Update depexp.py to support gtk+3
> >
> > Signed-off-by: Maxin B. John
> > ---
> > bitbake/lib/bb/ui/depexp.py | 127
> > --
> > --
> >
On Fri, 2016-06-17 at 17:19 +0300, Maxin B. John wrote:
> Update depexp.py to support gtk+3
>
> Signed-off-by: Maxin B. John
> ---
> bitbake/lib/bb/ui/depexp.py | 127 --
> --
> 1 file changed, 58 insertions(+), 69 deletions(-)
>
> diff --git a/bitbake/li
On Fri, 2016-06-17 at 08:52 -0400, Andrew Bradford wrote:
> On 05/25 15:46, Andrew Bradford wrote:
> I noticed that this patch has not been applied to oe-core, but it is
> a
> dependency for the bitbake perforce fetcher change to support srcrev
> which has been applied to bitbake's master branch [1
Setting rpath causes clash of host and sdk libc and makes
pseudo to crash with relocation error: libpthread.so.0:
symbol __libc_vfork, version GLIBC_PRIVATE not defined
in file libc.so.6 with link time reference
Removing rpath fixes this as it makes pseudo to use only host
pthread and libc
Current Dev Position: YP 2.2 M1 [still not in QA]
Next Deadline: YP 2.2 M2 cut off would be: 7/18/16
SWAT team rotation: Maxin -> Joshua
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
*GTK+3 and Sato rework have merged
*A rework of taskd
Setting rpath causes clash of host and sdk libc and makes
pseudo to crash with relocation error: libpthread.so.0:
symbol __libc_vfork, version GLIBC_PRIVATE not defined
in file libc.so.6 with link time reference
Removing rpath fixes this as it makes pseudo to use only host
pthread and libc
The CMake recipes contain a mismatch between the environmental variable
which defines where the Modules are installed and the location where they
actually are. This patch fixes the environmental variable to point to the
proper folder defined according to the cmake version.
Signed-off-by: Jose Pard
Previously when USERADD_ERROR_DYNAMIC was set to "1", an exception was
raised if no numeric UID/GID could be determined for a user/group. Now
it is possible to set it to either "error", which results in the old
behavior, or "warn" in which case a warning is issued instead.
For backwards compatibil
A regression was introduced with commit 3149319a whereby setting
USERADD_ERROR_DYNAMIC no longer resulted in an error for users and
groups that were missing numeric UIDs and GIDs but were not mentioned
at all in any passwd or groups file.
[YOCTO #9777]
Signed-off-by: Peter Kjellerstedt
---
meta
Document that USERADD_ERROR_DYNAMIC can now take "error" or "warn" as
values, to either cause an exception or a warning in case no numeric
UID/GID can be determined for a user or group.
Signed-off-by: Peter Kjellerstedt
---
documentation/ref-manual/ref-variables.xml | 16 +---
1 file
Suggested-by: Mark Hatle
Signed-off-by: Peter Kjellerstedt
---
documentation/ref-manual/ref-variables.xml | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index 0
Signed-off-by: Peter Kjellerstedt
---
meta/conf/documentation.conf | 4
1 file changed, 4 insertions(+)
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index c0025f5..010585a 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -452,8 +452
The main change here is to fix the regression reported in
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9777 which resulted
in setting USERADD_ERROR_DYNAMIC having no effect if the user or group
was not listed at all in a passwd or groups file.
In the ticket discussion there was also a suggest
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Mark Hatle
> Sent: den 17 juni 2016 15:55
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/4] documentatio
> On Jun 17, 2016, at 2:32 AM, Enrico Joerns wrote:
>
> Hi,
>
> On 05/19/2016 10:02 AM, Richard Purdie wrote:
>> On Thu, 2016-05-19 at 08:36 +0100, Richard Purdie wrote:
>>> On Tue, 2016-05-17 at 21:40 -0700, Khem Raj wrote:
Some system users which are needed by systemd components were
>>>
Update depexp.py to support gtk+3
Signed-off-by: Maxin B. John
---
bitbake/lib/bb/ui/depexp.py | 127
1 file changed, 58 insertions(+), 69 deletions(-)
diff --git a/bitbake/lib/bb/ui/depexp.py b/bitbake/lib/bb/ui/depexp.py
index 240aafc..8f603dd 1006
Signed-off-by: Peter Kjellerstedt
---
meta/conf/documentation.conf | 4
1 file changed, 4 insertions(+)
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index c0025f5..38639d5 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -452,8 +452
On 6/17/16 8:41 AM, Peter Kjellerstedt wrote:
> Signed-off-by: Peter Kjellerstedt
> ---
> meta/conf/documentation.conf | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
> index c0025f5..38639d5 100644
> --- a/meta/conf/docume
A regression was introduced with commit 3149319a whereby setting
USERADD_ERROR_DYNAMIC no longer resulted in an error for users and
groups that were missing numeric UIDs and GIDs but were not mentioned
at all in any passwd or groups file.
[YOCTO #9777]
Signed-off-by: Peter Kjellerstedt
---
meta
The main change here is to fix the regression reported in
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9777 which resulted
in setting USERADD_ERROR_DYNAMIC having no effect if the user or group
was not listed at all in a passwd or groups file.
In the ticket discussion there was also a suggest
Document that USERADD_ERROR_DYNAMIC can now take "error" or "warn" as
values, to either cause an exception or a warning in case no numeric
UID/GID can be determined for a user or group.
Signed-off-by: Peter Kjellerstedt
---
documentation/ref-manual/ref-variables.xml | 19 +++
1 f
Previously when USERADD_ERROR_DYNAMIC was set to "1", an exception was
raised if no numeric UID/GID could be determined for a user/group. Now
it is possible to set it to either "error", which results in the old
behavior, or "warn" in which case a warning is issued instead.
For backwards compatibil
On June 16, 2016 18:10:09 Andre McCurdy wrote:
> On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross wrote:
> > On 16 June 2016 at 21:49, Mark Asselstine
> >
> > wrote:
> >> While waiting to hear back about my inquiry I did take some
> >> time to put together this patch that allows things that
> >> re
still tooling around the initramfs images, and noticed:
$ grep -rw INITRD_IMAGE *
meta/recipes-extended/images/core-image-testmaster.bb:INITRD_IMAGE =
"core-image-testmaster-initramfs"
$
however:
$ grep -r INITRD_IMAGE *
meta/recipes-extended/images/core-image-testmaster.bb:INITRD_IMAGE =
Hi,
On 05/25 15:46, Andrew Bradford wrote:
> From: Andrew Bradford
>
> Enable the perforce fetcher to call bb.fetch2.get_srcrev() as it can use
> 'SRCREV = "${AUTOREV}"'.
>
> Signed-off-by: Andrew Bradford
> ---
> meta/classes/base.bbclass | 4
> 1 file changed, 4 insertions(+)
>
> diff
Binutils as(sembler) trying to referency _obstack_free when building
it for ARM uclibc(not cross compile version).
Enables it(just alias to uclibc obstack_free) to fix build of binutils.
[YOCTO #9781]
Signed-off-by: Dmitriy Falko
---
meta/recipes-core/uclibc/uclibc-git.inc| 1 +
.
We previously patched configure to stop looking around for a Python to use, and
to use the Python binary and install paths that we specify. Now that we depend
on Python 3 its possible that bitbake is being built on a machine without Python
2 installed, so hardcode the python3 interpreter instead.
Some recipes depend on Python 2 being present (eg glib and ncurses) so until
they've all been migrated to Python 3 we should continue to ship Python 2 in the
self-hosted packagegroup.
Signed-off-by: Ross Burton
---
meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 3 +++
1 file chang
short followup to earlier question -- what would be the ideal
starting point image for my basic installer? i just took a look in
oe-core, and i see something under recipes-extended called
core-image-testmaster-initramfs.bb which looks remarkably like what
i'm after:
DESCRIPTION = "Small image c
(i asked about this on the YP list a while back, but since this is
really a basic OE question, i'll re-ask it here with more detail.)
i want to build an "installer" image for a powerpc system i'm
working with, and i have what i think is a reasonable design, so i'll
describe it and just want t
On 17 June 2016 at 03:58, Christopher Larson wrote:
> gstreamer1.0-plugins-bad's upgrade was delayed due to the pending gtk3
> switch for sato, which has recently happened, so I'd expect that upgrade to
> come at some point in the near future. See
> https://bugzilla.yoctoproject.org/show_bug.cgi?
On 17 June 2016 at 11:02, Dmitriy Falko wrote:
> Signed-off-by: Dmitriy Falko
>
Please add a full explanation to the commit message and patch header to
explain what this patch does and why. The commit message should reference
the bug number [YOCTO #9781], and the patch also needs an Upstream S
Hi Ross,
I already re-send this patch(http://patches.openembedded.org/patch/125115/)
More info about this issue i wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9781
17.06.2016 13:15, Burton, Ross пишет:
Hi Dmitry,
Can you re-send this as a patch against oe-core itself instea
Hi Dmitry,
Can you re-send this as a patch against oe-core itself instead of
(presumably) binutils, explaining why it breaks for you and why this is the
correct fix?
Thanks,
Ross
On 17 June 2016 at 10:33, Dmitriy Falko wrote:
> Signed-off-by: Dmitriy Falko
> ---
> libc/misc/gnu/obstack.c | 4
On 17 June 2016 at 07:37, Jussi Kukkonen wrote:
> > That's certainly a good argument for putting the old vte in meta-oe.
>>
>> The meta-oe layers generally have a higher priority than oe-core, so
>> having an older version in meta-oe and a newer version in oe-core can
>> lead to unexpected result
Signed-off-by: Dmitriy Falko
---
meta/recipes-core/uclibc/uclibc-git.inc| 1 +
...Alias-_obstack_free-to-fix-binutils-build.patch | 31 ++
2 files changed, 32 insertions(+)
create mode 100644
meta/recipes-core/uclibc/uclibc-git/0001-Alias-_obstack_free-to-fix-bi
Signed-off-by: Dmitriy Falko
---
libc/misc/gnu/obstack.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libc/misc/gnu/obstack.c b/libc/misc/gnu/obstack.c
index 38cfd83..2689263 100644
--- a/libc/misc/gnu/obstack.c
+++ b/libc/misc/gnu/obstack.c
@@ -385,11 +385,11 @@ obstac
Hi,
On 05/19/2016 10:02 AM, Richard Purdie wrote:
On Thu, 2016-05-19 at 08:36 +0100, Richard Purdie wrote:
On Tue, 2016-05-17 at 21:40 -0700, Khem Raj wrote:
Some system users which are needed by systemd components were
missing
create these users knobbed with relevant packageconfig
Signed-off
Patch is a bit nasty and not maintainer friendly, but it does
make Gtk+3 compile without libepoxy (which means without OpenGL
dev files).
Signed-off-by: Jussi Kukkonen
---
meta/recipes-gnome/gtk+/gtk+3.inc | 7 +-
.../0001-Add-disable-opengl-configure-option.patch | 965 ++
Objective here is to allow building core-image-sato without OpenGL
even though Gtk+3 depends on it.
I'm not proud of the patch:
* It modifies Gtk API (only GdkX11GLContext is removed but still)
* It's a maintenance problem
* It finds all kinds of nasty corner cases in the Gtk build system
but I'm
59 matches
Mail list logo
