When the workspace bbappends are still using the old override syntax
with EXTERNALSRC_pn-*, externalsrc_re will not match, and pn will never
be assigned, leading to a nondescript UnboundLocalError being raised on
the user's terminal. Try to detect that situation and give the user a
hint how to solv
Lgtm
On Sat, Jul 23, 2022 at 4:30 PM Petr Vorel wrote:
> From: Petr Vorel
>
> Backport various post 20220527 release runtime fixes:
> * The concept of max runtime
> * tst_test.sh: Cleanup getopts usage
> * mountns0[1-3]: wait for umount completed in thread_b
>
> Signed-off-by: Petr Vorel
> ---
On Sat, Jul 23, 2022 at 4:34 PM Petr Vorel wrote:
> Hi Khem, all,
>
>
>> > 6 files changed, 466 insertions(+)
>> > create mode 100644
>> meta/recipes-extended/ltp/ltp/0001-memcg-functional-Fix-usage-of-PAGESIZE-from-memcg_li.patch
>> > create mode 100644
>> meta/recipes-extended/ltp/ltp/0001-m
Hi Khem, all,
> > 6 files changed, 466 insertions(+)
> > create mode 100644
> meta/recipes-extended/ltp/ltp/0001-memcg-functional-Fix-usage-of-PAGESIZE-from-memcg_li.patch
> > create mode 100644
> meta/recipes-extended/ltp/ltp/0001-mountns0-1-3-wait-for-umount-completed-in-thread_b.patch
> >
From: Petr Vorel
Backport various post 20220527 release runtime fixes:
* The concept of max runtime
* tst_test.sh: Cleanup getopts usage
* mountns0[1-3]: wait for umount completed in thread_b
Signed-off-by: Petr Vorel
---
Changes v1->v2:
* add patches to SRC_URI (Khem Raj)
...-Fix-usage-of-PA
The following changes since commit bba069463ca3813666d084643b0239b9af0199e1:
classes/cve-check: Move get_patches_cves to library (2022-07-13 05:25:10
-1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openem
This disables tests for runtime system specific functions like fcntl
there is no other change seen
+configure:77372: checking for fcntl
+configure:77372: result: yes
In libsttdc++ configure log outputs.
[YOCTO #14803]
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 3 +
some standalone targets e.g. riscv64-elf disable shared linking for
baremetal ELF ABI in ld, therefore lets make it a static library
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/gcc
Ignore the rmdir cmd if using usrmerge distro feature since the
intention is to delete /lib or /lib64 but not libdir under /usr and
base_libdir = libdir when usrmerge is enabled in distro
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/libgcc-common.inc | 8 ++--
1 file changed, 6 inse
Hi Petr
On Sat, Jul 23, 2022 at 9:24 AM Petr Vorel wrote:
>
> From: Petr Vorel
>
> Backport various post 20220527 release runtime fixes:
> * The concept of max runtime
> * tst_test.sh: Cleanup getopts usage
> * mountns0[1-3]: wait for umount completed in thread_b
>
> Signed-off-by: Petr Vorel
>
From: Petr Vorel
Backport various post 20220527 release runtime fixes:
* The concept of max runtime
* tst_test.sh: Cleanup getopts usage
* mountns0[1-3]: wait for umount completed in thread_b
Signed-off-by: Petr Vorel
---
Hi Richard, Daniel,
could you please test this patchset?
Kind regards,
Currently most of the rust recipes use this code but it is all piecemeal.
Turn the code into a class where things can start to be rationalised. Ultimately
some of the data and python code should be moved to a python library but one
step
at a time.
No functionality changes.
Signed-off-by: Richard
Remove further code duplication by allowing the main function to be
configurable.
Signed-off-by: Richard Purdie
---
meta/classes/rust-target-config.bbclass| 10 --
meta/recipes-devtools/cargo/cargo-cross-canadian.inc | 7 +--
.../rust/rust-cross-canadian-common.inc
Some of the subtleties in the different codepaths for target rust json
generation
were not easy to spot. Start to simplfy the code to make this clearer.
This patch should not have any functionality change.
Signed-off-by: Richard Purdie
---
.../cargo/cargo-cross-canadian.inc| 4 +--
On Sat, 2022-07-23 at 14:27 +0200, Alexandre Belloni wrote:
> Hello,
>
> This doesn't pass the selftests:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3865/steps/14/logs/stdio
>
> 2022-07-23 10:00:43,013 - oe-selftest - INFO -
> pkgdata.OePkgdataUtilTests.test_find_path
Hello,
This doesn't pass the selftests:
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3865/steps/14/logs/stdio
2022-07-23 10:00:43,013 - oe-selftest - INFO -
pkgdata.OePkgdataUtilTests.test_find_path (subunit.RemotedTestCase)
2022-07-23 10:00:43,026 - oe-selftest - INFO - .
When a 'BUILD' target is requested we shouldn't be looking at TARGET_SYS but
at BUILD_SYS. Due to the way rust mangles triplets, we need the HOST_SYS triplet
to work with existing code - fixing that issue is a separate patch.
Also drop the arch_abi argument, it doens't make any sense to a getVar()
Match the code in rust-cross-canadian so that further simplifications
can be considered in future.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/rust/rust-common.inc | 12 ++--
meta/recipes-devtools/rust/rust-cross.inc | 16
2 files changed, 10 insertions(+),
Based upon a patch from Otavio Salvador ,
ensure the target json files are written in the correct order with
the most specific last incase it overwrites earlier files if the prefixes
match.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/rust/rust-cross-canadian-common.inc | 5 +++--
1 f
rust-cross had special handling for armv7 targets but we also need this
for cross-canadian. Merge the code into the main function so everything is
consistent.
Also then fix the arm definition to be arm-eabi since ABI is correctly
being looked up.
Signed-off-by: Richard Purdie
---
meta/recipes-d
References:
https://nvd.nist.gov/vuln/detail/CVE-2022-1354
https://security-tracker.debian.org/tracker/CVE-2022-1354
https://nvd.nist.gov/vuln/detail/CVE-2022-1355
https://security-tracker.debian.org/tracker/CVE-2022-1355
Patches from:
CVE-2022-1354:
https://gitlab.com/libtiff/libtiff/-/commit/8
Hi Khem,
On 2022-07-21 17:29, Khem Raj wrote:
On 7/21/22 11:17 AM, Drew Moseley wrote:
On 2/3/22 9:12 AM, Kyle Russell wrote:
Thanks, Claudius. I really appreciate your responses. I'm not
trying to be pedantic. Since I don't have your test setup, I was
just trying to make sure I underst
22 matches
Mail list logo
