Signed-off-by: Khem Raj
---
...m-Add-Wimplicit-fallthrough-0-in-Makefile.patch | 37 ++
...pecify-enough-length-when-write-to-buffer.patch | 75
...rintf-with-strncpy-at-some-places-to-avoi.patch | 59 ++
Signed-off-by: Khem Raj
---
meta/recipes-support/aspell/aspell/gcc7.patch | 40 ++
meta/recipes-support/aspell/aspell_0.60.6.1.bb | 4 ++-
2 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644
Backport fix for gcc7 warning along the way
Signed-off-by: Khem Raj
---
...-FALLTHRU-comment-to-handle-GCC7-warnings.patch | 74 ++
.../0001-Link-against-libm-when-needed.patch | 53
.../0001-json_tokener-requires-INF-and-NAN.patch
Signed-off-by: Khem Raj
---
.../pax/0001-Add-a-comment-for-fallthrough.patch | 38 ++
meta/recipes-extended/pax/pax_3.4.bb | 9 ++---
2 files changed, 43 insertions(+), 4 deletions(-)
create mode 100644
Also fix build with gcc7 along
Signed-off-by: Khem Raj
---
.../nss/0001-Fix-warnings-found-with-gcc7.patch| 41 ++
.../nss/{nss_3.28.1.bb => nss_3.29.1.bb} | 28 +++
2 files changed, 55 insertions(+), 14 deletions(-)
create mode
Upgrade libepoxy from 1.4.0 to 1.4.1.
Signed-off-by: Huang Qiyu
---
.../libepoxy/{libepoxy_1.4.0.bb => libepoxy_1.4.1.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-graphics/libepoxy/{libepoxy_1.4.0.bb =>
== Series Details ==
Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Revision: 1
URL : https://patchwork.openembedded.org/series/6429/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
Signed-off-by: Andre McCurdy
---
meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch
b/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch
On 2017-04-19 06:10 PM, Trevor Woerner wrote:
> Could you please use
> https://www.timeanddate.com/worldclock/fixedform.html to specify the
> date/time?
>
Never used it before. Handy.
Here's a link to the time:
Are there no toll-free numbers that could be used, or at least more
options for local area codes?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Could you please use
https://www.timeanddate.com/worldclock/fixedform.html to specify the
date/time?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signed-off-by: Andre McCurdy
---
meta/conf/documentation.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index 06527cb..35b9103 100644
--- a/meta/conf/documentation.conf
+++
Signed-off-by: Andre McCurdy
---
meta/conf/distro/include/tclibc-musl.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/tclibc-musl.inc
b/meta/conf/distro/include/tclibc-musl.inc
index 1ddd58e..3d3f6ac 100644
---
The built curl is used during the builds, and any download using an https link
(e.g. from github) requires the certificates, so these must be installed before
curl is available.
This was breaking stb-kodi builds on openViX.
(Actually, absolute links get installed, so you also need to be using a
On Wed, 2017-04-19 at 15:17 -0700, Saul Wold wrote:
> Since BSPs also define package archs that are included in
> PACKAGE_EXTRA_ARCHS
> we should also enure they are accounted for in SSTATE_ARCH.
>
> This helps with the license manifest issue in some cases.
>
> Signed-off-by: Saul Wold
Since BSPs also define package archs that are included in PACKAGE_EXTRA_ARCHS
we should also enure they are accounted for in SSTATE_ARCH.
This helps with the license manifest issue in some cases.
Signed-off-by: Saul Wold
---
meta/classes/sstate.bbclass | 1 +
1 file
All - please note the time zone carefully when planning to attend.
On Wed, Apr 19, 2017 at 1:48 PM, Sean Hudson wrote:
> The board would like to hold a general meeting with all members. Under
> the new by-laws of the OpenEmbedded organization, we can meet
>
Using bitbake variable syntax (i.e., ${FOO}) for shell variables is
bad practice. First of all it is confusing, but more importantly it
can lead to weird problems if someone actually defines a bitbake
variable with the same name as the shell variable.
Also use lower case for local shell
kexec-tools upstream previously integrated the patch into master rev
587778e24c9 but for a bug report it was remove [1][2], after an intensive
testing on OpenSUSE 13.1 64 bits and in poky variants: qemux86 [3],
qemux86-64-x32 [4] and generix86-64 (minnow) [5] it worked.
I think that the upstream
This reverts commit ec1f1c4abe1d40708fefd56f01c58fff38f28960.
Signed-off-by: Aníbal Limón
---
.../kexec/kexec-tools/kexec-x32.patch | 88 ++
1 file changed, 88 insertions(+)
create mode 100644
This reverts commit ec1f1c4abe1d40708fefd56f01c58fff38f28960.
Signed-off-by: Aníbal Limón
---
.../kexec/kexec-tools/kexec-x32.patch | 88 ++
1 file changed, 88 insertions(+)
create mode 100644
kexec-tools upstream previously integrated the patch into master rev
587778e24c9 but for a bug report it was remove [1][2], after an intensive
testing on OpenSUSE 13.1 64 bits and in poky variants: qemux86 [3],
qemux86-64-x32 [4] and generix86-64 (minnow) [5] it worked.
I think that the upstream
The board would like to hold a general meeting with all members. Under
the new by-laws of the OpenEmbedded organization, we can meet
electronically. This will also fulfill the requirement for an annual,
general meeting.
Planned Date/Time:
Wednesday, May 3rd, at 8am US-CDT(UTC-06:00)/3pm
This saves relative paths in the qemuboot.conf file instead of absolute
paths. This is to allow the images and kernels to be relocated and still
have the testimage and runqemu work.
[YOCTO #11375]
Signed-off-by: brian avery
---
meta/classes/qemuboot.bbclass | 7 +++
We want to be able to save relative paths so that we can relocate the
deploy dir images and kernels, yet still have qemu and testimage work
correctly. This extends export2json with 2 named arguments so a
search/replace operation can be done to remove the leading path.
[YOCTO #11375]
We pass the TOPDIR to do a search/replace in export2json so that we save
relative paths in the testdata.json file rather than absolute paths.
This is to allow the images and kernels to be relocated yet still allow
testimage to work.
[YOCTO #11375]
Signed-off-by: brian avery
This patch set changes the behaviour to save relative paths instead of absolute
paths into the qemuboot.conf and the testdata.json files.
A sed test verified that this seems to work without complication. If certain
variables, need to be excluded from this relative path fix, that can be
done with
== Series Details ==
Series: Add files via upload
Revision: 1
URL : https://patchwork.openembedded.org/series/6421/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
From: original-birdman
The built curl is used during the builds, and any download using an https link
(e.g. from github) requires the certificates, so these must be installed before
curl is available.
(Actually, absolute links get installed, so you also need to be
libnsl needs this API
Signed-off-by: Khem Raj
---
- v1 -> v2
- Document the change in the patch a bit more with upstream references
.../libtirpc/export_key_secretkey_is_set.patch | 24 ++
meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb | 1 +
2
Create an option to wic doesn't change fstab file, the final
fstab file will be same that in rootfs and wic doesn't update
file, e.g adding a new mount point.
Users can control the fstab file content in base-files recipe.
This is useful if you want to only create an partition but not
add fstab
On 04/18/2017 12:57 PM, Davis, Michael wrote:
From: Choong YinThong
fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com.
Update the ${PN} to ${BPN} in order to pass the autobuilder
mulitlib enable configuration.
On Wed, Apr 19, 2017 at 9:36 AM, Burton, Ross wrote:
>
> On 19 April 2017 at 17:25, Khem Raj wrote:
>>
>> key_secret_is_set is a typo in libtirpc map file which is fixed here.
>
>
> Can you resubmit with that in the commit log. Are you pushing these
>
On Wed, Apr 19, 2017 at 8:06 AM, André Draszik wrote:
> On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote:
>> Replace a local patch for format warning with the one
>> that got committed upstream
>
> This commit message is confusing, as the two patches are unrelated and they
> are
On 19 April 2017 at 17:25, Khem Raj wrote:
> key_secret_is_set is a typo in libtirpc map file which is fixed here.
>
Can you resubmit with that in the commit log. Are you pushing these
upstream?
Ross
--
___
Openembedded-core
On Wed, Apr 19, 2017 at 1:57 AM, André Draszik wrote:
> On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote:
>> Use memset() API instead of __bzero()
>> Drop the patch removing des_* functions for musl
>>
>> Signed-off-by: Khem Raj
>> ---
>>
On Wed, Apr 19, 2017 at 1:52 AM, Burton, Ross wrote:
>
> On 19 April 2017 at 02:58, Khem Raj wrote:
>>
>> +-key_secret_is_set;
>> ++key_secretkey_is_set;
>
>
> This removes key_secret_is_set, was this a typo upstream or a mistake in the
> patch?
On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote:
> Replace a local patch for format warning with the one
> that got committed upstream
This commit message is confusing, as the two patches are unrelated and they
are addressing different issues.
You are:
- removing a patch that fixed
The architecture list used by dnf/libsolv was in the wrong order.
As a result, the images were built with wrong and unpredictable
packages.
$ MACHINE=intel-corei7-64 bitbake core-image-sato
$ MACHINE=qemux86-64 bitbake core-image-sato
$ MACHINE=intel-corei7-64 bitbake -ccleansstate
arm: mark __startcontext as .cantunwind, GNU
CVE: CVE-2016-6323
Signed-off-by: Andrej Valek
Signed-off-by: Pascal Bach
---
meta/recipes-core/glibc/glibc/CVE-2016-6323.patch | 39 +++
meta/recipes-core/glibc/glibc_2.24.bb
arm: mark __startcontext as .cantunwind, GNU
CVE: CVE-2016-6323
Signed-off-by: Andrej Valek
Signed-off-by: Pascal Bach
---
meta/recipes-core/glibc/glibc/CVE-2016-6323.patch | 39 +++
meta/recipes-core/glibc/glibc_2.23.bb
On mercredi 19 avril 2017 13:57:40 CEST Alexander Kanavin wrote:
> On 04/19/2017 02:53 PM, David Vincent wrote:
> >> This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I
> >> think. Look for examples in rootfs-postcommands.bbclass.
> >
> > The problem of ROOTFS_POSTPROCESS_COMMAND
On 04/19/2017 02:57 PM, Alexander Kanavin wrote:
On 04/19/2017 02:53 PM, David Vincent wrote:
This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I
think. Look for examples in rootfs-postcommands.bbclass.
The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot
On 19 April 2017 at 09:57, André Draszik wrote:
> This patch is being removed with this change, and so uclibc builds will
> fail. Is it time to remove all remaining references to uclibc?
>
Yes!
Ross
--
___
Openembedded-core mailing
On 04/19/2017 02:53 PM, David Vincent wrote:
This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I
think. Look for examples in rootfs-postcommands.bbclass.
The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot function
that is run at image creation. In my case, I
On mercredi 19 avril 2017 12:21:18 CEST Alexander Kanavin wrote:
> On 04/19/2017 11:27 AM, David Vincent wrote:
> > The package is then chosen during image creation based on some
> > MACHINE_FEATURES, i.e. if the machine provides a crypto accelerator to use
> > instead of relying on software
On 04/19/2017 11:27 AM, David Vincent wrote:
The package is then chosen during image creation based on some
MACHINE_FEATURES, i.e. if the machine provides a crypto accelerator to use
instead of relying on software implementations. I hope that these new details
will help you understand what I was
Setting POSIX_SHELL to "/usr/bin/env sh" fails when tested in
libopts.m4 with test -x "$POSIX_SHELL".
This patch sets the POSIX_SHELL variable to "/bin/sh".
Signed-off-by: Gabriel Ionescu
---
meta/recipes-devtools/autogen/autogen-native_5.18.12.bb | 2 +-
1 file
Hi,
Generally, cups serial backend is supported by “cups-filter” package. You can
find that package in the “meta-printing” layer:
https://github.com/rossburton/meta-printing
Hope this helps,
Maxin
From: openembedded-core-boun...@lists.openembedded.org
Sorry, this should be my fault, this fix is fine to me.
// Robert
On 04/19/2017 04:57 PM, Paul Eggleton wrote:
We were specifying a default parameter; the get() function defined here
does not take such a parameter. I appears this code had not been tested.
This fixes runqemu erroring out
On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote:
> Use memset() API instead of __bzero()
> Drop the patch removing des_* functions for musl
>
> Signed-off-by: Khem Raj
> ---
> .../0001-replace-__bzero-with-memset-API.patch | 28 +
>
The following changes since commit ba2884f6ad3a4e746fc80cbd707f83fa8abd4210:
oe-run-native: print more error messages (2017-04-14 10:26:10 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/esdk-runqemu-fixes
In order to have a shared sysroot usable within the eSDK after recipe
specific sysroots were implemented, we need to run
bitbake build-sysroots as a separate call. However, unlike the first
call, --quiet wasn't being specified and that somewhat undermined the
earlier effort to clean up the eSDK
Currently, in order to figure out variable values when run within the
eSDK, runqemu does not use the standard SDK method nor is it able to run
bitbake (since the eSDK environment isn't initialised like the normal
OE build environment). runqemu really ought to be fixed, but the quick
workaround is
We were specifying a default parameter; the get() function defined here
does not take such a parameter. I appears this code had not been tested.
This fixes runqemu erroring out immediately when used within the eSDK.
Signed-off-by: Paul Eggleton
---
scripts/runqemu
On 19 April 2017 at 02:58, Khem Raj wrote:
> +-key_secret_is_set;
> ++key_secretkey_is_set;
>
This removes key_secret_is_set, was this a typo upstream or a mistake in
the patch?
Ross
--
___
Openembedded-core mailing list
On jeudi 13 avril 2017 10:05:29 CEST Jussi Kukkonen wrote:
> Hi David,
>
> Just a heads-up: I will propose a revert of this patch this week unless
> better ideas come up in the mean time.
Sorry, I've been away last week so didn't have time to respond to your
previous mails. I've seen the revert
On 19 April 2017 at 04:45, Kyle Russell wrote:
> Thank you. Do I need to submit an amended patch to the mailing list, or
> will your fixup get merged in from your staging branch pending no problems?
>
Don't worry about it, I've fixed it.
Ross
--
From: Kai Kang
I didn't find out this patch, so add a gcc option in V1. Thanks for Ross's help.
The following changes since commit def638ebd69cef217ca567352bc08920b79ca03d:
poky.ent: Removed "python3-expect" package from 3 distros. (2017-04-18
15:51:44 +0100)
are
From: Kai Kang
Backport patch from upstream to fix build failures on ppc and ppc64.
Signed-off-by: Kai Kang
---
.../libsdl2/libsdl2/fix-build-failure-on-ppc.patch | 50 ++
meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb |
60 matches
Mail list logo