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:
Remove as commit b3afe7d redifines it.
https://git.openembedded.org/openembedded-core/commit/?id=b3afe7d9bd25a943e947de3ec064ea245173c5a8
Signed-off-by: Jose Quaresma
---
meta/classes/archiver.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/archiver.bbclass
The commit b8c5680 [1] add the funcion is_work_shared and at the same
time change from kernel-yocto.bbclass to a more generic kernel.bbclass.
This is also a fixup for the commit fed0ed8 [2] to avoid kernel rebuilds
because of the do_kernel_configme->do_unpack_and_patch task dependency.
[1]
This fix a race that happens when building some of the followning recipes
with kernel at same time.
The kernelsrc uses the kernel shared source dir as their source
S = "${STAGING_KERNEL_DIR}" and this will cause a race in the
do_unpack_and_patch task, when bitbake runs the
Set V=1 so that the compile log is useful when things go wrong.
Signed-off-by: Ross Burton
---
meta/recipes-extended/zstd/zstd_1.5.2.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-extended/zstd/zstd_1.5.2.bb
b/meta/recipes-extended/zstd/zstd_1.5.2.bb
index
This allows choosing padding algorithm when building fitImage. It may be
pkcs-1.5 or pss.
Signed-off-by: LUIS ENRIQUEZ
From: LUIS ENRIQUEZ
---
meta/classes/kernel-fitimage.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/classes/kernel-fitimage.bbclass
Historically there's been a split between /lib for early boot and
/usr/lib for everything else, but with modern systems this split is
meaningless and incomplete. If a minimal system for early boot is
needed, it should be a full minimal system in a initramfs.
Signed-off-by: Ross Burton
---
Modern gits print a big note if no branch name is specified when
creating a new repository. Silence this by explicitly naming the new
branch 'master' to match existing naming.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/selftest/context.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/selftest/cases/{git.py => intercept.py} | 0
On 22 Jul 2022, at 15:28, Khem Raj via lists.openembedded.org
wrote:
>
> On Fri, Jul 22, 2022 at 6:36 AM Bartosz Golaszewski wrote:
>>
>> 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 ?
>>>
>>
On Fri, Jul 22, 2022 at 10:31 AM Khem Raj wrote:
>
> On Fri, Jul 22, 2022 at 10:30 AM Ross Burton wrote:
> >
> > On 22 Jul 2022, at 15:28, Khem Raj via lists.openembedded.org
> > wrote:
> > >
> > > On Fri, Jul 22, 2022 at 6:36 AM Bartosz Golaszewski wrote:
> > >>
> > >> On Thu, Jul 21, 2022
On Fri, Jul 22, 2022 at 10:35 AM Khem Raj wrote:
>
> On Fri, Jul 22, 2022 at 10:31 AM Khem Raj wrote:
> >
> > On Fri, Jul 22, 2022 at 10:30 AM Ross Burton wrote:
> > >
> > > On 22 Jul 2022, at 15:28, Khem Raj via lists.openembedded.org
> > > wrote:
> > > >
> > > > On Fri, Jul 22, 2022 at 6:36
Source: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git
MR: 119424
Type: Security Fix
Disposition: Backport from
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=34c649b3601383cd11dbc76221747ec16fd68e1b
ChangeID: 97de66d6aa74e12cb1bf82fe85ee62e2530fccf6
Description:
On Fri, Jul 22, 2022 at 6:36 AM Bartosz Golaszewski wrote:
>
> 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
On Fri, Jul 22, 2022 at 10:30 AM Ross Burton wrote:
>
> On 22 Jul 2022, at 15:28, Khem Raj via lists.openembedded.org
> wrote:
> >
> > On Fri, Jul 22, 2022 at 6:36 AM Bartosz Golaszewski wrote:
> >>
> >> On Thu, Jul 21, 2022 at 3:52 PM Khem Raj wrote:
> >>>
> >>> I don’t see config.log for
On Fri, Jul 22, 2022 at 7:13 AM Ross Burton wrote:
>
> Set V=1 so that the compile log is useful when things go wrong.
>
verbose logs do add to build time, usually when build fails the error
parts are good with dumping error and
compiler cmdline, is that not the case here ?
> Signed-off-by:
> On 22 Jul 2022, at 15:54, Khem Raj via lists.openembedded.org
> wrote:
>
> On Fri, Jul 22, 2022 at 7:13 AM Ross Burton wrote:
>>
>> Set V=1 so that the compile log is useful when things go wrong.
>>
>
> verbose logs do add to build time, usually when build fails the error
> parts are
Thanks, this looks fine. Can you resend the patch using 'git
send-email'? I'm not sure if sending the patch as a quoted reply to me
allows it to be picked from the mailing list.
Alex
On Thu, 21 Jul 2022 at 02:19, Shruthi Ravichandran
wrote:
>
> Some opkg commands print an error during cleanup
There's been a recent discussion about how we can make the Yocto SDK
experience better [1]. One of the ideas was to eliminate the SDK
as a separate artefact altogether and simply provide everything
that the SDK and eSDKs do directly in a yocto build. This does not
mean that people have to 'learn
When using meson-native directly from bitbake this has no effect and
everything works as before; the use case is being able to build
meson-driven projects from the 'direct SDK' environment. Build systems
like cmake/autotools are entirely driven by environment variables,
but meson needs
Specifically:
1. Place the environment setup file into $B and not into $TMPDIR,
so that the recipe using the class can itself better decide what to do with the
file.
2. Use global, unified sysroots (provided through build-sysroots recipe)
and not recipe-specific ones, as this allows flexible
Specifically:
1. Add a few more toolchain items to DEPENDS so they're available in the recipe
sysroot.
2. Use deploy mechanism to place the SDK environment setup file and testdata
for testing it
into the image deploy directory.
3. Add ability to run SDK tests via the testsdk class and task. This
Other tests already have similar tweaks.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/sdk/cases/buildepoxy.py | 3 ++-
meta/lib/oeqa/sdk/cases/buildgalculator.py | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/sdk/cases/buildepoxy.py
This is a simpler version of the same class in testsdk.py, as it does not
need to unpack and set up the SDK, and can proceed to the tests straight away.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/sdk/testmetaidesupport.py | 43 +
1 file changed, 43 insertions(+)
On Fri, Jul 22, 2022 at 12:17 PM Ross Burton wrote:
>
>
>
> > On 22 Jul 2022, at 15:54, Khem Raj via lists.openembedded.org
> > wrote:
> >
> > On Fri, Jul 22, 2022 at 7:13 AM Ross Burton wrote:
> >>
> >> Set V=1 so that the compile log is useful when things go wrong.
> >>
> >
> > verbose logs
Some opkg commands print an error during cleanup when the tmp_dir
does not exist and an attempt is made to delete it. The error messages
are harmless and the opkg commands eventually succeed.
When these commands are run and stderr is piped to stdout, the error
messages may clobber the stdout and
So should I submit a patch with that change? I don't know how to reproduce the
original issue so I won't have any way to prove if this is a viable fix.
Drew
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168425):
On Fri, Jul 22, 2022 at 4:42 PM Drew Moseley wrote:
>
> So should I submit a patch with that change? I don't know how to reproduce
> the original issue so I won't have any way to prove if this is a viable fix.
>
Does this fix the problem you see ? if it does then perhaps Claudius
can help
28 matches
Mail list logo
