From: Mark Hatle
While debugsrc is almost always a file (or link), there are apparently
cases where a directory could be returned from the dwarfsrcfiles
processing. When this happens, the hashing fails and an error results
when building the SPDX documents.
Signed-off-by: Mark Hatle
Signed-off
From: Khem Raj
Signed-off-by: Khem Raj
Cc: Mark Hatle
Signed-off-by: Richard Purdie
Backport from master OE-Core rev: f0eac82b9a1e4549b7d918df768c369ed7ab5183
Signed-off-by: Mark Hatle
---
...fine-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch | 6 +++---
1 file changed, 3 insertions
s well.
This patch understandably doesn't cherry-pick to the earlier versions
of gcc in kirkstone and scarthgap.
If someone would like to prepare branch appropriate versions I'd be
happy to add them to my test queues.
Thanks,
Steve
On Tue, Sep 3, 2024 at 10:25 PM Khem Raj wrote:
Sig
From: Mark Hatle
Fix:
NameError: name 'shutil' is not defined
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
Signed-off-by: Richard Purdie
(cherry picked from commit 13bdd750ae54d57a5f459e4b7d8636c864978241)
Signed-off-by: Mark Hatle
---
meta/lib/oe/package.py | 1 +
1 fi
From: Richard Purdie
Update to a new revision which includes "Bugfix for Linux open(O_CREAT|O_EXCL)"
Signed-off-by: Richard Purdie
(cherry picked from commit 92a9710ec88c8729fa3d83baa2e63dd74d95cdf8)
Signed-off-by: Mark Hatle
---
meta/recipes-devtools/pseudo/pseudo_git.bb | 2
From: Mark Hatle
When a create-spdx-* classes is processing documents, it needs to
find the document in a path that is related to the SSTATE_ARCH
when a packge is generated. The SSTATE_ARCH can be affected by
multilib configurations, resulting is something like armv8a-mlib.
When the image (or
)
Signed-off-by: Mark Hatle
---
meta/recipes-devtools/pseudo/files/glibc238.patch | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/pseudo/files/glibc238.patch
b/meta/recipes-devtools/pseudo/files/glibc238.patch
index da4b8ca..dfb5c28 100644
--- a
From: Mark Hatle
When PACKAGE_STRIP_STATIC is enabled the system did not pay attention to
hardlinks. This could trigger a race condition during stripping of static
libraries where multiple strips (through hardlinks) could run at the same
time triggering a truncated or modified file error.
The
From: Mark Hatle
Additional test cases for debug symlink generation both binaries
and static libraries.
This also has the side effect of testing for race conditions in the
hardlink debug generation and stripping.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
Signed-off-by: Richard
From: Mark Hatle
Newlib generally requires additional components to function. Skip the
cases where newlib is known to not work.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
Signed-off-by: Richard Purdie
(cherry picked from commit b993474e40d9980b90c3d541f4c702203561)
Signed-off
ions so disable the class
there as
a deferred inherit would overwrite it.
Signed-off-by: Richard Purdie
(cherry picked from commit 662396533177b72cc1d83e95841b27f7e42dcb20)
Eliminate spdx-3.0 items, not applicable to Scarthgap.
Signed-off-by: Mark Hatle
---
meta/classes-recipe/populate_sdk_b
From: Mark Hatle
Newlib generally requires additional components to function. Skip the
cases where newlib is known to not work.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
I'm not entirely sure the patch is right, but it provides a mechanism to
exclude specific TCLIBCs
From: Mark Hatle
When a create-spdx-* classes is processing documents, it needs to
find the document in a path that is related to the SSTATE_ARCH
when a packge is generated. The SSTATE_ARCH can be affected by
multilib configurations, resulting is something like armv8a-mlib.
When the image (or
From: Mark Hatle
This resolves problems when building an SDK that includes multilibs.
It also adds the isfile change that was previou put in for spdx 2.2.
Introduce a new multilib SSTATE_ARCHs, as an optimization this just
defaults to SSTATE_ARCHs in most cases. If building an SDK we do
expand
From: Mark Hatle
Same change as previously made to the create-spdx-2.2.bbclass,
while debugsrc is almost always a file (or link), there are apparently
cases where a directory could be returned from the dwarfsrcfiles
processing. When this happens, the hashing fails and an error results
when
I'm requesting the following changes be backported to scarthgap. The commits
should apply directly. Any questions, let me know.
commit def276f0c4c43fa4b95b7b38a944de7cc7e9286f
Author: Mark Hatle
Date: Fri Jul 19 13:58:16 2024 -0500
package.py: Fix static debuginfo split
aries SHOULD happen though!
v2:
The first three patches were combined into a single patch originally.
This has been split apart to make it more clear the three individual changes.
Mark Hatle (3):
package.py: Fix static debuginfo split
package.py: Fix static library processing
selftest-har
From: Mark Hatle
Additional test cases for debug symlink generation both binaries
and static libraries.
This also has the side effect of testing for race conditions in the
hardlink debug generation and stripping.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
.../selftest-hardlink
From: Mark Hatle
When PACKAGE_STRIP_STATIC is enabled the system did not pay attention to
hardlinks. This could trigger a race condition during stripping of static
libraries where multiple strips (through hardlinks) could run at the same
time triggering a truncated or modified file error.
The
From: Mark Hatle
Fix:
NameError: name 'shutil' is not defined
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/lib/oe/package.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oe/package.py b/meta/lib/oe/package.py
index e6b46a0..235f2d6 100644
--- a/m
Fixes and test case for static-library related items.
v2:
The first three patches were combined into a single patch originally.
This has been split apart to make it more clear the three individual changes.
Mark Hatle (4):
package.py: Fix static debuginfo split
package.py: Fix inode link
From: Mark Hatle
Additional test cases for debug symlink generation both binaries
and static libraries.
This also has the side effect of testing for race conditions in the
hardlink debug generation and stripping.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
.../selftest-hardlink
From: Mark Hatle
When PACKAGE_STRIP_STATIC is enabled the system did not pay attention to
hardlinks. This could trigger a race condition during stripping of static
libraries where multiple strips (through hardlinks) could run at the same
time triggering a truncated or modified file error.
The
From: Mark Hatle
The process_split_and_strip_files attempts to reconstruct hardlinks
through the .debug directory components. Unfortunately there was an error
in the 'dest' calculation that cause the SRC and DEST to be the same when
they both exist in the same path. This did not
From: Mark Hatle
Fix:
NameError: name 'shutil' is not defined
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/lib/oe/package.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oe/package.py b/meta/lib/oe/package.py
index e6b46a0..8a64e13 100644
--- a/m
From: Mark Hatle
When PACKAGE_DEBUG_STATIC_SPLIT is enabled, the copy frunction fails since
shutil was not availble in this python module. Fix this with an import.
When PACKAGE_STRIP_STATIC is enabled the system did not pay attention to
hardlinks. This could trigger a race condition during
From: Mark Hatle
Additional test cases for debug symlink generation both binaries
and static libraries.
This also has the side effect of testing for race conditions in the
hardlink debug generation and stripping.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
.../selftest-hardlink
h64-tc
arm-rm-tc
microblaze-tc
riscv-tc
(aarch64-tc has by far the fewest multilibs so is the fastest to parse and
build.)
Any questions, let me know!
(Also these changes were made available to
https://git.yoctoproject.org/poky-contrib mgh/spdx-fixes)
Mark Hatle (2):
create-sdpx-2.2.b
From: Mark Hatle
While debugsrc is almost always a file (or link), there are apparently
cases where a directory could be returned from the dwarfsrcfiles
processing. When this happens, the hashing fails and an error results
when building the SPDX documents.
Signed-off-by: Mark Hatle
Signed-off
From: Mark Hatle
When create-spdx-2.2 class is processing documents, it needs to
find the document in a path that is related to the SSTATE_ARCH
when a packge is generated. The SSTATE_ARCH can be affected by
multilib configurations, resulting is something like armv8a-mlib.
When the image (or
On 7/4/24 2:09 AM, Adrian Freihofer wrote:
From: Adrian Freihofer
Make the fitimage_assemble function usable with absolute paths for the
generated its and the fitImage file.
Later on this will allow to take the linux.bin and the DTB files from
the sstated deploy derectory and write the gener
On 7/4/24 2:09 AM, Adrian Freihofer wrote:
From: Adrian Freihofer
If EXTERNAL_KERNEL_DEVICETREE and dtb_image_sect are empty variables
dtb_path ends up as "/" which is available on most Unix systems but
probably not the dtb_path which is needed here. Checking for a file
makes more sense and a
On 6/18/24 9:21 AM, Andrew Murray wrote:
Hi Marta,
On Tue, 18 Jun 2024 at 14:55, Marta Rybczynska via
lists.yoctoproject.org
wrote:
Hello all,
During the cve-check work, the cve-extra-exclusion.inc file is causing
difficulties. It is a global place for all CVEs, without linking them to the
I reviewed the RFC. It looks good to me. I had one minor comment on the 2/3 of
patch.
Reviewed-by: Mark Hatle
On 5/31/24 9:06 AM, Marta Rybczynska wrote:
Hello,
We have been working on the standalone version of the cve-check that can run
over an SBOM (SPDX+VEX-like information) since
On 5/31/24 8:01 AM, Marta Rybczynska wrote:
The "vex" class generates the minimum information that is necessary
by an external CVE checking tool. It is a drop-in replacement of "cve-check".
It uses the same variables from recipes.
It generates the JSON output format only.
Signed-off-by: Marta
PM, Mark Hatle via lists.openembedded.org wrote:
Fix for insufficient argument checking in Secure state Entry functions
in software using Cortex-M Security Extensions (CMSE), that has been
compiled using toolchains that implement 'Arm v8-M Security Extensions
Requirements on Development
From: Mark Hatle
Code backported from binutils development tree.
aarch64: Remove asserts from operand qualifier decoders [PR31595]
Given that the disassembler should never abort when decoding
(potentially random) data, assertion statements in the
`get_*reg_qualifier_from_value
From: "Mark Hatle via lists.openembedded.org"
Code backported from binutils development tree.
aarch64: Remove asserts from operand qualifier decoders [PR31595]
Given that the disassembler should never abort when decoding
(potentially random) data, assertion statements in t
in master.
--Mark
Thanks,
Steve
On Fri, May 24, 2024 at 1:12 PM Mark Hatle via lists.openembedded.org
wrote:
Code backported from binutils development tree.
aarch64: Remove asserts from operand qualifier decoders [PR31595]
Given that the disassembler should never abort when decoding
(p
prove problematic.
...
Signed-off-by: Mark Hatle
---
.../binutils/binutils-2.42.inc| 1 +
...sserts-from-operand-qualifier-decode.patch | 382 ++
2 files changed, 383 insertions(+)
create mode 100644
meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-as
er to pass values to Secure state that are out of range for types
smaller than 32-bits. Out of range values might lead to incorrect
operations in secure state.
Signed-off-by: Mark Hatle
---
meta/recipes-devtools/gcc/gcc-13.2.inc| 1 +
.../gcc/gcc/CVE-2024-0151.patch
rt of test cases to show it works or doesn't. It does
not break any of my existing test cases related to Linux for cortex-r
baremetal.
Again this change has already been accepted to newer versions of GCC.
Mark Hatle (2):
binutils: Fix aarch64 disassembly abort
gcc: Fix for CVE-2024-0151
.
Signed-off-by: Mark Hatle
---
I found this issue on scarthgap, but I've seen similar symptoms back to
langdale.
Most likely it's an issue back to kirkstone, but clearly rare outside of a
specific workdlow with tinfoil vs command line bitbake!
meta/classes-global/sstate.bbclass | 2
I know this request is a week or so old..
But do NOT upgrade to 'xz' 5.6.0 or 5.6.1. It has been compromised:
https://www.openwall.com/lists/oss-security/2024/03/29/4
--Mark
On 3/14/24 8:40 AM, Richard Purdie wrote:
On Wed, 2024-03-13 at 15:08 +0800, wangmy via lists.openembedded.org
wrote:
Will this work in the case of a system boot? I know if we load the kernel
directly to memory and boot, we can pass kernel command line through QEMU.
However many boards I have worked with in the past (and still do) do a system
level boot that starts with BIOS/Firmware, goes into a second stage
There are plenty of systems where we don't want package-management enabled by
default. This will just make core-image-full-cmdline less useful there.
In the past, it's always been up to the user to enable full package-management
in their configuration, default has been to not have it present.
On 2/21/24 9:06 AM, Paul Barker wrote:
On 21/02/2024 10:57, Ross Burton wrote:
From: Ross Burton
This is a new 64-bit "generic" Arm machine, that expects the hardware to
be SystemReady IR compatible. This is slightly forward-leaning as there's
not a _lot_ of SystemReady hardware in the wild,
Ubuntu 18.04 had 4.15 alright. Later point releases offered
much newer kernels. It’s also altogether EOL since end of may 2023.
Why should oe-core carry these? It’s RP’s call as qemu maintainer but my vote is
a firm no, unless additional arguments are put forward.
Alex
On Thu 25.
ools-tarball in your build will accomplish the same end result,
hides the problem but doesn't verify the mmap will actually work (or error) as
needed.
--Mark
Regards,
On Thu, Jan 25, 2024 at 10:04 PM Mark Hatle <mailto:mark.ha...@kernel.crashing.org>> wrote:
From: Mark Hatl
build for an older host, but
more importantly you can build an SDK that includes QEMU that will execute
on the 'SDK_OLDEST_KERNEL'. While I've not gone back and verified things
work on 3.2.0 system, I have verified that Ubuntu 18.04 is working for me.
(Ubuntu 18.04 is kernel 4.15)
From: Mark Hatle
Linux kernel 4.17 introduced two new mmap flags, MAP_FIXED_NOREPLACE and
MAP_SHARED_VALIDATE. Starting with QEMU 8.1, these flags are now used
and required for proper system operation. In order to build and run on a
system older then 4.17, we need to emulate this new behavior
On 1/15/24 7:50 AM, Jasper Orschulko via lists.openembedded.org wrote:
Hi Alex,
Okay, I've read the README file in that repo, and if i understood it
right, the process is:
- run fossology
- have a human inspect the output, and correct it on a file by file
basis (tremendous waste of time and l
On 12/11/23 2:35 PM, Ross Burton wrote:
On 11 Dec 2023, at 17:35, Richard Purdie via lists.openembedded.org
wrote:
Currently, pseudo tracks all files referenced within it's presence unless
they're listed in an exclusion list. The exclusion list has grown to be
fairly unwieldy.
This patch s
On 11/5/23 1:43 PM, Adrian Freihofer wrote:
On Sat, 2023-11-04 at 11:09 +, Richard Purdie wrote:
On Sat, 2023-11-04 at 11:29 +0100, adrian.freiho...@gmail.com wrote:
Hi Alex, hi Richard
After some internal discussions, I would like to clarify my
previous
answers on this topic.
* Usual
I wanted to confirm, this did fix the problem for me. Thanks!
On 10/16/23 10:54 AM, Yoann Congal wrote:
Le lun. 16 oct. 2023 à 17:37, Mark Hatle
a écrit :
On 10/16/23 7:17 AM, Yoann Congal wrote:
Hi Mark,
Le lun. 16 oct. 2023 à 02:40, Mark Hatle via lists.openembedded.org
a écrit
On 10/16/23 7:17 AM, Yoann Congal wrote:
Hi Mark,
Le lun. 16 oct. 2023 à 02:40, Mark Hatle via lists.openembedded.org
a écrit :
Running a number of builds recently, a small number of them failed. Note we
ran about 20 builds and only 3 failed like this, the others completed. I&#
Running a number of builds recently, a small number of them failed. Note we
ran about 20 builds and only 3 failed like this, the others completed. I'm
wondering if maybe there is a race condition with the new code?
Error:
ERROR: depmodwrapper-cross-1.0-r0 do_patch: Error executing a python f
On 9/15/23 2:59 AM, Marta Rybczynska wrote:
On Wed, Sep 13, 2023 at 6:28 PM Mark Hatle
wrote:
* Visibility of the security work of the YP
There is much work on security in the YP, but it lacks visibility.
Is there a common nexus for this work? eg. do most of the folks who are
doing
On 9/13/23 11:00 AM, Alex Stewart wrote:
Thanks for driving this Marta. Internally and externally, it feels like
we're just on the cusp of everyone *suddenly caring* about our security
response strategy. So it's good to see that we're making moves in that
direction.
In general, this list looks
context resumed or exited during
breakpoint evaluation
Bug 581799 - when loads .debug_info section from dwarf 5 file, the content
of some part are zero
Updated examples/daytime/readme.txt
Signed-off-by: Mark Hatle
---
meta/recipes-devtools/tcf-agent/tcf-agent_git.bb | 4 ++--
1 file changed
From: Ross Burton
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
(cherry picked from commit c1841ab1e7b4e078cea77001e83e733764bb65ea)
Signed-off-by: Mark Hatle
---
meta/lib/oeqa/utils/qemurunner.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa
I know there won't be any more releases of langdale (as well as automatic
backports for security and other things.) However, I found a bug in the oeqa
qemurunner (fixed in Mickledore). Would you be willing to take the backport fix
(one line) or is the branch closed for further development?
T
ut how to pass configure options into the subports function call.
I'll continue to look into that, but it really shouldn't be necessary outside of
the YP use-case where we want one pseudo to run across a variety of hosts.)
--Mark
On 6/1/23 9:20 AM, Alexandre Belloni via lists.openembedd
t-1.0-r0: task do_install: Failed
ERROR: Task
(/home/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-1782300/meta-selftest/recipes-test/wrapper/cmdline-shebang-wrapper-test.bb:do_install)
failed with exit code '1'
On 30/05/2023 20:01:26-0700, Mark Hatle via lists.openembedd
On 5/30/23 10:18 PM, Seebs wrote:
On Tue, 30 May 2023 19:54:41 -0700
Mark Hatle wrote:
- int existed = (real___xstat64(_STAT_VER, path, &buf) != -1);
+ int existed = (base_stat64(path, &buf) != -1);
Honestly, with the benefit of hindsight, I actually can't eve
, but it's probably closer
to something that does what we need.
(There is still more duplication then I would like.. hopefully reviewers will be
able to suggest something.)
--Mark
On 5/30/23 10:01 PM, Mark Hatle via lists.openembedded.org wrote:
Changes to eliminate __*.c function usage
sired.
Signed-off-by: Mark Hatle
---
ports/linux/guts/fopen64.c | 4 +-
ports/linux/guts/freopen64.c | 4 +-
ports/linux/guts/fstat.c | 8 ++-
ports/linux/guts/fstat64.c | 14 +++-
ports/linux/guts/fstatat.c
I am working on changing the v4 into a more generic implementation based on
Seebs' and others comments. I'll likely be sending something to the list as an
RFC later today or tomorrow.
--Mark
On 5/30/23 11:43 AM, Seebs wrote:
On Tue, 30 May 2023 19:33:03 +0800
zhangjial...@loongson.cn wrote:
A little background, looking at oe-core and poky for background, I see the
initramfs images contain:
IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
I see this in both oe-core
meta/recipes-core/images/core-image-minimal-initramfs.bb and
core-image-tiny-initramfs.bb.
The "meta-security" layer also se
From: Mark Hatle
With a gcc older then 8.0, mesa-native will fail to build with the error:
sorry, unimplemented: non-trivial designated initializers not supported
According to https://docs.mesa3d.org/install.html?highlight=gcc+version#compile
the required minimum compiler version is now GCC
From: Mark Hatle
With a gcc older then 8.0, meta-native will fail to build with the error:
sorry, unimplemented: non-trivial designated initializers not supported
According to https://docs.mesa3d.org/install.html?highlight=gcc+version#compile
the required minimum compiler version is now GCC
u18, gcc version is 7.5.0.
Regards,
Qi
-Original Message-
From: openembedded-core@lists.openembedded.org
On Behalf Of Mark Hatle
Sent: Tuesday, April 4, 2023 10:25 AM
To: Patches and discussions about the oe-core layer
Subject: [OE-core] mesa-native fails on master
It's been
It's been a few weeks since I last built master, but starting with today's pull
I'm getting errors building mesa-native -- which pretty much kills the whole build.
I'm on an Ubuntu 18.04 host, and have the 'buildtools-tarball' from the last
4.1.3 loaded so I can get to the minimum version of py
From: Mark Hatle
While there has not been an official release in some time, the latest version
fixes a large number of bugs and adds support for Dwarf 5, among other
things. (Dwarf 5 is default in gcc 12 and newer.)
Short change log since the last version:
TCF Agent: Narrow down
On 12/16/22 9:45 AM, Alexander Kanavin wrote:
Disable slirp by default: qemu no longer carries libslirp in-tree,
and enabling slirp requires providing external libslirp first
(available from e.g. meta-virtualization).
I think disabling slirp (by default) is going to be problematic. Most of m
In the kernel is the jitter entropy system. It should work on all platforms
that have high res timers available. (This is the same mechanism that haveged
was using before as well. So no change in the RNG quality, just now built into
the kernel itself.)
The only place we've observed an issue
Ping, any comments on this?
On 11/21/22 1:20 PM, Mark Hatle wrote:
From: Mark Hatle
Some vendor versions of QEMU may be on older versions that do not have
qmp.legacy, but instead of qmp. Default to the integrated library
versions, fall back to the older one and then if neither is available
From: Mark Hatle
Some vendor versions of QEMU may be on older versions that do not have
qmp.legacy, but instead of qmp. Default to the integrated library
versions, fall back to the older one and then if neither is available
catch the exception and provide a more human readable error.
Signed
On 11/1/22 3:03 PM, Gundlupet Raju, Sandeep wrote:
Hello,
We wanted to know what the actual use case is for running weston as
weston user only in OE core
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-graphics/wayland/weston-init/weston.service#n44
How is this expected to b
.contains('PACKAGECONFIG', 'gbm', 'virtual/libgbm', '', d)} \
virtual/mesa \
"
While it might be possible to switch around the PROVIDES using distibution
configuration or similar, this has been difficult to get right in the past.
This is why the
x27;s: 'gl' is
basically 'opengl in x11' or 'opengl rendered to memory', and if a
system uses neither, then it is not needed.
Alex
On Wed, 26 Oct 2022 at 19:48, Joshua Watt wrote:
On Wed, Oct 26, 2022 at 12:21 PM Mark Hatle
wrote:
On 10/26/22 11:03 AM, Alexander
On 10/26/22 12:48 PM, Joshua Watt wrote:
On Wed, Oct 26, 2022 at 12:21 PM Mark Hatle
wrote:
On 10/26/22 11:03 AM, Alexander Kanavin wrote:
On Wed, 26 Oct 2022 at 16:35, Mark Hatle wrote:
(I just saw this, so a little late on the reply, but..)
mesa-gl is ABSOLUTELY still being used
On 10/26/22 11:03 AM, Alexander Kanavin wrote:
On Wed, 26 Oct 2022 at 16:35, Mark Hatle wrote:
(I just saw this, so a little late on the reply, but..)
mesa-gl is ABSOLUTELY still being used. It's needed for libmali usage. Not
everyone wants to use lima support for graphics.
It was b
On 10/19/22 5:35 AM, Alexander Kanavin wrote:
This also begs the question if mesa-gl is actually used by anyone, and
what warrants its continued inclusion in core as opposed to
product/BSP layers. I'll propose dropping the recipe and merging .inc
into mesa.bb once patches start flowing.
The or
Some versions of hashlib don't appear to implement the second FIPS
related argument. Detect this and support both versions.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
This was found on an internal Ubuntu 18.04 container. Unfortunately I
don't have access to the contai
Thank you, this worked perfectly.
On 9/17/22 1:20 AM, Markus Volk wrote:
--use-label
This should do it.
Am Fr, 16. Sep 2022 um 16:41:48 -0500 schrieb Mark Hatle
:
Is there a way to tell the _generated_ fstab to use labels to boot and not
hard coded partitions? If I remove the --ondisk
Is there a way to tell the _generated_ fstab to use labels to boot and not hard
coded partitions?
If I remove the --ondisk attribute from the wks file it defaults to
/dev/sda.
What I tried was:
part /boot --source bootimg-partition --fstype=vfat --label boot --active
--align 4 size 16
par
On 9/16/22 10:18 AM, Alberto Pianon wrote:
... trimmed ...
I also can see the issue with multiple sources in SRC_URI, although you
should be able to map those back if you assume subtrees are "owned" by
given SRC_URI entries. I suspect there may be a SPDX format limit in
documenting that piece
On 9/14/22 9:56 AM, Joshua Watt wrote:
On Wed, Sep 14, 2022 at 9:16 AM Marta Rybczynska wrote:
Dear all,
(cross-posting to oe-core and *-architecture)
In the last months, we have worked in Oniro on using the create-spdx
class for both IP compliance and security.
During this work, Alberto Pi
Wind River already has a mechanism to do something like this, called templates.
https://github.com/WindRiver-Labs/wr-template/tree/WRLINUX_10_21_BASE
Each template can have (optionally):
# README - template README file
# require - list of other templates required for this one
# template.c
On 8/29/22 6:59 PM, William A. Kennington III via lists.openembedded.org wrote:
This makes the determination of the timestamp for the /etc/timestamp
file consistent with mtimes in the generated image. This is desirable to
make the built image reproducible with the git commit date instead of
the
On 8/4/22 11:27 AM, Richard Purdie wrote:
On Thu, 2022-08-04 at 12:36 +0100, Khem Raj wrote:
On Thu, Aug 4, 2022 at 10:05 AM Richard Purdie
wrote:
Just to note that where we've been seeing pseudo hangs in rust, it
seems jemalloc calls obtain_malloc_conf() which calls readlink()
which
pseud
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/recipes-devtools/elfutils/elfutils_0.187.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-devtools/elfutils/elfutils_0.187.bb
b/meta/recipes-devtools/elfutils/elfutils_0.187.bb
index d03da61353..561112c580
When building with the previous a number of atomic functions come back as
undefined. Switching to linux-latomic fixes this.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/recipes-connectivity/openssl/openssl_3.0.5.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
ed by
microblaze systems currently. (Or at least Xilinx systems with the custom
qemu-xilinx.)
The other two are simple recipe updates.
Mark Hatle (4):
runqemu: Add missing space on default display option
default-distrovars: seccomp doesn't support microblaze
openssl: Move microblaze to lin
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
scripts/runqemu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index b4c1ae6d83..b6fc212ebe 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -1375,7 +1375,7 @@ class BaseConfig
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/conf/distro/include/default-distrovars.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/conf/distro/include/default-distrovars.inc
b/meta/conf/distro/include/default-distrovars.inc
index 9f4617be01..230bab84dd 100644
Note, it appears this bug is in honister as well.
On 3/6/22 3:08 PM, Jose Quaresma wrote:
When inside the threadedpool we make a copy of the localdata
to avoid some race condition, so we need to use this new
localdata2 and stop write the shared localdata.
Signed-off-by: Jose Quaresma
---
met
n a license has changed is permitted, as we're
not using it for file integrity.
Signed-off-by: Mark Hatle
Signed-off-by: Mark Hatle
---
meta/classes/insane.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbcl
already uses sha256 for file
integrity.)
In addition to this, it's possible that a recipe may attempt to use md5
during the build process. In oe-core, the only user is 'ovmf'. At this
time I don't intend to provide a fix for ovmf, but everything else in core
works properly
1 - 100 of 1868 matches
Mail list logo
