On Tue, Sep 3, 2019 at 9:43 PM Hongzhi.Song wrote:
>
> There are two errors when compile an out of tree kernel module
> using sdk:
>
This is not universally true. Can you expand on what kernel version
and architectures you are building ? I'm able to build kernel modules
across all the arches I'm
On 9/3/19 8:37 AM, Ruslan Bilovol wrote:
> Hi Philip,
>
> I can see now this event in the list of ELCE co-located events.
> Is day 2 track track 2 (Yocto Project and OE maintainers meeting)
> restricted to attend to mainatainers only, or regular OE developers
> can also join?
Anyone can signup.
On 9/3/19 5:39 AM, Bruce Ashfield wrote:
> On Tue, Sep 3, 2019 at 4:10 AM Richard Purdie
> wrote:
>> I'm going to summarise the current state as it will help people see the
>> set of issues we have. We have three issues blocking the current patch
>> queue and kernel uprev, spread over four
Kindly ping.
Zhe
On 8/29/19 9:15 PM, zhe...@windriver.com wrote:
> From: He Zhe
>
> When PACKAGECONFIG libgcrypt is enabled, we would get the following error.
>
> ERROR: /usr/bin/libgcrypt-config should not be used, use an alternative such
> as pkg-config
>
> In oe-core, libgcrypt has been
Maxime
Thanks for this contribution
On 9/3/19 6:56 PM, Maxime Roussin-Bélanger wrote:
> Signed-off-by: Maxime Roussin-Bélanger
> ---
> Changes in v2:
> - Rewrite acpid description to be more meaningful
> - Change grub-bootconf description
>
> meta/recipes-bsp/acpid/acpid.inc
Signed-off-by: Maxime Roussin-Bélanger
---
Changes in v2:
- Rewrite acpid description to be more meaningful
- Change grub-bootconf description
meta/recipes-bsp/acpid/acpid.inc | 6 ++
meta/recipes-bsp/formfactor/formfactor_0.0.bb | 3 +++
Hi Alex
Thank you for your advice and I have a question.
1:-> This does not seem like the right place to me to adjust the settings.
Well, did you mean that I shouldn’t adjust the settings in meta-environment
recipe, instead of it, adjust the settings in the nativesdk-meson recipe?
There are two errors when compile an out of tree kernel module
using sdk:
1. "In file included from ./include/linux/seqlock.h:36:0,
from ./include/linux/time.h:6,
from ./include/linux/stat.h:19,
from ./include/linux/module.h:10,
Hi Armin
Can we cherry-pick this patch to warrior and thud, please ?
On Sat, Aug 31, 2019 at 7:23 AM Khem Raj wrote:
>
> Signed-off-by: Khem Raj
> ---
> .../libgpg-error-1.36-gawk5-support.patch | 142 ++
> .../libgpg-error/libgpg-error_1.36.bb | 1 +
> 2 files
sys/user.h related API fixed on ppc/ppc64
Detailed log [1]
https://git.musl-libc.org/cgit/musl/log/?qt=range=29e8737f81ccc9fbadcf61a75318aa3d0516aafa..6ad514e4e278f0c3b18eb2db1d45638c9af1c07f
Signed-off-by: Khem Raj
---
meta/recipes-core/musl/musl_git.bb | 2 +-
1 file changed, 1
From: Drew Moseley
Signed-off-by: Drew Moseley
---
scripts/runqemu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index 4079f2b17d..44128b118b 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -83,7 +83,7 @@ of the following
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org core-boun...@lists.openembedded.org> On Behalf Of liu.min...@gmail.com
> Sent: den 3 september 2019 11:02
> To: openembedded-core@lists.openembedded.org
> Cc: stefan.ag...@toradex.com; Ming Liu
> Subject:
Hi,
This patch breaks the API of stable-1.5. It is clearly mentioned in the commit
message:
It introduces API-breaking changes in the C and Python APIs, since we
need to be able to return negative time values, which were previously
used as errors (-1ULL).
You can have it in your layer but
Current Dev Position: YP 2.8 M4 Feature FreezeNext Deadline: YP 3.0
Final Release 25th Oct
SWAT Team Rotation:SWAT lead is currently: ArminSWAT team rotation:
Armin -> Paul on Sept. 6, 2019SWAT team rotation: Paul -> Ross on Sept.
13, 2019
On Tue, 2019-09-03 at 16:53 -0400, Jonathan Rajotte-Julien wrote:
> Hi,
>
> This patch breaks the API of stable-1.5. It is clearly mentioned in
> the commit message:
>
> It introduces API-breaking changes in the C and Python APIs, since
> we
> need to be able to return negative time values,
Mark,
In reference to "It typically does NOT include the license of things used
to build the software (such as makefiles, autoconf fragments, etc)".
Since the only file that is licensed under GPLv3 is a M4 macro, does that
mean the current patch is still valid? Shouldn't the GPLv3 license be
Hi,
FYI: I have updated kmscube to perform run-time checks that replace the
existing build-time gbm_bo_map() check (which is what the patch in the
kmscube folder is about), since upstream prefers run-time checks via
weak functions. The commit is here:
On 9/3/19 11:00 AM, Ross Burton wrote:
On 30/08/2019 02:08, Maxime Roussin-Bélanger wrote:
+DESCRIPTION = "In recent linux kernels, the /proc/acpi/event
interface has \
+been deprecated. The same information (and more) is available via
netlink \
+(a way for the kernel to communicate with
These two tests relied on the context containing the results information.
This was moved into the OETestResults class.
Signed-off-by: Nathan Rossi
---
Changes in v2:
- New
---
meta/lib/oeqa/core/tests/test_data.py | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
Add '--run-only-tags' for running tests which match any of the provided
tags, and '--run-exclude-tags' for running all tests except those that
have any of the provided tags.
Signed-off-by: Nathan Rossi
---
Changes in v2:
- New
---
meta/lib/oeqa/selftest/context.py | 11 +++
1 file
Create a oeqa selftest test case to execute the glibc test suite and
report the results. The results are populated into the extraresults
variable of the test case which are written to testresults.json for
resulttool to analyse.
An additional subclass is created to separate the execution with qemu
Create a oeqa selftest test case to execute the gcc test suites and
report the results. The results are populated into the extraresults
variable of the test case which are written to testresults.json for
resulttool to analyse.
An additional subclass is created to separate the execution with qemu
Create a oeqa selftest test case to execute the binutils test suites and
report the results. The results are populated into the extraresults
variable of the test case which are written to testresults.json for
resulttool to analyse.
Signed-off-by: Nathan Rossi
---
Changes in v2:
- Update to use
Rework OETestTag so that it does not rely on the existing decorator code
base and instead inserts the tags into an attribute on the decorated
target (e.g. class/type or method). This allows the use of OETestTag on
classes and method.
In order to filter tagged tests rework the loaders filtering
This series adds support to execute the gnu test suites for binutils,
gcc and glibc. With the intention for enabling automated test running of
these test suites within the OEQA framework such that they can be
executed by the Yocto Autobuilder.
The test suites covered need significant resources or
Correct the 'staging_processfixme' call so that target sysroot and
native sysroot paths are corrected when extracting the stashed build
directory. This is required for 'make check' to work correctly due paths
used in configuration and scripts which point at the native sysroot.
Signed-off-by:
A recipe needs to be created for the test suite due to the dependency
chain between libgcc -> glibc -> libgcc-initial, and the requirements of
the test suite to have libgcc for compilation and execution.
The glibc test suite does not use dejagnu like the gcc test suites do.
Instead a test wrapper
Add a do_check task to implement execution of the gcc component test
suites. The component test suites require execution of compiled programs
on the target.
The implementation provided allows for execution testing against a host
via SSH or within the local build environment using qemu linux-user
At some point the modules in tests/cases/loader/invalid/ were removed,
this test relied on having tests/cases/loader/invalid/oetag.py to
trigger a ImportError in the loader module. Skip this test.
Signed-off-by: Nathan Rossi
---
Changes in v2:
- New
---
meta/lib/oeqa/core/tests/test_loader.py |
The binutils and gcc test suites use dejagnu for execution. Copy the
dejagnu recipe from meta-oe, and update it to 1.6.2.
Signed-off-by: Nathan Rossi
---
Changes in v2:
- New
---
meta/recipes-devtools/dejagnu/dejagnu_1.6.2.bb | 15 +++
1 file changed, 15 insertions(+)
create mode
Create the do_check task in a new recipe 'binutils-cross-testsuite'.
This recipe is built within a target recipe (not -cross) to ensure
correct testing against target specific libraries/etc. The do_check task
is used to execute the binutils test suite for the cross target
binutils. By default this
PRIVATE_LIBS is used to exclude 'private' libraries from getting added to
automatic runtime dependency resolution. This variable currently has to list
all libraries by name, which becomes a maintenance issue if the list
of such libraries frequently changes, or is very large.
This change allows
On Tue, 3 Sep 2019 at 17:29, Alexander Kanavin
wrote:
> PRIVATE_LIBS is used to exclude 'private' libraries from getting added to
> automatic runtime dependency resolution. That variable has to list
> all libraries by name which becomes a maintenance issue if the list
> of such libraries
On 9/3/19 8:36 AM, Bruce Ashfield wrote:
> On Tue, Sep 3, 2019 at 11:15 AM Bruce Ashfield
> wrote:
>> On Tue, Sep 3, 2019 at 11:09 AM akuster808 wrote:
>>>
>>>
>>> On 9/3/19 1:10 AM, Richard Purdie wrote:
I'm going to summarise the current state as it will help people see the
set
Hi Philip,
I can see now this event in the list of ELCE co-located events.
Is day 2 track track 2 (Yocto Project and OE maintainers meeting)
restricted to attend to mainatainers only, or regular OE developers
can also join?
Thanks,
Ruslan
On Tue, Jul 30, 2019 at 8:33 PM Philip Balister wrote:
On Tue, Sep 3, 2019 at 11:15 AM Bruce Ashfield wrote:
>
> On Tue, Sep 3, 2019 at 11:09 AM akuster808 wrote:
> >
> >
> >
> > On 9/3/19 1:10 AM, Richard Purdie wrote:
> > > I'm going to summarise the current state as it will help people see the
> > > set of issues we have. We have three issues
PRIVATE_LIBS is used to exclude 'private' libraries from getting added to
automatic runtime dependency resolution. That variable has to list
all libraries by name which becomes a maintenance issue if the list
of such libraries frequently changes, or is very large.
PRIVATE_LIBS_ALL allows
On 22/08/2019 20:19, Randy MacLeod wrote:
I'm checking if you have done any work on upgrading the
boost recipe? Trevor will work on it if you haven't started.
He's relatively new to YP so depending on how easy the
update is he might bail or need help or take a while.
I know I'm late to this
On Tue, Sep 3, 2019 at 11:09 AM akuster808 wrote:
>
>
>
> On 9/3/19 1:10 AM, Richard Purdie wrote:
> > I'm going to summarise the current state as it will help people see the
> > set of issues we have. We have three issues blocking the current patch
> > queue and kernel uprev, spread over four
On 9/3/19 1:10 AM, Richard Purdie wrote:
> I'm going to summarise the current state as it will help people see the
> set of issues we have. We have three issues blocking the current patch
> queue and kernel uprev, spread over four machines and five autobuilder
> targets:
>
> qemumips64:
>
>
On 30/08/2019 02:08, Maxime Roussin-Bélanger wrote:
+DESCRIPTION = "In recent linux kernels, the /proc/acpi/event interface has \
+been deprecated. The same information (and more) is available via netlink \
+(a way for the kernel to communicate with userspace that is usually used \
+for
From: Henning Schild
NO_PROXY can also contain just suffixes that do not start with a "*". We
failed to match those so far. Just add an extra "*" to also match those
suffixes. If one was there we get "**" which does not hurt.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 2 +-
1
From: Henning Schild
Change to v1:
- fix comment in p4
- move "set -f" all the way up in p4, that was the intention in the
first place
Henning Schild (6):
oe-git-proxy: allow setting SOCAT from outside
oeqa: add case for oe-git-proxy
Revert "oe-git-proxy: Avoid resolving NO_PROXY
From: Henning Schild
This truly fixes the issue that cbc148d5d93d5f3531434fee7b234a16196b3088
wanted to solve, without breaking the iteration over multiple entries.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 3 +++
1 file changed, 3 insertions(+)
diff --git
From: Henning Schild
The script claims it works with dash, make sure that is actually the
case.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/oe-git-proxy b/scripts/oe-git-proxy
index
From: Henning Schild
This allows to write selftests where we can mock the real socat.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/scripts/oe-git-proxy b/scripts/oe-git-proxy
index bb2ed2a46e..8499a99a71
From: Henning Schild
The escaping, splitting and matching of NO_PROXY in oe-git-proxy
deserves its own testcase, add it.
Signed-off-by: Henning Schild
---
meta/lib/oeqa/selftest/cases/oescripts.py | 58 +++
1 file changed, 58 insertions(+)
diff --git
From: Henning Schild
This reverts commit cbc148d5d93d5f3531434fee7b234a16196b3088.
The quoting causes H to be one string with spaces, so looping over
multiple entries does not work anymore.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 4 ++--
1 file changed, 2 insertions(+), 2
On Tue, Sep 3, 2019 at 4:10 AM Richard Purdie
wrote:
>
> I'm going to summarise the current state as it will help people see the
> set of issues we have. We have three issues blocking the current patch
> queue and kernel uprev, spread over four machines and five autobuilder
> targets:
>
>
On 03.09.19 14:22, Henning Schild wrote:
From: Henning Schild
This truly fixes the issue that cbc148d5d93d5f3531434fee7b234a16196b3088
wanted to solve, without breaking the iteration over multiple entries.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 3 +++
1 file changed, 3
This series fixes several issues in oe-git-proxy, mostly related to
matching NO_PROXY entries.
Patch 2 introduces a test that will actually fail until all other
patches are applied. If that is a problem and every commit should be
testable, Patch2 needs to be moved to then end.
Let me know what
From: Henning Schild
The escaping, splitting and matching of NO_PROXY in oe-git-proxy
deserves its own testcase, add it.
Signed-off-by: Henning Schild
---
meta/lib/oeqa/selftest/cases/oescripts.py | 58 +++
1 file changed, 58 insertions(+)
diff --git
From: Henning Schild
This reverts commit cbc148d5d93d5f3531434fee7b234a16196b3088.
The quoting causes H to be one string with spaces, so looping over
multiple entries does not work anymore.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 4 ++--
1 file changed, 2 insertions(+), 2
From: Henning Schild
This truly fixes the issue that cbc148d5d93d5f3531434fee7b234a16196b3088
wanted to solve, without breaking the iteration over multiple entries.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 3 +++
1 file changed, 3 insertions(+)
diff --git
From: Henning Schild
NO_PROXY can also contain just suffixes that do not start with a "*". We
failed to match those so far. Just add an extra "*" to also match those
suffixes. If one was there we get "**" which does not hurt.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 2 +-
1
From: Henning Schild
The script claims it works with dash, make sure that is actually the
case.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/scripts/oe-git-proxy b/scripts/oe-git-proxy
index
From: Henning Schild
This allows to write selftests where we can mock the real socat.
Signed-off-by: Henning Schild
---
scripts/oe-git-proxy | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/scripts/oe-git-proxy b/scripts/oe-git-proxy
index bb2ed2a46e..8499a99a71
== Series Details ==
Series: libnl: don't patch libnl-3.0.pc
Revision: 1
URL : https://patchwork.openembedded.org/series/19665/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
This patch originally came from oe-classic in 2010 with the comment "fix pc file
so that it actually links to the support libraries". If an application wants to
link to the support libraries then it should be using the relevant .pc files to
do so.
oe-core builds successfully with this patch
Drop the musl workaround, as upstream has solved this correctly now.
Signed-off-by: Ross Burton
---
...fix-libnl-3.4.0-musl-compile-problem.patch | 38 ---
.../libnl/{libnl_3.4.0.bb => libnl_3.5.0.bb} | 5 +--
2 files changed, 2 insertions(+), 41 deletions(-)
delete mode
On 31/08/2019 21:45, Andre McCurdy wrote:
It looks like the User-Agent workaround for libedit might not be
needed any more anyway...
wget http://thrysoee.dk/editline/libedit-20190324-3.1.tar.gz
works fine for me ( User-Agent: Wget/1.17.1 (linux-gnu) )
Verified here, patch sent.
Ross
--
This dates from when upstream was for some reason refusing the wget user agent,
but this isn't the case anymore:
$ wget http://www.thrysoee.dk/editline/libedit-20190324-3.1.tar.gz
...
HTTP request sent, awaiting response... 200 OK
Length: 521999 (510K) [application/x-gzip]
Saving to:
Retracting this, upgrade incoming.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signed-off-by: Ross Burton
---
.../0001-PATCH-fix-libnl-3.4.0-musl-compile-problem.patch| 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
a/meta/recipes-support/libnl/libnl/0001-PATCH-fix-libnl-3.4.0-musl-compile-problem.patch
On Wed, 2019-07-31 at 13:53 +, Bedel, Alban wrote:
> AArch64 images are not self-decompressing, thus usually much larger.
> Boot times can be reduced by compressing them in FIT and uImages.
>
> This commit is a backport of commit a725d188b5 (kernel-uboot:
> compress
> arm64 kernels) and
On 30/08/2019 10:33, Yi Zhao wrote:
Fixes:
nfsidmap.c:404:4: error: format not a string literal, argument types not
checked [-Werror=format-nonliteral]
404 |xlog_warn(usage, progname);
|^
These options are not enabled by default, presumably this is a Wind
River
On Fri, 2019-08-23 at 13:41 -0300, Fabio Berton wrote:
> Without this change, images with systemd hang on shutdown/reboot.
I already submitted a patch[1] to fix this which is currently under
review. It is the very same patch with a slightly different log
message as the changes from commit
From: He Zhe
Backport a patch to fix the following failure.
rt_sigtimedwait011 TFAIL : .../sigwaitinfo01.c:58: test_empty_set
(.../sigwaitinfo01.c: 148): Unexpected failure:
TEST_ERRNO=EINVAL(22): Invalid argument
Signed-off-by: He Zhe
---
v2: Rebase
On 9/3/19 5:16 PM, Ross Burton wrote:
> On 03/09/2019 08:55, He Zhe wrote:
>> Kindly ping.
>
> This doesn't apply to current master, can you please rebase?
Oops, v2 is sent.
Thanks,
Zhe
>
> Ross
>
--
___
Openembedded-core mailing list
On 03/09/2019 08:55, He Zhe wrote:
Kindly ping.
This doesn't apply to current master, can you please rebase?
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
From: Ming Liu
Fix a following build issue when usrmerge is enabled:
| WARNING: iputils-s20190709-r0 do_package: iputils: alternative target
(/usr/bin/ping or /usr/bin/ping.iputils) does not exist, skipping...
| WARNING: iputils-s20190709-r0 do_package: iputils: NOT adding alternative
provide
I'm going to summarise the current state as it will help people see the
set of issues we have. We have three issues blocking the current patch
queue and kernel uprev, spread over four machines and five autobuilder
targets:
qemumips64:
Kindly ping.
Zhe
On 8/23/19 3:26 PM, zhe...@windriver.com wrote:
> From: He Zhe
>
> Add a patch to fix the following failure.
> rt_sigtimedwait011 TFAIL : .../sigwaitinfo01.c:58: test_empty_set
> (.../sigwaitinfo01.c: 148): Unexpected failure:
> TEST_ERRNO=EINVAL(22): Invalid argument
>
73 matches
Mail list logo
