I would like to understand why this patch series was never merged.
Specifically, the patch that moves CMAKE_NO_SYSTEM_FROM_IMPORTED to
toolchain.cmake seems to fix a common issue when building with OE: By default,
CMake adds the SYSTEM property to all imported libraries, which lets consuming
ta
r/lib/perl5/site_perl/5.30.1
/usr/lib/perl5/vendor_perl/5.30.1/aarch64-linux
/usr/lib/perl5/vendor_perl/5.30.1
/usr/lib/perl5/5.30.1/aarch64-linux
/usr/lib/perl5/5.30.1 .) at /usr/bin/dpkg-architecture line 25.
Cc: Richard Purdie
Signed-off-by: Manuel Leonhardt
---
meta/recipes-devtools
.
Signed-off-by: Manuel Leonhardt
Cc: Richard Purdie
---
meta/classes/sstate.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 6e4eb09f8e..8182010047 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes
On Mon, Nov 1, 2021 at 12:19 PM, Richard Purdie wrote:
>
> On Mon, 2021-11-01 at 04:09 -0700, Manuel Leonhardt wrote:
>
>> On Mon, Nov 1, 2021 at 11:52 AM, Richard Purdie wrote:
>>
>>> On Mon, 2021-11-01 at 03:47 -0700, Manuel Leonhardt wrote:
>&g
On Mon, Nov 1, 2021 at 11:52 AM, Richard Purdie wrote:
>
> On Mon, 2021-11-01 at 03:47 -0700, Manuel Leonhardt wrote:
>
>> I submitted a patch to fix bb.utils.lockfile to at least break the loop
>> and
>> fail
>> when a too long filename is passed with
&g
I submitted a patch to fix bb.utils.lockfile to at least break the loop and
fail when a too long filename is passed with
https://lists.openembedded.org/g/bitbake-devel/message/12850
Nevertheless, you have a good point here: Fixing the code that constructs the
filename of the lock files would be
See also https://lists.openembedded.org/g/bitbake-devel/topic/86724965 , where
bb.utils.lockfile is fixed to raise when the filename of a lockfile is too long.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157692):
https://lists.openembedded.org/
roperly
in bb.utils.lockfile, this caused populate tasks to hang indefinitely.
Also, previously when generating a shorter filename, the reserved
characters for .siginfo and now .lock were not considered. This is now
fixed by using limit instead of 254, which is the maximum length.
Signed-off-by: Manuel
