* [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log
@ 2026-03-10 11:33 Mikko Rapeli
2026-03-10 12:41 ` [OE-core] " Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Mikko Rapeli @ 2026-03-10 11:33 UTC (permalink / raw)
To: openembedded-core; +Cc: Mikko Rapeli
With https://lists.yoctoproject.org/g/linux-yocto/message/16359
updates to merge_config.sh in kern-tools-native the output
is useful and not too verbose. Thus capture it to normal
do_kernel_configme task logs.
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
meta/classes-recipe/kernel-yocto.bbclass | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/meta/classes-recipe/kernel-yocto.bbclass b/meta/classes-recipe/kernel-yocto.bbclass
index e53bf1519418..d981ca0e30e6 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -492,14 +492,9 @@ do_kernel_configme() {
bbfatal_log "Could not find configuration queue (${meta_dir}/config.queue)"
fi
- CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
+ CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs}
if [ $? -ne 0 -o ! -f ${B}/.config ]; then
bberror "Could not generate a .config for ${KMACHINE}-${LINUX_KERNEL_TYPE}"
- if [ ${KCONF_AUDIT_LEVEL} -gt 1 ]; then
- bbfatal_log "`cat ${meta_dir}/cfg/merge_config_build.log`"
- else
- bbfatal_log "Details can be found at: ${S}/${meta_dir}/cfg/merge_config_build.log"
- fi
fi
if [ ! -z "${LINUX_VERSION_EXTENSION}" ]; then
--
2.34.1
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [OE-core] [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log
2026-03-10 11:33 [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log Mikko Rapeli
@ 2026-03-10 12:41 ` Bruce Ashfield
2026-03-10 12:49 ` Mikko Rapeli
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Ashfield @ 2026-03-10 12:41 UTC (permalink / raw)
To: mikko.rapeli; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 2937 bytes --]
On Tue, Mar 10, 2026 at 7:34 AM Mikko Rapeli via lists.openembedded.org
<mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> With https://lists.yoctoproject.org/g/linux-yocto/message/16359
> updates to merge_config.sh in kern-tools-native the output
> is useful and not too verbose. Thus capture it to normal
> do_kernel_configme task logs.
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
> meta/classes-recipe/kernel-yocto.bbclass | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/meta/classes-recipe/kernel-yocto.bbclass
> b/meta/classes-recipe/kernel-yocto.bbclass
> index e53bf1519418..d981ca0e30e6 100644
> --- a/meta/classes-recipe/kernel-yocto.bbclass
> +++ b/meta/classes-recipe/kernel-yocto.bbclass
> @@ -492,14 +492,9 @@ do_kernel_configme() {
> bbfatal_log "Could not find configuration queue
> (${meta_dir}/config.queue)"
> fi
>
> - CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}"
> LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} >
> ${meta_dir}/cfg/merge_config_build.log 2>&1
> + CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}"
> LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs}
> if [ $? -ne 0 -o ! -f ${B}/.config ]; then
> bberror "Could not generate a .config for
> ${KMACHINE}-${LINUX_KERNEL_TYPE}"
> - if [ ${KCONF_AUDIT_LEVEL} -gt 1 ]; then
> - bbfatal_log "`cat
> ${meta_dir}/cfg/merge_config_build.log`"
> - else
> - bbfatal_log "Details can be found at:
> ${S}/${meta_dir}/cfg/merge_config_build.log"
> - fi
>
There are tools built on having the log around in a file. So we can't merge
this as-is.
Why not just change the default to 1 (and not make it fatal) instead of
undoing all the infrastructure ?
Bruce
fi
>
> if [ ! -z "${LINUX_VERSION_EXTENSION}" ]; then
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#232770):
> https://lists.openembedded.org/g/openembedded-core/message/232770
> Mute This Topic: https://lists.openembedded.org/mt/118239002/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
[-- Attachment #2: Type: text/html, Size: 4999 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [OE-core] [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log
2026-03-10 12:41 ` [OE-core] " Bruce Ashfield
@ 2026-03-10 12:49 ` Mikko Rapeli
2026-03-10 12:55 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Mikko Rapeli @ 2026-03-10 12:49 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
Hi,
On Tue, Mar 10, 2026 at 08:41:46AM -0400, Bruce Ashfield wrote:
> On Tue, Mar 10, 2026 at 7:34 AM Mikko Rapeli via lists.openembedded.org
> <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
>
> > With https://lists.yoctoproject.org/g/linux-yocto/message/16359
> > updates to merge_config.sh in kern-tools-native the output
> > is useful and not too verbose. Thus capture it to normal
> > do_kernel_configme task logs.
> >
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> > meta/classes-recipe/kernel-yocto.bbclass | 7 +------
> > 1 file changed, 1 insertion(+), 6 deletions(-)
> >
> > diff --git a/meta/classes-recipe/kernel-yocto.bbclass
> > b/meta/classes-recipe/kernel-yocto.bbclass
> > index e53bf1519418..d981ca0e30e6 100644
> > --- a/meta/classes-recipe/kernel-yocto.bbclass
> > +++ b/meta/classes-recipe/kernel-yocto.bbclass
> > @@ -492,14 +492,9 @@ do_kernel_configme() {
> > bbfatal_log "Could not find configuration queue
> > (${meta_dir}/config.queue)"
> > fi
> >
> > - CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> > ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}"
> > LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> > ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} >
> > ${meta_dir}/cfg/merge_config_build.log 2>&1
> > + CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> > ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}"
> > LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> > ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs}
> > if [ $? -ne 0 -o ! -f ${B}/.config ]; then
> > bberror "Could not generate a .config for
> > ${KMACHINE}-${LINUX_KERNEL_TYPE}"
> > - if [ ${KCONF_AUDIT_LEVEL} -gt 1 ]; then
> > - bbfatal_log "`cat
> > ${meta_dir}/cfg/merge_config_build.log`"
> > - else
> > - bbfatal_log "Details can be found at:
> > ${S}/${meta_dir}/cfg/merge_config_build.log"
> > - fi
> >
>
> There are tools built on having the log around in a file. So we can't merge
> this as-is.
Which tools? Why aren't these tools part of oe-core?
Standard practice of oe-core is to have details in task logs. I do not
think extra log locations should be used or logs hidden behind other
variables or switches.
Cheers,
-Mikko
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [OE-core] [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log
2026-03-10 12:49 ` Mikko Rapeli
@ 2026-03-10 12:55 ` Bruce Ashfield
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Ashfield @ 2026-03-10 12:55 UTC (permalink / raw)
To: Mikko Rapeli; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]
On Tue, Mar 10, 2026 at 8:49 AM Mikko Rapeli <mikko.rapeli@linaro.org>
wrote:
> Hi,
>
> On Tue, Mar 10, 2026 at 08:41:46AM -0400, Bruce Ashfield wrote:
> > On Tue, Mar 10, 2026 at 7:34 AM Mikko Rapeli via lists.openembedded.org
> > <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> >
> > > With https://lists.yoctoproject.org/g/linux-yocto/message/16359
> > > updates to merge_config.sh in kern-tools-native the output
> > > is useful and not too verbose. Thus capture it to normal
> > > do_kernel_configme task logs.
> > >
> > > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > > ---
> > > meta/classes-recipe/kernel-yocto.bbclass | 7 +------
> > > 1 file changed, 1 insertion(+), 6 deletions(-)
> > >
> > > diff --git a/meta/classes-recipe/kernel-yocto.bbclass
> > > b/meta/classes-recipe/kernel-yocto.bbclass
> > > index e53bf1519418..d981ca0e30e6 100644
> > > --- a/meta/classes-recipe/kernel-yocto.bbclass
> > > +++ b/meta/classes-recipe/kernel-yocto.bbclass
> > > @@ -492,14 +492,9 @@ do_kernel_configme() {
> > > bbfatal_log "Could not find configuration queue
> > > (${meta_dir}/config.queue)"
> > > fi
> > >
> > > - CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> > > ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}"
> CC="${KERNEL_CC}"
> > > LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> > > ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} >
> > > ${meta_dir}/cfg/merge_config_build.log 2>&1
> > > + CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC}
> > > ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}"
> CC="${KERNEL_CC}"
> > > LD="${KERNEL_LD}" OBJCOPY="${KERNEL_OBJCOPY}" STRIP="${KERNEL_STRIP}"
> > > ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs}
> > > if [ $? -ne 0 -o ! -f ${B}/.config ]; then
> > > bberror "Could not generate a .config for
> > > ${KMACHINE}-${LINUX_KERNEL_TYPE}"
> > > - if [ ${KCONF_AUDIT_LEVEL} -gt 1 ]; then
> > > - bbfatal_log "`cat
> > > ${meta_dir}/cfg/merge_config_build.log`"
> > > - else
> > > - bbfatal_log "Details can be found at:
> > > ${S}/${meta_dir}/cfg/merge_config_build.log"
> > > - fi
> > >
> >
> > There are tools built on having the log around in a file. So we can't
> merge
> > this as-is.
>
> Which tools? Why aren't these tools part of oe-core?
> Standard practice of oe-core is to have details in task logs. I do not
> think extra log locations should be used or logs hidden behind other
> variables or switches.
>
>
Thanks, but I'm not sure why you are educating me on something
I've been involved with for a very long time.
Bruce
> Cheers,
>
> -Mikko
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
[-- Attachment #2: Type: text/html, Size: 5105 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-03-10 12:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-10 11:33 [PATCH] kernel-yocto.bbclass: capture merge_config.sh output to task log Mikko Rapeli
2026-03-10 12:41 ` [OE-core] " Bruce Ashfield
2026-03-10 12:49 ` Mikko Rapeli
2026-03-10 12:55 ` Bruce Ashfield
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.