G'day All,
How can I run fetchall so that it will also fetch all package sources related
to the sdk as well as the image.
ie: "bitbake -c fetchall myimage" gets all the sources to build myimage,
allowing a build to proceed without network access later.
Out sdk however includes a few extra
Signed-off-by: Wang Mingyu
---
.../{python3-pygments_2.12.0.bb => python3-pygments_2.13.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pygments_2.12.0.bb =>
python3-pygments_2.13.0.bb} (83%)
diff --git
The following changes since commit 10891d4d955f347c328cf8c099031f05f5c855a2:
lttng-modules: replace mips compaction fix with upstream change (2022-08-17
04:55:49 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
On 2022-08-25 19:24, Khem Raj wrote:
On Thu, Aug 25, 2022 at 12:11 PM Randy MacLeod
wrote:
On 2022-08-25 07:53, Richard Purdie wrote:
On Thu, 2022-08-25 at 13:04 +0200, Alexander Kanavin wrote:
On Thu, 25 Aug 2022 at 12:59, Richard Purdie
wrote:
The usptreamable version of the patch would
Fixes build errors seen with clang/musl like on x86
error: the 'sse' unit is not supported with this instruction set
Signed-off-by: Khem Raj
---
meta/recipes-extended/ltp/ltp_20220527.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/ltp/ltp_20220527.bb
On Thu, Aug 25, 2022 at 12:11 PM Randy MacLeod
wrote:
>
> On 2022-08-25 07:53, Richard Purdie wrote:
> > On Thu, 2022-08-25 at 13:04 +0200, Alexander Kanavin wrote:
> >> On Thu, 25 Aug 2022 at 12:59, Richard Purdie
> >> wrote:
> >>> The usptreamable version of the patch would probably be
On Thu, Aug 25, 2022 at 3:49 AM Richard Purdie
wrote:
>
> We see a lot of warnings about incorrect processor types on qemuppc, drowning
> out anything else. Fix the option.
>
> Signed-off-by: Richard Purdie
> ---
> meta/classes-recipe/rust-target-config.bbclass | 2 +-
> 1 file changed, 1
On Thu, Aug 25, 2022 at 1:35 PM Luca Ceresoli wrote:
>
> Hi Khem,
>
> On Thu, 25 Aug 2022 00:21:03 -0700
> "Khem Raj" wrote:
>
> > AC_TRY_RUN macro means the test needs to run to find the result and we
> > are cross compiling so this will always get wrong results, this results
> > in
Hit this error while building nlf-native recently:
{
"error": {
"summary": "URI malformed",
"detail": ""
}
}
Some poking about led me to discover that:
1) The npm.py tool replaces npm:// with http://, not https://
2) Some versions of the npm tool don't handle 301 redirects properly,
Hi Khem,
On Thu, 25 Aug 2022 00:21:03 -0700
"Khem Raj" wrote:
> AC_TRY_RUN macro means the test needs to run to find the result and we
> are cross compiling so this will always get wrong results, this results
> in miscompiling apache2 on musl because it disables rlimit
> (ac_cv_struct_rlimit)
This script can be used directly from poky or oe-core, or can be copied directly
into alayer or any other repository - it is self-suffucient and requires only
python3
and git on the host where it will run. It is also copied by the bitbake-layers
layers-setup plugin together with the json, unless
This does a basic run-through of the bitbake-layers plugin, and the resulting
json layer config
and the layer setup script that uses it. Only poky is actually fetched by the
script.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/bblayers.py | 22 ++
1
From: Joshua Watt
Defines a common schema for layer setup that can be consumed by tools to
know how to fetch and assemble layers for end users. Also includes an
example of the layer setup that constructs poky/meta-intel/imaginary product
layer
for reference.
The schema can be used to validate
This addresses a long standing gap in the core offering:
there is no tooling to capture the currently configured layers
with their revisions, or restore the layers from a configuration
file (without using external tools, some of which aren't particularly
suitable for the task). This plugin
This is the reverse of setting up a build by pointing TEMPLATECONF to a
directory
with a template and running '. oe-init-build-env': this takes the config files
from build/conf,
replaces site-specific paths in bblayers.conf with ##OECORE##-relative paths,
and copies
the config files into a
I added to support 7-Zip in conversion types/commands. It is fully configurable
in compression level, method and file extension.
From: "Benjamin Szőke"
Date: Thu, 25 Aug 2022 21:45:55 +0200
Subject: [PATCH] image_types: add 7-Zip support in conversion types and commands
---
> -Original Message-
> From: Alexander Kanavin
> Sent: den 25 augusti 2022 11:19
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> ; Richard Purdie
> Subject: Re: [OE-core] [PATCH 2/2] scripts/oe-setup-builddir: add a check
> that TEMPLATECONF
On 2022-08-25 07:53, Richard Purdie wrote:
On Thu, 2022-08-25 at 13:04 +0200, Alexander Kanavin wrote:
On Thu, 25 Aug 2022 at 12:59, Richard Purdie
wrote:
The usptreamable version of the patch would probably be something which
splits the target names in no_atomics up into components and
Am Do, 25. Aug 2022 um 12:17:06 + schrieb Ross Burton
:
Note that if wpa_supplicant and iwd are mutually exclusive, you can
express that in the PACKAGECONFIG:
I didn't want to make the decision whether wpa_supplicant and iwd
should be mutually exclusive. Although I think mixed operation
From: Andrei Gherzan
With the current regex expression, a machine that is not part of the
compatible could match the regex expression.
For example, consider the following COMPATIBLE_MACHINE:
COMPATIBLE_MACHINE = "qemuarm|qemuarm64"
A machine definition bringing in "qemuarm-foo" would match
From: Andrei Gherzan
The libnss configuration file is only installed when glibc is used. The
inexistence of it on a musl-based rootfs, will make shadow complain
about it:
Failed opening /etc/nsswitch.conf
This is because shadow will try to use nsswich when dealing with
subordinate IDs and the
From: Andrei Gherzan
When creating users, shadow-utils might create backup files for
subordinate ID files (subid, subgid). Make sure we clean them up
similarly to the other backup files shadow-utils creates.
This is a backport from master that brings in only the cleanup of the
subid backup
From: Andrei Gherzan
shadow utils are used when creating users at image creation time. The
useradd/usermod tools will only try to add a default configuration for
subid files if they exist.
Signed-off-by: Andrei Gherzan
---
meta/recipes-extended/shadow/shadow.inc | 7 +++
1 file changed, 7
Am Do, 25. Aug 2022 um 16:59:58 +0200 schrieb Quentin Schulz
:
From the comment " For smooth operation it would be best to start
only one wireless daemon at a time." I gathered that both can be
enabled at once.
Correct. Connman doesn't really care if both wpa_supplicant and iwd are
running.
On Thu, 2022-08-25 at 14:03 +0200, Peter Bergin wrote:
> Hi Richard,
>
> On 2022-08-25 10:21, Richard Purdie wrote:
> >
> > > I've tried locally to reproduce something. I've built and tested
> > > genericx86 and qemuarm64 now on core-image-sato sdk that I saw was the
> > > target for the
Hi Ross,
On 8/25/22 14:17, Ross Burton wrote:
On 24 Aug 2022, at 13:50, Markus Volk via lists.openembedded.org
wrote:
+# For smooth operation it would be best to start only one wireless daemon at a
time.
+# If wpa_supplicant is running, connman will use it preferentially.
+# Select either
On Thu, Aug 25, 2022 at 3:02 AM Luca Ceresoli wrote:
>
> Hi Khem,
>
> On Wed, 24 Aug 2022 09:57:13 -0700
> "Khem Raj" wrote:
>
> > On Wed, Aug 24, 2022 at 9:52 AM Luca Ceresoli
> > wrote:
> > >
> > > Hi Khem,
> > >
> > > On Tue, 23 Aug 2022 11:01:51 -0700
> > > "Khem Raj" wrote:
> > >
> > > >
crossbeam-utils tries to use the triplet to look up whether the target
supports various forms of atomics. We use TARGET_VENDOR and not "-unknown"
in the target case which means this fails and breaks platforms like mips
and powerpc 32 bit. Add a patch to handle TARGET_VENDOR in this case.
On Wed, Aug 24, 2022 at 9:34 PM Marta Rybczynska wrote:
>
>
>
> On Thu, Aug 25, 2022 at 9:25 AM ghassaneben wrote:
>>
>> From: ghassaneben
>>
>> Increase the size of loop variables in the printf() implementation to avoid
>> integer overflow on multi-gigabyte string arguments. CVE-2022-35737.
I've sent a separate patch for meta-yocto to poky@ list, does that help?
Alex
On Thu, 25 Aug 2022 at 15:37, Luca Ceresoli wrote:
>
> Hello Alex,
>
> On Wed, 24 Aug 2022 14:42:33 +0200
> "Alexander Kanavin" wrote:
>
> > This sets the ground for standardizing (and enforcing) the location of
> >
Forgot the branch prefix, resending.
Ross
> On 25 Aug 2022, at 14:36, Ross Burton via lists.openembedded.org
> wrote:
>
> By naming this test class git.py, any attempt to import GitPython (as
> needed by oelib.buildhistory) failed.
>
> As this class exercises the intercepts, rename it to
We can't rely on the host objcopy knowing how to process target binaries,
so use the cross objcopy in the sysroot instead.
Also construct the command argument-by-argument as the format expression
was getting unwieldy.
(From OE-Core rev: 0264aeedbf21e9e7a104243c11b3b57f00e38bda)
Signed-off-by:
We might want to run a cross tool, such as objcopy, in wic. These are
in a TARGET_SYS/ subdirectory under /usr/bin, so add that directory to
the search path too.
(From OE-Core rev: c523549141e5c31edc75281f581d97867b7d251d)
Signed-off-by: Ross Burton
Signed-off-by: Luca Ceresoli
Signed-off-by:
Wic can build an unified kernel image, but this needs the cross-objcopy
from binutils.
(From OE-Core rev: 7c7a488116f49083ca42d3628ebc0870585110c3)
Signed-off-by: Ross Burton
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
---
meta/classes/image_types_wic.bbclass | 2 ++
In cross-compiles CGO_ENABLED=1 needs to be set explicitly, as otherwise
Go refuses to use it even if CC is already set.
This fixes the selftest on setups where the host and the SDK target
don't have matching architectures.
[ YOCTO #14859 ]
(From OE-Core rev:
By naming this test class git.py, any attempt to import GitPython (as
needed by oelib.buildhistory) failed.
As this class exercises the intercepts, rename it to intercept.py.
(From OE-Core rev: d557cbbf86767bc2ebf2beb3d70af3b3ca5e0529)
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
By default 'go mod' creates read-only files, but that just complicates
things. Add -modcacherw to make the cache read/write, so it can be
cleaned up without needing to chmod.
(From OE-Core rev: 7ff30e0d9fe8527cbc2f8ca84e0300fdc84663b6)
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
Hello Alex,
On Wed, 24 Aug 2022 14:42:33 +0200
"Alexander Kanavin" wrote:
> This sets the ground for standardizing (and enforcing) the location of
> configuration templates: let's start with the default one.
>
> Signed-off-by: Alexander Kanavin
I have been trying to apply this patch, and it
Wic can build an unified kernel image, but this needs the cross-objcopy
from binutils.
(From OE-Core rev: 7c7a488116f49083ca42d3628ebc0870585110c3)
Signed-off-by: Ross Burton
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard Purdie
---
meta/classes/image_types_wic.bbclass | 2 ++
We can't rely on the host objcopy knowing how to process target binaries,
so use the cross objcopy in the sysroot instead.
Also construct the command argument-by-argument as the format expression
was getting unwieldy.
(From OE-Core rev: 0264aeedbf21e9e7a104243c11b3b57f00e38bda)
Signed-off-by:
We might want to run a cross tool, such as objcopy, in wic. These are
in a TARGET_SYS/ subdirectory under /usr/bin, so add that directory to
the search path too.
(From OE-Core rev: c523549141e5c31edc75281f581d97867b7d251d)
Signed-off-by: Ross Burton
Signed-off-by: Luca Ceresoli
Signed-off-by:
By default 'go mod' creates read-only files, but that just complicates
things. Add -modcacherw to make the cache read/write, so it can be
cleaned up without needing to chmod.
(From OE-Core rev: 7ff30e0d9fe8527cbc2f8ca84e0300fdc84663b6)
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
By naming this test class git.py, any attempt to import GitPython (as
needed by oelib.buildhistory) failed.
As this class exercises the intercepts, rename it to intercept.py.
(From OE-Core rev: d557cbbf86767bc2ebf2beb3d70af3b3ca5e0529)
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
In cross-compiles CGO_ENABLED=1 needs to be set explicitly, as otherwise
Go refuses to use it even if CC is already set.
This fixes the selftest on setups where the host and the SDK target
don't have matching architectures.
[ YOCTO #14859 ]
(From OE-Core rev:
> On 24 Aug 2022, at 08:16, Markus Volk via lists.openembedded.org
> wrote:
>
> Hi,
>
> one question regarding this part of packagegroup-base.bb:
>
> SUMMARY:packagegroup-base-wifi = "WiFi support"
> RDEPENDS:packagegroup-base-wifi = "\
> iw \
> wireless-regdb-static \
>
On 24 Aug 2022, at 13:50, Markus Volk via lists.openembedded.org
wrote:
> +# For smooth operation it would be best to start only one wireless daemon at
> a time.
> +# If wpa_supplicant is running, connman will use it preferentially.
> +# Select either wpa_supplicant or iwd
> +WIRELESS_DAEMON
On 24 Aug 2022, at 13:09, Quentin Schulz via lists.openembedded.org
wrote:
>
> Hi all,
>
> On 8/24/22 11:51, Luca Ceresoli via lists.openembedded.org wrote:
>> Hello Markus,
>> On Wed, 24 Aug 2022 10:56:54 +0200
>> "Markus Volk" wrote:
>>> Hello Luca,
>>>
>>> Am Mi, 24. Aug 2022 um 10:54:40
Hi Richard,
On 2022-08-25 10:21, Richard Purdie wrote:
I've tried locally to reproduce something. I've built and tested
genericx86 and qemuarm64 now on core-image-sato sdk that I saw was the
target for the autobuilder. Both tests passes. The failure I see in the
autobuilder logs is that the
Source: https://github.com/golang/go
MR: 120622, 120625
Type: Security Fix
Disposition: Backport from
https://github.com/golang/go/commit/76f8b7304d1f7c25834e2a0cc9e88c55276c47df &&
https://github.com/golang/go/commit/2678d0c957193dceef336c969a9da74dd716a827
ChangeID:
Add a new selftest to exercise the debuginfod support, by starting a
debuginfod on DEPLOY_DIR and verifying that an image can fetch the
symbols for a binary.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/selftest/cases/debuginfod.py | 44 ++
1 file changed, 44 insertions(+)
On Thu, 2022-08-25 at 13:04 +0200, Alexander Kanavin wrote:
> On Thu, 25 Aug 2022 at 12:59, Richard Purdie
> wrote:
> > The usptreamable version of the patch would probably be something which
> > splits the target names in no_atomics up into components and matched on
> > subsections of it rather
On Thu, 25 Aug 2022 at 12:59, Richard Purdie
wrote:
> The usptreamable version of the patch would probably be something which
> splits the target names in no_atomics up into components and matched on
> subsections of it rather than the whole string. My rust isn't really up
> to doing that though.
On Thu, 2022-08-25 at 12:52 +0200, Alexander Kanavin wrote:
> This will complicate version updates unfortunately, as updating
> .cargo-checksum.json is a pain :(
> Can we try to arrive at something upstreamable?
The usptreamable version of the patch would probably be something which
splits the
On Thu, 2022-08-25 at 12:53 +0200, Alexander Kanavin wrote:
> What would be much preferred is an explicit switch to disable atomics
> on the platforms where we know they don't work.
There is a list of such platforms in no_atomics.rs. This patch means we
don't have to add the switch for every
What would be much preferred is an explicit switch to disable atomics
on the platforms where we know they don't work.
Alex
On Thu, 25 Aug 2022 at 12:52, Alexander Kanavin wrote:
>
> This will complicate version updates unfortunately, as updating
> .cargo-checksum.json is a pain :(
> Can we try
This will complicate version updates unfortunately, as updating
.cargo-checksum.json is a pain :(
Can we try to arrive at something upstreamable?
Alex
On Thu, 25 Aug 2022 at 12:49, Richard Purdie
wrote:
>
> crossbeam-utils tries to use the triplet to look up whether the target
> supports
This option doesn't seem to exist any more and causes lots of warnings.
Remove it.
Signed-off-by: Richard Purdie
---
meta/classes-recipe/rust-target-config.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes-recipe/rust-target-config.bbclass
crossbeam-utils tries to use the triplet to look up whether the target
supports various forms of atomics. We use TARGET_VENDOR and not "-unknown"
in the target case which means this fails and breaks platforms like mips
and powerpc 32 bit. Add a patch to handle TARGET_VENDOR in this case.
We see a lot of warnings about incorrect processor types on qemuppc, drowning
out anything else. Fix the option.
Signed-off-by: Richard Purdie
---
meta/classes-recipe/rust-target-config.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Everyone,
QA for yocto-3.1.19.rc1 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jay
>
On Thu, 25 Aug 2022 at 11:46, Richard Purdie
wrote:
> Digging further crossbeam-utils has a no_atomics.rs file listing all
> the triplets that can't use atomic or have limited 64 bit ones.
>
> Sadly those triplets don't match the ones were using as we have
> TARGET_VENDOR in ours, for reasons.
Hi Khem,
On Wed, 24 Aug 2022 09:57:13 -0700
"Khem Raj" wrote:
> On Wed, Aug 24, 2022 at 9:52 AM Luca Ceresoli
> wrote:
> >
> > Hi Khem,
> >
> > On Tue, 23 Aug 2022 11:01:51 -0700
> > "Khem Raj" wrote:
> >
> > > Fix build with musl
> > >
> > > Signed-off-by: Khem Raj
> >
> > AB testing
On Fri, 2022-08-19 at 19:29 -0700, Randy MacLeod wrote:
> For qemuppc/mips, rustfmt isn't being built so check
> that it and related tools exist before copying them.
> qemuppc/mips are not well-supported in the Rust world
> but will work to get the build to fixed later.
>
> Signed-off-by: Randy
On Thu, 25 Aug 2022 at 09:19, Peter Kjellerstedt
wrote:
>
> > We are trying to move towards standardizing build configuration
> > management. One step towards that goal is that config templates must
> > live in meta-some-layer/conf/templates, and aren't scattered around,
> > or generated on the
Hi Peter,
On Thu, 2022-08-25 at 09:17 +0200, Peter Bergin wrote:
> On 2022-08-24 10:52, Richard Purdie wrote:
> > On Tue, 2022-08-23 at 10:56 +0200, Peter Bergin wrote:
> > > The test for rust in the SDK is extended with the simplest
> > > possible build script. This will make use of the host
On Thu, Aug 25, 2022 at 9:25 AM ghassaneben wrote:
> From: ghassaneben
>
> Increase the size of loop variables in the printf() implementation to
> avoid integer overflow on multi-gigabyte string arguments. CVE-2022-35737.
> This bug fix refers to: CVE-2022-35737 and it's a backport of a fix
On 08/08/2022 12.20, Sean Nyekjaer wrote:
On Mon, Jul 18, 2022 at 04:12:25PM +, Ross Burton wrote:
This still seems overkill. You can build minizip from inside the zlib recipe
by fixing the minizip Makefile (fix posted to
https://github.com/madler/zlib/pull/681) and then adding one
From: ghassaneben
Increase the size of loop variables in the printf() implementation to avoid
integer overflow on multi-gigabyte string arguments. CVE-2022-35737. This bug
fix refers to: CVE-2022-35737 and it's a backport of a fix added in sqlite
3.39.2 (2022-07-21).
Original commit:
Source: https://github.com/golang/go
MR: 120613, 120613
Type: Security Fix
Disposition: Backport from
https://github.com/golang/go/commit/c15a8e2dbb5ac376a6ed890735341b812d6b965c &&
https://github.com/golang/go/commit/0117dee7dccbbd7803d88f65a2ce8bd686219ad3
ChangeID:
AC_TRY_RUN macro means the test needs to run to find the result and we
are cross compiling so this will always get wrong results, this results
in miscompiling apache2 on musl because it disables rlimit
(ac_cv_struct_rlimit) wrongly.
All these variables are determined with AC_TRY_RUN checks
> -Original Message-
> From: Alexander Kanavin
> Sent: den 24 augusti 2022 16:53
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
>
> Subject: Re: [OE-core] [PATCH 2/2] scripts/oe-setup-builddir: add a check
> that TEMPLATECONF is valid
>
> On
Hi Richard,
On 2022-08-24 10:52, Richard Purdie wrote:
On Tue, 2022-08-23 at 10:56 +0200, Peter Bergin wrote:
The test for rust in the SDK is extended with the simplest
possible build script. This will make use of the host toolchain
for building build.rs before building the rust package for
72 matches
Mail list logo
