On Sun, May 26, 2024, 2:06 PM Alexandre Belloni <
alexandre.bell...@bootlin.com> wrote:
> Please always resend the whole series, I'm not cherry-picking patches
> once they have been dropped.
>
Done
Cheers,
Alejandro
> On 22/05/2024 14:33:06-0600, Alejandro Hernand
NTAINER:pn-perf = "Bruce Ashfield "
RECIPE_MAINTAINER:pn-perl = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-perlcross = "Alexander Kanavin "
+RECIPE_MAINTAINER:pn-picolibc = "Alejandro Hernandez "
+RECIPE_MAINTAINER:pn-picolibc-helloworld = "Alejandro Her
It was previously discovered that mcmodel=medany should be used for RISCV64,
however this was only being set for the applications themselves, but not for
newlib, this meant that we ended up with C library that used a code model and
an application that used another one which is not something we
NTAINER:pn-perf = "Bruce Ashfield "
RECIPE_MAINTAINER:pn-perl = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-perlcross = "Alexander Kanavin "
+RECIPE_MAINTAINER:pn-picolibc = "Alejandro Hernandez "
+RECIPE_MAINTAINER:pn-picolibc-helloworld = "Alejandro Her
On Wed, 22 May 2024 at 04:30, Ross Burton wrote:
> On 21 May 2024, at 19:55, Alejandro Enedino Hernandez Samaniego <
> alejan...@enedino.org> wrote:
> > I did see that comment when I was trying to debug the issue with the
> early compiler tests, however, I couldn't find an easy way to inject
>
tainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -579,6 +579,8 @@ RECIPE_MAINTAINER:pn-pcmanfm = "Alexander Kanavin
"
RECIPE_MAINTAINER:pn-perf = "Bruce Ashfield "
RECIPE_MAINTAINER:pn-perl = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-per
Setting skip_sanity_check=true in the [properties] section of meson.cross allows
early compiler tests to be skipped on cross compilation environments where
sanity applications cant be compiled or tested.
Setting MESON_SKIP_SANITY_CHECK=1 enables this behavior.
Signed-off-by: Alejandro Enedino
On Tue, 21 May 2024 at 13:32, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2024-05-18 at 23:50 -0600, Alejandro Hernandez Samaniego via
> lists.openembedded.org wrote:
> > Enables usage of TCLIBC=picolibc extending OE functionality to build and
> u
On Tue, 21 May 2024 at 05:38, Ross Burton wrote:
>
>
> > On 19 May 2024, at 06:50, Alejandro Hernandez Samaniego via
> lists.openembedded.org
> wrote:
> > +# Use the same method that picolibc uses to bypass early compiler tests
> on meson,
> > +# otherwise meson
On Sun, 19 May 2024 at 00:37, Khem Raj wrote:
> On Sat, May 18, 2024 at 10:48 PM Alejandro Hernandez Samaniego via
> lists.openembedded.org
> wrote:
> >
> > It was previously discovered that mcmodel=medany should be used for
> RISCV64,
> > however this was only
It appears that it is no longer necessary to disable security cflags for
newlib targets, with the exception of RISCV architectures where the linker
does not support PIE
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/conf/distro/include/tclibc-newlib.inc | 6 +++---
1 file
nc
@@ -579,6 +579,8 @@ RECIPE_MAINTAINER:pn-pcmanfm = "Alexander Kanavin
"
RECIPE_MAINTAINER:pn-perf = "Bruce Ashfield "
RECIPE_MAINTAINER:pn-perl = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-perlcross = "Alexander Kanavin "
+RECIPE_MAINTAINER:pn-picolibc
When the meson build configuration file is generated the exe_wrapper value
was being hardcoded, however, there may be applications which require for us
to use a different value.
To allow for this value to be manually set; create a variable EXEWRAPPER_EXE
that defaults to
It was previously discovered that mcmodel=medany should be used for RISCV64,
however this was only being set for the applications themselves, but not for
newlib, this meant that we ended up with C library that used a code model and
an application that used another one which is not something we
bitbake python3 -c create_manifest revealed several changes that were missing.
This commit contains a manual cherry-picked version of those, making sure that
new RDEPENDS are reflected since the last time this was updated.
In this case its taking out unnecessary dependencies to python3-profile
by
both contexts.
As a supplement to this change, when creating the merged usr symlinks at the
do_populate_sdk stage,
these need to be created for both the target and native sysroots within the SDK.
Signed-off-by: Maanya Goenka
Signed-off-by : Alejandro Hernandez Samaniego
---
meta/classes
- COPYING.LICENSE: Added Apache-2.0-with-LLVM-exception from newlibs commit
96ec8f868e1a0f5a75badfe4627a41f12cce742d
applicable to newlib/libc/machine/aarch64.
- Also switch libgloss to use PV from newlib.inc instead to align with the
newlib recipe behavior.
Signed-off-by: Alejandro Enedino
It was previously discovered that there was a race condition during the Makefile
execution between the assemble and compile targets, the previous fix attempted
to serialize the build targets, but the fix was missing for x86-64.
Pull in latest commit from upstream to fix this issue on x86-64.
The conditional for the DTB nomenclature hasnt changed
and the 4.7 kernel is old enough at this point, hence
this check has become unnecessary'
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/conf/machine/qemuarmv5.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 10/11/23 15:54, Bruce Ashfield wrote:
On Wed, Oct 11, 2023 at 5:39 PM Richard Purdie
wrote:
On Tue, 2023-10-10 at 19:11 -0600, Alejandro Enedino Hernandez
Samaniego wrote:
>
>
>
>
> On 10/6/23 05:36, Richard Purdie wrote:
>
>
> >
> > Drop the
On 10/6/23 05:36, Richard Purdie wrote:
Drop the version overrides for the kernel for the x86 and arm machines
so we can go back to following the distro versions. The reasons for
these versions is mostly historical at this point as the issues were
resolved.
Signed-off-by: Richard Purdie
---
On 9/2/23 00:53, Richard Purdie wrote:
On Fri, 2023-09-01 at 23:32 +, Michelle Lin wrote:
Currently, there is not a class to support the building of unified kernel
images. Adding a uki.bbclass to support the creation of UKIs. This class calls
the systemd Ukify tool, which will combine the
Acked-by: Alejandro Hernandez
On 9/1/23 17:32, Michelle Lin wrote:
Currently, there is not a class to support the building of unified kernel
images. Adding a uki.bbclass to support the creation of UKIs. This class calls
the systemd Ukify tool, which will combine the kernel/initrd/stub
Sounds good to me!, to be fair, I do believe we are moving in the right
direction,
perhaps we're just missing a couple of test cases to expand our testing
spectrum.
Cheers,
Alejandro
On Sun, 25 Jun 2023 at 02:46, wrote:
> Hi Alejandro
>
> Thank you.
> I will prepare another patch to bring the
logger.warn() has been deprecated, logger.warning() should be used instead.
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
scripts/runqemu | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index 62774a3b98..6a3fbb2d6f 100755
---
When runqemu tries to call runqemu-ifup to create tap devices, it checks the
output of runqemu-ifup to get the newly created tap device.
The behavior of runqemu-ifup was recently modified along with its output, it
no longer expects the uid parameter to be passed and it prints out a warning
if it
Hello,
I've already replied on another thread of this patch series, however, I
have discovered this is the patch that is causing the problem.
On Fri, 23 Jun 2023 at 03:31, Jörg Sommer via lists.openembedded.org
wrote:
> On 22 June 2023 19:01, openembedded-core@lists.openembedded.org wrote:
> >
Hello,
I hate to be the bearer of bad news, but I just discovered an issue on my
CI regarding this patch (or this patch series), this happens when trying to
run testimage (with no pre-existing tap devices):
runqemu - INFO - Setting up tap interface under sudo
Traceback (most recent call last):
There was a race condition during the Makefile execution in
between the assemble and compile targets, only the assemble
target had a dependency on creating the build directory.
If the compile target was executed first, an error was thrown
by bitbake since the build directory did not exist yet:
|
On Fri, 16 Jun 2023 at 02:36, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2023-06-09 at 16:12 -0600, Alejandro Hernandez Samaniego wrote:
> > Update to the latest SRCREV to bring fixes using the proper entry
> > addresses for ARM architectures [
Since https://git.yoctoproject.org/poky/commit/?id=51063c1e6ac
we need to pass exactly 2 arguments to runqemu-ifup, otherwise
the script will return an error since bindir is no longer being
used.
However the call to runqemu-ifup from runqemu is still passing
bindir as an argument resulting in the
Hello,
Just to add more information to this, I've noticed a failure on my test
environment today while trying to run -c testimage, apparently due to one
of these fixes:
Command '('sudo', '/home/vsts/poky/scripts/runqemu-ifup', '1001', '123',
Update to the latest SRCREV to bring fixes using the proper entry
addresses for ARM architectures [1], as well as fixing a race condition
in the Makefile during assembly [2].
Fix url in case automatic redirects stop working.
[1]
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/classes-recipe/testimage.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-recipe/testimage.bbclass
b/meta/classes-recipe/testimage.bbclass
index 5cc408b0c4..df22bb2344 100644
---
ibgcrypt = "Hongxu Jia "
RECIPE_MAINTAINER:pn-libgfortran = "Khem Raj "
RECIPE_MAINTAINER:pn-libgit2 = "Unassigned "
-RECIPE_MAINTAINER:pn-libgloss = "Alejandro Hernandez "
+RECIPE_MAINTAINER:pn-libgloss = "Alejandro Hernandez "
RECIPE_MAINTAINER:pn-
Hey Khem,
On Sun, 15 Jan 2023 at 11:44, Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> meta/recipes-devtools/binutils/binutils.inc | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/meta/recipes-devtools/binutils/binutils.inc
>
d to go back and fish
>out the previous patches. This is error prone and time consuming.
>
> Thanks!
>
> On 11/01/2023 21:34:44-0700, Alejandro Hernandez Samaniego wrote:
> > Signed-off-by: Alejandro Enedino Hernandez Samaniego <
> alejan...@enedino.org>
&g
ude/maintainers.inc
@@ -54,6 +54,7 @@ RECIPE_MAINTAINER:pn-automake = "Robert Yang
"
RECIPE_MAINTAINER:pn-avahi = "Yi Zhao "
RECIPE_MAINTAINER:pn-babeltrace = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-babeltrace2 = "Alexander Kanavin "
+RECIPE_MAINTAINER:pn-
ntry to meta/conf/distro/include/maintainers.inc file.
> baremetal-helloworld
> (/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/recipes-extended/baremetal-example/
> baremetal-helloworld_git.bb)
>
> please run oe-selftest before submitting
>
>
> On 08/01/2023 12
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/lib/oeqa/selftest/cases/baremetal.py | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 meta/lib/oeqa/selftest/cases/baremetal.py
diff --git a/meta/lib/oeqa/selftest/cases/baremetal.py
My apologies, last minute typo on this one, sending v2
Alejandro
On Sun, 8 Jan 2023 at 12:15, Alejandro Hernandez Samaniego via
lists.openembedded.org wrote:
> Signed-off-by: Alejandro Enedino Hernandez Samaniego <
> alejan...@enedino.org>
> ---
> meta/lib/oeqa/selftest/
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/lib/oeqa/selftest/cases/baremetal.py | 13 +
1 file changed, 13 insertions(+)
create mode 100644 meta/lib/oeqa/selftest/cases/baremetal.py
diff --git a/meta/lib/oeqa/selftest/cases/baremetal.py
- The qemux86 port for helloworld-baremetal builds in the standard way, however,
it uses NASM syntax for the startup code, hence we include a dependency to
nasm-native, QEMU forces us to use an ELF file rather than a bin file to boot
from this architecture using the -kernel parameter.
-
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
.../baremetal-example}/baremetal-helloworld_git.bb| 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename {meta-skeleton/recipes-baremetal/baremetal-examples =>
with this, the build-std
feature
builds the std library as part of the crate compilation process, this way
you end up with a newly built corresponding std library.
On Mon, Dec 19, 2022, 4:24 AM Alex Kiernan wrote:
> On Sat, Dec 17, 2022 at 4:21 PM Alejandro Hernandez Samaniego
> wrote:
> &
From: Alejandro Hernandez Samaniego
Rust follows the train release model via the stable, beta and nightly channels,
by default we build rust from the stable channel, however there are certain
features which are only available in the beta or nightly channels.
Make these channels available
On Sat, Dec 17, 2022, 2:56 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2022-12-16 at 18:21 -0700, Alejandro Hernandez Samaniego wrote:
> > From: Alejandro Hernandez Samaniego
> >
> > Rust follows the train release model via the stable,
From: Alejandro Hernandez Samaniego
Rust follows the train release model via the stable, beta and nightly channels,
by default we build rust from the stable channel, however there are certain
features which are only available in the beta or nightly channels.
Make these channels available
On Thu, 15 Dec 2022 at 22:33, Alex Kiernan wrote:
> On Thu, Dec 15, 2022 at 9:45 PM Alejandro Enedino Hernandez Samaniego
> wrote:
> >
> >
> >
> > On Thu, Dec 15, 2022, 3:36 PM Alex Kiernan
> wrote:
> >>
> >> On Thu, Dec 15, 2022 at 6:24 PM Alejandro Enedino Hernandez Samaniego
> >> wrote:
>
On Thu, Dec 15, 2022, 3:36 PM Alex Kiernan wrote:
> On Thu, Dec 15, 2022 at 6:24 PM Alejandro Enedino Hernandez Samaniego
> wrote:
> >
> >
> >
> > On Thu, 15 Dec 2022 at 11:11, Alejandro Enedino Hernandez Samaniego <
> alejan...@enedino.org> wrote:
> >>
> >>
> >> On Thu, 15 Dec 2022 at 11:03,
On Thu, 15 Dec 2022 at 11:11, Alejandro Enedino Hernandez Samaniego <
alejan...@enedino.org> wrote:
>
> On Thu, 15 Dec 2022 at 11:03, Alexander Kanavin
> wrote:
>
>> On Thu, 15 Dec 2022 at 19:01, Alexander Kanavin via
>> lists.openembedded.org
>> wrote:
>> > Ok, I think what we should do first
On Thu, 15 Dec 2022 at 11:03, Alexander Kanavin
wrote:
> On Thu, 15 Dec 2022 at 19:01, Alexander Kanavin via
> lists.openembedded.org
> wrote:
> > Ok, I think what we should do first is to actually drop the version
> > from all of the .bb file names, and set it once, inside some .inc, and
> >
On Thu, 15 Dec 2022 at 09:08, Alex Kiernan wrote:
> On Thu, Dec 15, 2022 at 3:38 PM Alejandro Hernandez Samaniego
> wrote:
> >
> >
> >
> > On Thu, Dec 15, 2022, 3:05 AM Alexander Kanavin
> wrote:
> >>
> >> On Thu, 15 Dec 2022
On Thu, Dec 15, 2022, 3:05 AM Alexander Kanavin
wrote:
> On Thu, 15 Dec 2022 at 08:32, Alejandro Hernandez Samaniego
> wrote:
> > +RUST_VERSION = "1.65.0"
> > +SRC_URI += "
> https://static.rust-lang.org/dist/rustc-${RUST_VERSION}-src.tar.xz;name=rust
> &q
From: Alejandro Hernandez Samaniego
Rust follows the train release model via the stable, beta and nightly channels,
by default we build rust from the stable channel, however there are certain
features which are only available in the beta or nightly channels.
Make these channels available
Allow rust to build for baremetal targets by generating the proper target
triple, follow the format specified by rusts Triple [1], that is:
---
This is done automatically based on both TARGET_OS and TCLIBC.
For example, a riscv64 baremetal target triple would look like this:
Since qemuboot is part of IMAGE_CLASSES via qemu.inc it is being
inherited before we set the QB_FOO variables.
Since our variables have conditional definitions and at that point
they've already been defined by qemuboot, we can no longer define
them in our class.
Move the IMAGE_CLASSES inherit to
Theres not a rootfs for baremetal images, hence we should avoid
trying to list rootfs packages for them.
This fixes an issue where some classes (e.g. license_image) rely on
rootfs functionality when included for baremetal images even if its
nonexistent
Signed-off-by: Alejandro Enedino Hernandez
On Fri, Sep 2, 2022, 9:47 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2022-09-01 at 17:42 -0600, Alejandro Hernandez Samaniego wrote:
> > There could be IMAGE_CLASSES designed to work on images which arent
> > necessarily compatible with baremeta
There could be IMAGE_CLASSES designed to work on images which arent
necessarily compatible with baremetal-images, one example is the
license_image class which relies on the package managers functionality
during do_rootfs, for baremetal images no rootfs is created hence the
package manager shouldnt
.
Alejandro
On Tue, Aug 23, 2022, 4:13 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2022-08-23 at 15:31 -0600, Alejandro Hernandez Samaniego wrote:
> > The new classes scope implemented on commit 7bd328f9d
> > made testimage.bbclass (and perhaps
The new classes scope implemented on commit 7bd328f9d
made testimage.bbclass (and perhaps others) stop working
for baremetal-images, the expected way to run testimage
is no longer to use INHERIT but to use IMAGE_CLASSES
instead, however this functionality was not implemented in the
baremetal-image
Previous commit c725bdb29b266 broke kernel source handling, this was due
to the code expecting the sources to be in a different directory, this did
not happen when using externalsrc since sources were found in the expected
directories.
Pass work-shared to the check to allow sources to be found in
On 7/10/22 10:42, Otavio Salvador wrote:
We need full target passed for build so we changed the
rust-cross-canadian to use same code used in regular rust recipes and
added support to use specific llvm-target for the building host.
Fixes: ef566af964 ("rust: fix issue building cross-canadian
On 7/12/22 06:31, Bruce Ashfield wrote:
On Tue, Jul 12, 2022 at 6:44 AM Richard Purdie
wrote:
On Mon, 2022-07-11 at 00:06 -0300, Bruce Ashfield wrote:
On Sun, Jul 10, 2022 at 11:27 PM Bruce Ashfield via
lists.openembedded.org
wrote:
On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
While executing do_package, bitbake checks for a list of
debug source files and uses a pattern to match the ones
to be included in copydebugsources.
Previously when externalsrc was in use either directly or by
using devtool, the source location changed and this pattern
no longer matched, hence
Hello everyone,
There have been a number of failures in the autobuilder today [1] [2] due
to the change currently sitting in master-next that switches
LAYERSERIES_COMPAT from honister to kirkstone[3].
Since the change will soon be merged into master I thought it'd be a good
idea to send an email
Hello,
This is causing a do_fetch failure in the autobuilder for go-binary-native:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3231
Cheers,
Alejandro
On 2/14/22 14:27, wangmy wrote:
Signed-off-by: Wang Mingyu
---
meta/recipes-devtools/go/{go-1.17.6.inc =>
Thanks for catching this Ross
Alejandro
On 2/8/22 11:56, Ross Burton wrote:
COPYING.LIBGLOSS simply had the FSF street address change.
COPYING.NEWLIB now includes BSD-3-Clause.
Signed-off-by: Ross Burton
---
meta/recipes-core/newlib/newlib.inc | 6 +++---
1 file changed, 3 insertions(+),
On 2/2/22 08:15, Vyacheslav Yurkov wrote:
Hi Alejandro
On 02.02.2022 07:58, Alejandro Hernandez wrote:
Hey Vyacheslav,
...I definitely tried extending the overlay-etc class but it simply
does not work for this, since the rootfs becomes inaccessible once
the system has booted
to initramfs-framework?
Cheers,
Vyacheslav
On 29.01.2022 20:48, Alejandro Hernandez Samaniego wrote:
When installed, this module mounts a read-write (RW) overlay on
top of a root filesystem, which is kept read-only (RO), free
from modifications by the user, this might prove to be useful
if we want
When installed, this module mounts a read-write (RW) overlay on
top of a root filesystem, which is kept read-only (RO), free
from modifications by the user, this might prove to be useful
if we want to access or restore the original unmodified rootfs.
The existing overlay-etc.bbclass does
On Fri, 28 Jan 2022 at 02:10, Khem Raj wrote:
> On Thu, Jan 27, 2022 at 5:40 PM Alejandro Hernandez Samaniego
> wrote:
> >
> > Signed-off-by: Alejandro Enedino Hernandez Samaniego <
> alejan...@enedino.org>
> > ---
> > .../newlib/{libgloss_4.1.0.bb =>
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
.../newlib/{libgloss_4.1.0.bb => libgloss_4.2.0.bb} | 0
meta/recipes-core/newlib/newlib.inc | 12 +---
.../newlib/{newlib_4.1.0.bb => newlib_4.2.0.bb} | 0
3 files changed, 9 insertions(+), 3 deletions(-)
On 1/26/22 7:11 AM, Bruce Ashfield wrote:
On Wed, Jan 26, 2022 at 2:22 AM Alejandro Hernandez Samaniego
wrote:
When installed, this module mounts a read-write (RW) overlay on
top of a root filesystem, which is kept read-only (RO).
It needs to be executed after the initramfs-module-rootfs
When installed, this module mounts a read-write (RW) overlay on
top of a root filesystem, which is kept read-only (RO).
It needs to be executed after the initramfs-module-rootfs since
it relies on it to mount the filesystem at initramfs startup but
before the finish module which normally switches
There may be a case where we want to build an initramfs image
that doesnt inherit the same DISTRO_FEATURES (or others) from
the main image being built.
For example we may want our initramfs not to inherit a certain
conf or feature, say we want to use musl for a smaller footprint,
but if we are
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
meta/recipes-core/images/core-image-tiny-initramfs.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/images/core-image-tiny-initramfs.bb
b/meta/recipes-core/images/core-image-tiny-initramfs.bb
index
On Tue, 11 Jan 2022 at 00:55, Khem Raj wrote:
> On Mon, Jan 10, 2022 at 6:50 PM Alejandro Hernandez Samaniego
> wrote:
> >
> > While building GCC it checks whether the include directory exists,
> > if it doesnt it throws an error and exits:
> >
> > | The
While building GCC it checks whether the include directory exists,
if it doesnt it throws an error and exits:
| The directory that should contain system headers does not exist:
| tmp/work/x86_64-nativesdk-pokysdk-linux/gcc-cross-canadian-riscv32/
11.2.0-r0/recipe-sysroot/usr/include/
|
SDK recipes now require a provider for /bin/sh, this
should come from nativesdk-sdk-provides-dummy which
is added by default to Linux SDKs, however tclibc-baremetal
requires us to explicitly add its new dependency to
TOOLCHAIN_HOST_TASK, otherwise we get a packaging error
while generating an SDK.
SDK recipe now require a provider for /bin/sh, this
should come from nativesdk-sdk-provides-dummy which
is added by default to Linux SDKs, however tclibc-newlib
requires us to explicitly add its new dependency to
TOOLCHAIN_HOST_TASK, otherwise we get a packaging error
while generating an SDK.
Commit 282d596b8 added a fix for image.bbclass related to QEMU
dependencies, such fix made the older logic borrowed from
image.bbclass incompatible.
Update the dependency logic to reflect new changes, we no longer
need to add the do_addto_recipe_sysroot dependency specifically.
Signed-off-by:
$ runqemu nographic
runqemu - INFO - Running bitbake -e ...
KERNEL:
[tmp/deploy/images/qemuriscv32/baremetal-helloworld-image-qemuriscv32.bin]
MACHINE: [qemuriscv32]
runqemu - INFO - Running
tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-riscv32
Hello
On 6/1/21 9:09 AM, Trevor Gamblin wrote:
Backport and modify the patch for CVE-2021-22890 from curl 7.76 to make
it apply cleanly on 7.75.
CVE: CVE-2021-22890
Signed-off-by: Trevor Gamblin
---
...-argument-to-Curl_ssl_get-addsession.patch | 517 ++
On 5/31/21 11:24 PM, zangrc wrote:
From: Wang Mingyu
0001-add-support-for-ipkg-to-debuginfod.cxx.patch
Removed since this is included in 0.185.
Refresh the following patch:
0001-debuginfod-debuginfod-client.c-correct-string-format.patch
0015-config-eu.am-do-not-use-Werror.patch
, May 27, 2021 at 7:16 AM Alejandro Hernandez Samaniego
wrote:
From: Khem Raj
gcc needs -mmusl option to be passed in SDK since we ship crossdk compiler
configured for glibc by default, this helps in creating correct
compiler defaults for musl based SDK compilers
[YOCTO #13459]
(From OE-Core rev
From: Khem Raj
gcc needs -mmusl option to be passed in SDK since we ship crossdk compiler
configured for glibc by default, this helps in creating correct
compiler defaults for musl based SDK compilers
[YOCTO #13459]
(From OE-Core rev: e6fbac7aeabe00d8fb734992012dd629a8527b25)
Signed-off-by:
Please discard this patch, this was meant to be for dunfell, its missing
the tag due to a typo
Alejandro
On 5/27/21 11:02 AM, Alejandro Hernandez Samaniego wrote:
From: Khem Raj
gcc needs -mmusl option to be passed in SDK since we ship crossdk compiler
configured for glibc by default
Woestenberg
Signed-off-by: Richard Purdie
Signed-off-by: Khem Raj
Signed-off-by: Alejandro Hernandez Samaniego
---
.../gcc/gcc-cross-canadian.inc| 23 +++
1 file changed, 23 insertions(+)
diff --git a/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
b/meta/recipes
When running:
execute_pre_post_process(d, d.getVar(ROOTFS_POSTPROCESS_COMMAND))
rootfs_update_timestamp is run, which assumes that rootfs/${sysconfdir}
is already created (usually done through the do_rootfs task on linux).
This causes the build to fail if ${sysconfdir} does not exist.
This may
On Mon, May 10, 2021, 11:59 PM Alistair Francis
wrote:
> On Tue, May 11, 2021 at 3:31 PM Alejandro Hernandez Samaniego
> wrote:
> >
> > Add support for MACHINE=qemuriscv64.
> >
> > $ runqemu nographic
> >
> > KERNEL:
> [tmp/deploy/images/qemuriscv
Add support for MACHINE=qemuriscv64.
$ runqemu nographic
KERNEL:
[tmp/deploy/images/qemuriscv64/baremetal-helloworld-image-qemuriscv64.bin]
MACHINE: [qemuriscv64]
FSTYPE: [bin]
runqemu - INFO - Running
On Sun, May 9, 2021, 7:25 PM Alistair Francis wrote:
> On Sat, May 8, 2021 at 6:30 PM Alejandro Hernandez Samaniego
> wrote:
> >
> > Add support for MACHINE=qemuriscv64.
> >
> > $ runqemu nographic
> >
> > BIOS:
> [tmp/deploy/images/qemuriscv
On Sat, 8 May 2021 at 09:16, Khem Raj wrote:
> On Sat, May 8, 2021 at 1:30 AM Alejandro Hernandez Samaniego
> wrote:
> >
> > Add support for MACHINE=qemuriscv64.
> >
> > $ runqemu nographic
> >
> > BIOS:
> [tmp/deploy/images/qemuriscv64/baremetal-
Add support for MACHINE=qemuriscv64.
$ runqemu nographic
BIOS: [tmp/deploy/images/qemuriscv64/baremetal-helloworld-image-qemuriscv64.elf]
MACHINE: [qemuriscv64]
runqemu - INFO - Running
tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-riscv64
Hello
From: Konrad Weihmann
Recently an entry in the NVD DB appeared that looks like that
{'vulnerable': True, 'cpe_name': []}.
As besides all the vulnerable flag no data is present we would get
a KeyError exception on acccess.
Use get method on dictionary and return if no meta data is present
Also
Hey Konrad,
Seems to work on my side as well, it applies cleanly for dunfell as
well, I will send it again so it gets backported since that also broken.
Cheers,
Alejandro
Tested-by: Alejandro Hernandez
On 4/22/21 11:12 AM, Ralph Siemsen wrote:
On Thu, Apr 22, 2021 at 06:48:27PM +0200
From: Alejandro Enedino Hernandez Samaniego
The imp module has een deprecated by upstream python, drop its usage
(imp.get_tag) in favor of sys.implementation.cache_tag.
Avoid incorrectly getting dependencies for running script and
multiprocessing module.
Improve logging behavior of the
+++
b/meta/recipes-devtools/python/python3/0001-test_locale.py-correct-the-test-output-format.patch
@@ -23,24 +23,24 @@ Before this patch:
Upstream-Status: Submitted [https://github.com/python/cpython/pull/15132]
+
+Rebased for 3.9.4, still not accepted upstream Signed-off-by: Alejandro
Her
1 - 100 of 419 matches
Mail list logo
