From: Bartosz Golaszewski
Add the firmware package for the ATH12K module.
Signed-off-by: Bartosz Golaszewski
---
.../linux-firmware/linux-firmware_20240312.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux
On Tue, Mar 26, 2024 at 11:56 AM Bartosz Golaszewski wrote:
>
> On Wed, Mar 20, 2024 at 5:44 PM Steve Sakoman wrote:
> >
> > From: Alexander Kanavin
> >
> > License-Update: additional files
> >
> > Signed-off-by: Alexander Kanavin
> > Signed
On Wed, Mar 20, 2024 at 5:44 PM Steve Sakoman wrote:
>
> From: Alexander Kanavin
>
> License-Update: additional files
>
> Signed-off-by: Alexander Kanavin
> Signed-off-by: Richard Purdie
> (cherry picked from commit add81ef0299ea5260f9bdc59ffc8f5cc0e74276f)
> Signed-off-by: Steve Sakoman
>
From: Bartosz Golaszewski
Add the firmware package for the ATH12K module.
Signed-off-by: Bartosz Golaszewski
---
.../linux-firmware/linux-firmware_20240312.bb | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux
From: Bartosz Golaszewski
Update the linux-firmware recipe to the most recent upstream tag.
Signed-off-by: Bartosz Golaszewski
---
...{linux-firmware_20240220.bb => linux-firmware_20240312.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/linux-firmw
On Thu, May 18, 2023 at 6:56 PM Ross Burton wrote:
>
>
>
> > On 17 May 2023, at 17:32, Bruce Ashfield via lists.openembedded.org
> > wrote:
> >
> > I'm not sure if you saw the old threads on this, but we went through this
> > binding in detail in february:
> >
> > See the series from TrevorW:
>
On Wed, May 17, 2023 at 6:15 PM Trevor Gamblin wrote:
>
>
> On 2023-05-17 04:06, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > Add missing RDEPENDS for this package.
> >
> > Signed-off-by: Bartosz Golaszewski
> > ---
> >
From: Bartosz Golaszewski
Extend the manifest with definitions for the turtle package from the
Python standard library. Currently this package cannot be imported at
run-time because python3-misc doesn't pull the required dependencies.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3
From: Bartosz Golaszewski
Extend the manifest with definitions for the zipapp package from the
Python standard library. Currently this package cannot be imported at
run-time because python3-misc doesn't pull the required dependencies.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-pygobject_3.44.1.bb | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-pygobject_3.44.1.bb
b
From: Bartosz Golaszewski
Extend the manifest with definitions for the cgitb package from the
Python standard library. Currently this package cannot be imported at
run-time because python3-misc doesn't pull the required dependencies.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python-pycryptodome.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python-pycryptodome.inc
b/meta/recipes-devtools
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
.../recipes-devtools/python/python3-pyproject-hooks_1.0.0.bb | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-pyproject
From: Bartosz Golaszewski
We no longer support python2. Drop PYTHON_PN and use python3 explicitly.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python-pycryptodome.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/python
From: Bartosz Golaszewski
Cargo and rustc can now be built for the target architecture. There's no
reason to limit the setuptools rust extensions to native build only so
make the RDEPENDS global. Also: add the missing ones.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3-setuptools
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Remove DEPENDS as this package doesn't really have any.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3-sphinx-rtd-theme_1.2.0.bb | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-installer_0.7.0.bb | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-installer_0.7.0.bb
b/meta/recipes
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-pathspec_0.11.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pathspec_0.11.1.bb
b/meta/recipes
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-tomli_2.0.1.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-tomli_2.0.1.bb
b/meta/recipes-devtools
From: Bartosz Golaszewski
The main hypothesis module depends on pytest already so move it to
global RDEPENDS from ptest-specific ones.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-hypothesis_6.71.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-dtschema_2023.4.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-dtschema_2023.4.bb
b
From: Bartosz Golaszewski
Add a recipe for python bindings for libfdt (spun out of upstream dtc)
fetched from pypi.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3-libfdt_1.7.0.post1.bb | 20 +++
1 file changed, 20 insertions(+)
create mode 100644 meta/recipes
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-certifi_2022.12.7.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-certifi_2022.12.7.bb
b/meta/recipes
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-attrs_23.1.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/python/python3-attrs_23.1.0.bb
b/meta/recipes-devtools/python
From: Bartosz Golaszewski
We no longer support python2. Drop PYTHON_PN and use python3 explicitly.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-attrs_23.1.0.bb | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-devtools
From: Bartosz Golaszewski
I noticed that every now and then I import some python package into an
image only to find out the recipe didn't pull in all required run-time
dependencies. I would fix it whenever I noticed it but figured that I
could right a script that would go over all python
From: Bartosz Golaszewski
The nativesdk and target RDEPENDS are the same and there's nothing that
prohibits this package from build built for the native sysroot either.
Use the global RDEPENDS instead of per-class assignments.
While at it: order the dependencies alphabetically.
Signed-off
From: Bartosz Golaszewski
Add missing RDEPENDS for this package.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python-async.inc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python-async.inc
b/meta/recipes-devtools
From: Bartosz Golaszewski
python3-build has several run-time dependencies that are missing from
the recipe. This makes it impossible to use the module in self-hosted
images. Add missing RDEPENDS.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-build_0.10.0.bb | 11
From: Bartosz Golaszewski
Add the TOML parsing module from the standard library to the manifest.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3/python3-manifest.json| 17 +
1 file changed, 17 insertions(+)
diff --git a/meta/recipes-devtools/python/python3
From: Bartosz Golaszewski
Add the pip bootstrapping module from the standard library to the
manifest. This module is a run-time requirement of python3-build.
Signed-off-by: Bartosz Golaszewski
---
.../python/python3/python3-manifest.json | 23 +++
1 file changed, 23
From: Bartosz Golaszewski
python3-build cannot be used in self-hosted images due to missing
run-time dependencies in several packages. This series adds required
RDEPENDS to python3-packaging and python3-pyproject-hooks, extends the
manifest to include standard tomllib and ensurepip package
From: Bartosz Golaszewski
JSON module is required at run-time by pyproject-hooks.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-pyproject-hooks_1.0.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyproject
From: Bartosz Golaszewski
python3-profile is required by python3-packaging at run-time.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3-packaging_23.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/python/python3-packaging_23.0.bb
b
From: Bartosz Golaszewski
Some PACKAGECONFIG switches enable building of additional artifacts that
end up in sub-packages for a recipe. For example in foo.bb we have:
PACKAGES =+ "foo-bar"
PACKAGECONFIG[bar] = "--enable-bar,--disable-bar,libdep"
FILES:foo-bar = &q
From: Bartosz Golaszewski
Unless we're using systemd, dbus is not pulled into the system
automatically. Bluez5 will not work without dbus so add it to RDEPENDS
explicitly.
Signed-off-by: Bartosz Golaszewski
---
v1 -> v2:
- don't overwrite RDEPENDS, use '+='
meta/recipes-connectivity/blu
From: Bartosz Golaszewski
Unless we're using systemd, dbus is not pulled into the system
automatically. Bluez5 will not work without dbus so add it to RDEPENDS
explicitly.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
1 file changed, 1 insertion
On Thu, Jul 21, 2022 at 3:52 PM Khem Raj wrote:
>
> I don’t see config.log for Libstdc++ folder in there
> Can you see why that’s missing ?
>
I was missing because I misunderstood you - you were probably asking
for the config.log *with* Jon's patch applied.
Here's the log:
On Wed, Jul 20, 2022 at 5:59 PM Khem Raj wrote:
>
>
>
> On Wed, Jul 20, 2022 at 11:35 AM Bartosz Golaszewski wrote:
>>
>> On Tue, Jul 19, 2022 at 4:58 PM Khem Raj wrote:
>> >
>> > On Tue, Jul 19, 2022 at 10:48 AM Bartosz Golaszewski wrote:
>> >
On Tue, Jul 19, 2022 at 4:58 PM Khem Raj wrote:
>
> On Tue, Jul 19, 2022 at 10:48 AM Bartosz Golaszewski wrote:
> >
> > On Tue, Jul 19, 2022 at 2:54 PM Khem Raj wrote:
> > >
> > >
> > >
> > > On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszews
On Tue, Jul 19, 2022 at 2:54 PM Khem Raj wrote:
>
>
>
> On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszewski wrote:
>>
>> On Tue, Jul 19, 2022 at 12:10 AM Jon Mason wrote:
>> >
>> > On Mon, Jul 18, 2022 at 4:06 PM Khem Raj wrote:
>> > >
>
On Tue, Jul 19, 2022 at 12:10 AM Jon Mason wrote:
>
> On Mon, Jul 18, 2022 at 4:06 PM Khem Raj wrote:
> >
> > Can you try something like this
> >
> > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > index 5d74e4494d..61d5bf6058 100644
> >
Hi!
It seems that the zephyr build is currently broken with master (and
master-next) for meta-zephyr samples:
Build Configuration:
BB_VERSION = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-yocto-eabi"
MACHINE
Hi!
I'm trying to build java support with the following configuration:
Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO
On Wed, Jun 8, 2022 at 3:21 AM Randy MacLeod
wrote:
>
[snip]
>
> Naveen or I will take a look at some point and at least let you know if
> we can reproduce the error.
> Can you try using the master branch to use rust_1.60 ?
> I doubt it will help but it might be easy to check.
>
Actually, the
On Mon, Jun 6, 2022 at 5:23 PM Alexander Kanavin wrote:
>
> Thanks; is this something that oe-core needs to provide? As it's not
> in version lockstep with the rest of gstreamer, it seems more like a
> collection of experimental plugins and is maybe a better fit for
> meta-oe for now?
>
Fine
In order to allow rust packages to define PACKAGECONFIG options, append
the contents of PACKAGECONFIG_CONFARGS to the build command.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/cargo.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/cargo.bbclass b
This adds a recipe for gstreamer plugins written in Rust.
Signed-off-by: Bartosz Golaszewski
---
.../gstreamer1.0-plugins-rs_0.8.4.bb | 465 ++
1 file changed, 465 insertions(+)
create mode 100644
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-rs_0.8.4.bb
This adds a patch to the cargo recipe that prohibits cargo from trying
to update git submodules when running in --offline mode.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/cargo/cargo.inc | 2 +-
...-t-update-submodules-in-offline-mode.patch | 32 +++
2
This series contains some improvements to the cargo build and adds a new
recipe for gstreamer plugins written in rust.
Bartosz Golaszewski (4):
cargo: don't update git submodules in --offline mode
cargo: run in --offline mode
cargo: pass PACKAGECONFIG_CONFARGS to cargo build
gstreamer1.0
We fetch sources ourselves in do_fetch, don't let cargo fetch anything
else on its own during the build stage.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/cargo.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/cargo.bbclass b/meta/classes
Hi!
I have a recipe[1] for a rust project. It builds the gstreamer plugin
for streaming from AWS S3 that is part of the gst-plugins-rs repo. I'm
upgrading the system from dunfell to kirkstone and trying to switch
from using meta-rust to using the rust support from openembedded-core.
The target is
On Sun, Mar 7, 2021 at 4:19 PM Bartosz Golaszewski wrote:
>
> From: Bartosz Golaszewski
>
> pydoc needs tempfile (provided by python3-io) to work. Add python3-io
> to its RDEPENDS.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> meta/recipes-devtools/python/pytho
From: Bartosz Golaszewski
pydoc needs tempfile (provided by python3-io) to work. Add python3-io
to its RDEPENDS.
Signed-off-by: Bartosz Golaszewski
---
meta/recipes-devtools/python/python3_3.9.2.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/python/python3_3.9.2
On Fri, May 15, 2020 at 7:56 AM Richard Purdie
wrote:
>
> On Tue, 2020-05-12 at 16:05 +0200, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
> > override. This way each generate
wt., 12 maj 2020 o 16:05 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
> override. This way each generated set of artifacts is deployed as soon
> as it's ready instead of the do_image_comp
From: Bartosz Golaszewski
Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
override. This way each generated set of artifacts is deployed as soon
as it's ready instead of the do_image_complete task handling the entire
deployement. This allows us to better fine-tune dependencies
śr., 15 kwi 2020 o 12:32 Richard Purdie
napisał(a):
>
> > >
> >
> > Gentle ping.
>
> Gentle reminder that we're in the middle of sorting out a release. This
> will not merge until after the release and I don't have the cycles for
> review of this kind of change right now.
>
Got it, I'll get back
pon., 6 kwi 2020 o 19:02 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
> override. This way each generated set of artifacts is deployed as soon
> as it's ready instead of the do_image_comp
From: Bartosz Golaszewski
Hi Richard et al,
This is another shot at multi-stage image deployment. This time around
I managed to fix the problem with changing task hashes and anonymous
python functions ordering by simply moving the code assigning pre- and
postfuncs for sstate into an even
From: Bartosz Golaszewski
Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
override. This way each generated set of artifacts is deployed as soon
as it's ready instead of the do_image_complete task handling the entire
deployement. This allows us to better fine-tune dependencies
From: Bartosz Golaszewski
This variable is already defined in image.bbclass and there's not need
to redefine it here.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/qemuboot.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/qemuboot.bbclass b/meta/classes
pon., 23 mar 2020 o 18:28 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> This variable is already defined in image.bbclass and there's not need
> to redefine it here.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> meta/classes/qemuboot.bbclass
pon., 30 mar 2020 o 18:31 Richard Purdie
napisał(a):
>
> On Mon, 2020-03-30 at 18:26 +0200, Bartosz Golaszewski wrote:
> > pon., 23 mar 2020 o 18:28 Bartosz Golaszewski
> > napisał(a):
> > > From: Bartosz Golaszewski
> > >
> > > Make each IMAGE_CMD
pon., 23 mar 2020 o 18:28 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
> override. This way each generated set of artifacts is deployed as soon
> as it's ready instead of the do_image_comp
From: Bartosz Golaszewski
This variable is already defined in image.bbclass and there's not need
to redefine it here.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/qemuboot.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/qemuboot.bbclass b/meta/classes
From: Bartosz Golaszewski
Make each IMAGE_CMD task an sstate task with its own IMGDEPLOYDIR
override. This way each generated set of artifacts is deployed as soon
as it's ready instead of the do_image_complete task handling the entire
deployement. This allows us to better fine-tune dependencies
From: Bartosz Golaszewski
Hi Richard,
please take a look at the following patch series. It's a follow up to
my previous attempt[1] and is also related to the dm-verity problem I
described on the list[2].
This time instead of having hardcoded two stages of deployment for simple
and composed
pt., 20 mar 2020 o 00:38 Richard Purdie
napisał(a):
>
> On Thu, 2020-03-19 at 19:20 +0100, Bartosz Golaszewski wrote:
> > If we'll really get to a point where we need to create a hierarchy of
> > multiple levels of image deployment, then maybe we should switch to
> > de
czw., 19 mar 2020 o 18:13 Richard Purdie
napisał(a):
>
> On Thu, 2020-03-19 at 17:44 +0100, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > This is a follow-up to the discussion I started on the OE-core
> > mailing
> > list a couple days ag
czw., 19 mar 2020 o 17:44 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> This is a follow-up to the discussion I started on the OE-core mailing
> list a couple days ago[1]. These patches propose to split the deployment
> of image artifacts into two stages w
From: Bartosz Golaszewski
Instead of using do_image_complete for both the deployment of image
artifacts into DEPLOY_DIR_IMAGE as well as calling the image
post-process commands, split the responsability between two separate
tasks: do_image_deploy will take care of the sstate deployment, while
From: Bartosz Golaszewski
This is a follow-up to the discussion I started on the OE-core mailing
list a couple days ago[1]. These patches propose to split the deployment
of image artifacts into two stages where the first one includes all
"regular" images and takes place before do_imag
From: Bartosz Golaszewski
Currently the artifacts for all image types are deployed to the shared
space at the same time by the do_image_deploy task. This however creates
a problem with circular dependencies if we want to use certain security
features[1]. Because wic is designed to fetch
wt., 17 mar 2020 o 14:45 Quentin Schulz
napisał(a):
>
> Hi Bartosz,
>
> On Tue, Mar 17, 2020 at 02:26:37PM +0100, Bartosz Golaszewski wrote:
> > pon., 16 mar 2020 o 12:01 Richard Purdie
> > napisał(a):
> > >
> > > On Mon, 2020-03-16 at 11:48 +0100, Ba
't do this
with upstream OE-core then something is broken/missing upstream and we
should fix it. This is what I'm trying to do. I'm just looking for the
right way. I don't want to carry some non-upstreamable workaround over
to every other project I'm working on - opt
pon., 16 mar 2020 o 12:01 Richard Purdie
napisał(a):
>
> On Mon, 2020-03-16 at 11:48 +0100, Bartosz Golaszewski wrote:
> > There has been no relevant feedback, but I've been experimenting with
> > various things. I think that the best approach would be to make image
> &g
wt., 10 mar 2020 o 22:23 Bartosz Golaszewski napisał(a):
>
> Hi,
>
> I've been struggling for a while now trying to fix a circular
> dependency issue when the initramfs image needs to access an image
> file generated by the main (for lack of a better term) image recipe.
>
&g
wt., 10 mar 2020 o 23:54 Ayoub Zaki napisał(a):
>
>
> On 10.03.20 23:02, Bartosz Golaszewski wrote:
>
> wt., 10 mar 2020 o 22:33 Ayoub Zaki napisał(a):
>
> Do I implement do_install in image.bbclass so that initramfs can
> depend on core-image-full-cmdline:do_p
the key is appended to
u-boot's DTB. When do_image_wic starts, u-boot and initramfs assembly
are long completed - another reason for not using a wic plugin.
Best regards,
Bartosz Golaszewski
--
___
Openembedded-core mailing list
Openembedded-core@
this would mean that the initramfs
recipe deploys the main image artifact. Should we deploy the images
earlier (before do_image_complete) for the initramfs recipe to fetch
from DEPLOY_DIR_IMAGE? Any other ideas?
Best regards,
Bartosz Golaszewski
[1]
https://github.com/brgl/meta-security/blob/to
pon., 24 lut 2020 o 17:16 akuster808 napisał(a):
>
> wrong ml.
>
> should be yo...@list.yoctoproject.org
>
> On 2/24/20 7:45 AM, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > v4.19 LTS has been dropped in poky in favor of v5.4. Drop the bbap
From: Bartosz Golaszewski
Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying
to use any other checksum conversion will result in a build failure.
Fix it by adding other supported checksum utilities to HOSTTOOLS.
Signed-off-by: Bartosz Golaszewski
---
meta/conf/bitbake.conf
From: Bartosz Golaszewski
v4.19 LTS has been dropped in poky in favor of v5.4. Drop the bbappend
from meta-security as right now the build fails.
Signed-off-by: Bartosz Golaszewski
---
recipes-kernel/linux/linux-yocto_4.%.bbappend | 2 --
1 file changed, 2 deletions(-)
delete mode 100644
From: Bartosz Golaszewski
Only md5sum and sha256sum tools are provided by HOSTTOOLS. For other
checksum utils, the conversions need to depend on coreutils-native.
Signed-off-by: Bartosz Golaszewski
---
meta/classes/image_types.bbclass | 4
1 file changed, 4 insertions(+)
diff --git
śr., 13 lis 2019 o 23:37 Khem Raj napisał(a):
>
> On Wed, Nov 13, 2019 at 7:50 AM Ross Burton wrote:
> >
> > On 13/11/2019 15:04, Mark Hatle wrote:
> > >> This is because the implementation of __pthread_exit() in glibc calls
> > >> pthread_cancel() which leads to pthread_cancel_init() being
śr., 13 lis 2019 o 23:39 Khem Raj napisał(a):
>
> On Wed, Nov 13, 2019 at 12:34 AM Bartosz Golaszewski wrote:
> >
> > This isn't a patch as I'm not sure how to fix the right way it but it
> > seems to my that every program that calls pthread_exit() indirectly
> > r
śr., 13 lis 2019 o 16:04 Mark Hatle napisał(a):
>
>
>
> On 11/13/19 2:34 AM, Bartosz Golaszewski wrote:
> > This isn't a patch as I'm not sure how to fix the right way it but it
> > seems to my that every program that calls pthread_exit() indirectly
> > rdepends on
not sure if the same issue is present in musl - the implementation
of __pthread_exit() there is different.
Please advise on how to best approach this.
Thanks in advance,
Bartosz Golaszewski
--
___
Openembedded-core mailing list
Openembedded-core
pon., 12 sie 2019 o 10:51 Richard Purdie
napisał(a):
>
> On Mon, 2019-08-12 at 09:01 +0200, Bartosz Golaszewski wrote:
> > wt., 30 lip 2019 o 09:22 Bartosz Golaszewski
> > napisał(a):
> > > From: Bartosz Golaszewski
> > >
> > > I accidentally change
wt., 30 lip 2019 o 09:22 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> I accidentally changed the patch author when backporting this from
> upstream qemu. This commit restores the original author.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> ..
pon., 29 lip 2019 o 09:17 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> The build fails on qemu-native if we're using kernels after commit
> 0768e17073dc527ccd18ed5f96ce85f9985e9115. This adds an upstream
> patch that fixes the issue.
>
> Signed-off
From: Bartosz Golaszewski
I accidentally changed the patch author when backporting this from
upstream qemu. This commit restores the original author.
Signed-off-by: Bartosz Golaszewski
---
...4-linux-user-fix-to-handle-variably-sized-SIOCGSTAMP-w.patch | 2 +-
1 file changed, 1 insertion
From: Bartosz Golaszewski
The build fails on qemu-native if we're using kernels after commit
0768e17073dc527ccd18ed5f96ce85f9985e9115. This adds an upstream
patch that fixes the issue.
Signed-off-by: Bartosz Golaszewski
---
v1 -> v2:
- fixed authorship which was accidentally changed w
From: Bartosz Golaszewski
The build fails on qemu-native if we're using kernels after commit
0768e17073dc527ccd18ed5f96ce85f9985e9115. This adds an upstream
patch that fixes the issue.
Signed-off-by: Bartosz Golaszewski
---
NOTE: Resending this because I sent it to the wrong list previously
95 matches
Mail list logo
