[master][PATCH v2 0/3] jailhouse: Fix build issues and QA warnings

[master][PATCH v2 0/3] jailhouse: Fix build issues and QA warnings

[Mahammed Sadik Shaik]

This series fixes build failures and QA warnings in the jailhouse recipes:

1. Fix JH_RAMFS image path to match current naming convention
2. Add buildpaths fix for kernel module compilation
3. Inhibit debug package split for bare-metal inmate binaries

These changes resolve build failures when searching for initramfs images
and eliminate QA warnings related to buildpaths and debug packages.

Changes in v2:
  - Split buildpaths fix into separate commit
  - Improved commit message descriptions
  - Added KCFLAGS with -ffile-prefix-map for reproducible builds

Link to v1:https://lists.yoctoproject.org/g/meta-ti/message/19674

Mahammed Sadik Shaik (3):
  jailhouse: Fix JH_RAMFS image path
  jailhouse-inmate: Inhibit debug package split
  ti-jailhouse: Fix buildpaths QA warning

 meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb | 3 +++
 meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb    | 8 ++++----
 meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc    | 4 ++--
 3 files changed, 9 insertions(+), 6 deletions(-)

-- 
2.34.1

[master][PATCH v2 1/3] jailhouse: Fix JH_RAMFS image path

[Mahammed Sadik Shaik]

Update JH_RAMFS_IMAGE references to use correct .cpio
extension instead of .rootfs.cpio to match current image
naming convention

Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
---
 meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb b/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
index 0113a916..7d908215 100644
--- a/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
+++ b/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
@@ -55,11 +55,11 @@ do_install() {
 	install -d ${D}/boot
 	if [ -n "${JH_RAMFS_IMAGE}" ]
 	then
-		if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}*-${MACHINE}.rootfs.cpio ]
+		if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}*-${MACHINE}.cpio ]
 		then
-			install -m 0644 ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}*-${MACHINE}.rootfs.cpio ${D}/boot
+			install -m 0644 ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}*-${MACHINE}.cpio ${D}/boot
 		else
-			bberror "Could not find JH_RAMFS_IMAGE (${JH_RAMFS_IMAGE}*-${MACHINE}.rootfs.cpio)!"
+			bberror "Could not find JH_RAMFS_IMAGE (${JH_RAMFS_IMAGE}*-${MACHINE}.cpio)!"
 			bberror "Please make sure that \"cpio\" is in IMAGE_FSTYPES."
 		fi
 	fi
@@ -72,7 +72,7 @@ do_install() {
 		./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
 			-a ${JH_ARCH} -c "${JH_CMDLINE}" \
 			-d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
-			-i ${D}/boot/${JH_RAMFS_IMAGE}*-${MACHINE}.rootfs.cpio \
+			-i ${D}/boot/${JH_RAMFS_IMAGE}*-${MACHINE}.cpio \
 			${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
 			${DEPLOY_DIR_IMAGE}/Image \
 			| tr -cd '\11\12\15\40-\176' \
-- 
2.34.1

[master][PATCH v2 2/3] jailhouse-inmate: Inhibit debug package split

[Mahammed Sadik Shaik]

Inmate binaries are bare-metal applications without standard debug
symbols that can be meaningfully split. Inhibit debug package
creation to avoid unnecessary packaging overhead and potential
QA warnings.

Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
---
 meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb b/meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb
index 39654a53..c6b3b85b 100644
--- a/meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb
+++ b/meta-ti-extras/recipes-ti/jailhouse/jailhouse-inmate.bb
@@ -1,5 +1,8 @@
 require ti-jailhouse.inc
 
+# Inmate binaries are bare-metal; no debug package needed
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
+
 do_install() {
 
 	install -d ${D}${bindir}
-- 
2.34.1

[master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Mahammed Sadik Shaik]

Add -ffile-prefix-map flags to KCFLAGS to remove build path
references from kernel module compilation, ensuring reproducible
builds and preventing absolute path leakage in binaries.

This resolves buildpaths QA warnings during packaging.

Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
---
 meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
index 91076c9e..8308f0e5 100644
--- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
+++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
@@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS} -DLIBEXECDIR=\\\"${libexecdir}\\\" \
 
 TOOLS_SRC_DIR = "${S}/tools"
 
-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR}"
-
+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR} \
+    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/= -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
 do_compile() {
         oe_runmake V=1
 }
-- 
2.34.1

Re: [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Ryan Eatmon]

On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> Add -ffile-prefix-map flags to KCFLAGS to remove build path
> references from kernel module compilation, ensuring reproducible
> builds and preventing absolute path leakage in binaries.
> 
> This resolves buildpaths QA warnings during packaging.
> 
> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> ---
>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> index 91076c9e..8308f0e5 100644
> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS} -DLIBEXECDIR=\\\"${libexecdir}\\\" \
>   
>   TOOLS_SRC_DIR = "${S}/tools"
>   
> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR}"
> -
> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR} \
> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/= -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
>   do_compile() {
>           oe_runmake V=1
>   }

Thank you.  I was going to comment on the v1 to not disable buildpaths.

-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS

Re: [master][PATCH v2 0/3] jailhouse: Fix build issues and QA warnings

[PRC Automation]

meta-ti / na / 20260309170134.2779295-1-s-sadik

PRC Results: PASS

=========================================================
  check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
WARN - [master][PATCH v2 1/3] jailhouse: Fix JH_RAMFS image path
    WARN: Revised patch missing a comment. (REVISION-1)
        patch
    
    For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
WARN - [master][PATCH v2 2/3] jailhouse-inmate: Inhibit debug package split
    WARN: Revised patch missing a comment. (REVISION-1)
        patch
    
    For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
WARN - [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning
    WARN: Revised patch missing a comment. (REVISION-1)
        patch
    
    For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887



=========================================================
  apply-yocto-patch: PASS
=========================================================
master
=====================
Summary:
- Patch Series: [master][PATCH v2 0/3] jailhouse: Fix build issues and QA warnings
- Submitter: From: Mahammed Sadik Shaik <s-sadik@ti.com>
- Date: Date: Mon, 9 Mar 2026 22:31:31 +0530
- Num Patches: 3
- Mailing List (public inbox) Commit SHA: 32b3f4c540fc6ca3a8dd2d7c370cbf433aeb7953

Applied to:
- Repository: lcpd-prc-meta-ti
- Base Branch: master-wip
- Commit Author: Ryan Eatmon <reatmon@ti.com>
- Commit Subject: conf: Add falcon support natively
- Commit SHA: deced73fc1a79071913faddb857ca79c2f6c7b72

Patches
----------------------------------------
All patches applied



=========================================================
  check-yocto-repo: PASS
=========================================================
master
=====================
PASS



=========================================================
  yocto-check-layers: PASS
=========================================================
master - PASS
=====================
All checks passed

Re: [meta-ti] [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Denys Dmytriyenko]

On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> 
> 
> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> >Add -ffile-prefix-map flags to KCFLAGS to remove build path
> >references from kernel module compilation, ensuring reproducible
> >builds and preventing absolute path leakage in binaries.
> >
> >This resolves buildpaths QA warnings during packaging.
> >
> >Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> >---
> >  meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> >diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >index 91076c9e..8308f0e5 100644
> >--- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >+++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >@@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS} -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> >  TOOLS_SRC_DIR = "${S}/tools"
> >-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR}"
> >-
> >+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" KDIR=${STAGING_KERNEL_BUILDDIR} \
> >+    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/= -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> >  do_compile() {
> >          oe_runmake V=1
> >  }

Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()


> Thank you.  I was going to comment on the v1 to not disable buildpaths.

+1

Re: [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Sadik]

On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:

>
> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
> lists.yoctoproject.org wrote:
> > 
> > 
> > On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> > >Add -ffile-prefix-map flags to KCFLAGS to remove build path
> > >references from kernel module compilation, ensuring reproducible
> > >builds and preventing absolute path leakage in binaries.
> > >
> > >This resolves buildpaths QA warnings during packaging.
> > >
> > >Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> > >---
> > >  meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > >diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > >index 91076c9e..8308f0e5 100644
> > >--- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > >+++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > >@@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> > >  TOOLS_SRC_DIR = "${S}/tools"
> > >-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
> KDIR=${STAGING_KERNEL_BUILDDIR}"
> > >-
> > >+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
> KDIR=${STAGING_KERNEL_BUILDDIR} \
> > >+    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> > >  do_compile() {
> > >          oe_runmake V=1
> > >  }
> 
> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()

Thanks for the review Denys, Apologies for multiple replies was facing some issues with relply all in mail.

Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile() override. . This is insufficient for jailhouse, which requires building:
1. Kernel modules (driver/jailhouse.ko)
2. Hypervisor binary (hypervisor/jailhouse.bin)
3. Userspace tools (tools/jailhouse, jailhouse-*)
4. Inmate demos (inmates/demos/*) — causing the install failure for all the demos during the build.

The do_compile() override is needed to run a plain oe_runmake which hits jailhouse's top-level Makefile and builds the full project.

If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that doesn't serve our purpose of completely overriding the do_compile
And also I couldn't find an existing bbclass that does "run the top-level Makefile and build everything."

> 
> 
> > Thank you.  I was going to comment on the v1 to not disable buildpaths.
> 
> +1
>

Re: [meta-ti] [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Andrew Davis]

On 3/10/26 3:58 AM, Sadik via lists.yoctoproject.org wrote:
> On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
> 
>>
>> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
>> lists.yoctoproject.org wrote:
>>>
>>>
>>> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
>>>> Add -ffile-prefix-map flags to KCFLAGS to remove build path
>>>> references from kernel module compilation, ensuring reproducible
>>>> builds and preventing absolute path leakage in binaries.
>>>>
>>>> This resolves buildpaths QA warnings during packaging.
>>>>
>>>> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
>>>> ---
>>>>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>> index 91076c9e..8308f0e5 100644
>>>> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
>> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
>>>>   TOOLS_SRC_DIR = "${S}/tools"
>>>> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
>> KDIR=${STAGING_KERNEL_BUILDDIR}"
>>>> -
>>>> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
>> KDIR=${STAGING_KERNEL_BUILDDIR} \
>>>> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
>> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
>>>>   do_compile() {
>>>>           oe_runmake V=1
>>>>   }
>>
>> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
> 
> Thanks for the review Denys, Apologies for multiple replies was facing some issues with relply all in mail.
> 
> Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile() override. . This is insufficient for jailhouse, which requires building:
> 1. Kernel modules (driver/jailhouse.ko)
> 2. Hypervisor binary (hypervisor/jailhouse.bin)
> 3. Userspace tools (tools/jailhouse, jailhouse-*)
> 4. Inmate demos (inmates/demos/*) — causing the install failure for all the demos during the build.
> 
> The do_compile() override is needed to run a plain oe_runmake which hits jailhouse's top-level Makefile and builds the full project.
> 

Does the default do_compile() not hit the top level Makefile?

Andrew

> If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that doesn't serve our purpose of completely overriding the do_compile
> And also I couldn't find an existing bbclass that does "run the top-level Makefile and build everything."
> 
>>
>>
>>> Thank you.  I was going to comment on the v1 to not disable buildpaths.
>>
>> +1
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#19687): https://lists.yoctoproject.org/g/meta-ti/message/19687
>> Mute This Topic: https://lists.yoctoproject.org/mt/118225330/3619733
>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>

Re: [meta-ti] [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Denys Dmytriyenko]

On Tue, Mar 10, 2026 at 01:58:45AM -0700, Sadik via lists.yoctoproject.org wrote:
> On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
> 
> >
> > On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
> > lists.yoctoproject.org wrote:
> > > 
> > > 
> > > On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> > > >Add -ffile-prefix-map flags to KCFLAGS to remove build path
> > > >references from kernel module compilation, ensuring reproducible
> > > >builds and preventing absolute path leakage in binaries.
> > > >
> > > >This resolves buildpaths QA warnings during packaging.
> > > >
> > > >Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> > > >---
> > > >  meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > >diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > >index 91076c9e..8308f0e5 100644
> > > >--- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > >+++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > >@@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
> > -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> > > >  TOOLS_SRC_DIR = "${S}/tools"
> > > >-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
> > KDIR=${STAGING_KERNEL_BUILDDIR}"
> > > >-
> > > >+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}"
> > KDIR=${STAGING_KERNEL_BUILDDIR} \
> > > >+    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
> > -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> > > >  do_compile() {
> > > >          oe_runmake V=1
> > > >  }
> > 
> > Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
> 
> Thanks for the review Denys, Apologies for multiple replies was facing some issues with relply all in mail.
> 
> Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile() override. . This is insufficient for jailhouse, which requires building:
> 1. Kernel modules (driver/jailhouse.ko)
> 2. Hypervisor binary (hypervisor/jailhouse.bin)
> 3. Userspace tools (tools/jailhouse, jailhouse-*)
> 4. Inmate demos (inmates/demos/*) — causing the install failure for all the demos during the build.
> 
> The do_compile() override is needed to run a plain oe_runmake which hits jailhouse's top-level Makefile and builds the full project.

The default do_compile() does exactly that - calls oe_runmake:
https://git.openembedded.org/openembedded-core/tree/meta/classes-global/base.bbclass#n399


> If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that doesn't serve our purpose of completely overriding the do_compile
> And also I couldn't find an existing bbclass that does "run the top-level Makefile and build everything."
> 
> > 
> > 
> > > Thank you.  I was going to comment on the v1 to not disable buildpaths.
> > 
> > +1

Re: [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Sadik]

On Tue, Mar 10, 2026 at 07:22 PM, Denys Dmytriyenko wrote:

>
> On Tue, Mar 10, 2026 at 01:58:45AM -0700, Sadik via lists.yoctoproject.org
> wrote:
> > On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
> > 
> > >
> > > On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
> > > lists.yoctoproject.org wrote:
> > > > 
> > > > 
> > > > On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> > > > >Add -ffile-prefix-map flags to KCFLAGS to remove build path
> > > > >references from kernel module compilation, ensuring reproducible
> > > > >builds and preventing absolute path leakage in binaries.
> > > > >
> > > > >This resolves buildpaths QA warnings during packaging.
> > > > >
> > > > >Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> > > > >---
> > > > >  meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> > > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > >diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > > >index 91076c9e..8308f0e5 100644
> > > > >--- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > > >+++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> > > > >@@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
> > > -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> > > > >  TOOLS_SRC_DIR = "${S}/tools"
> > > > >-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> CC="${CC}"
> > > KDIR=${STAGING_KERNEL_BUILDDIR}"
> > > > >-
> > > > >+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> CC="${CC}"
> > > KDIR=${STAGING_KERNEL_BUILDDIR} \
> > > > >+    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
> > > -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> > > > >  do_compile() {
> > > > >          oe_runmake V=1
> > > > >  }
> > > 
> > > Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
> > 
> > Thanks for the review Denys, Apologies for multiple replies was facing some
> issues with relply all in mail.
> > 
> > Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile()
> override. . This is insufficient for jailhouse, which requires building:
> > 1. Kernel modules (driver/jailhouse.ko)
> > 2. Hypervisor binary (hypervisor/jailhouse.bin)
> > 3. Userspace tools (tools/jailhouse, jailhouse-*)
> > 4. Inmate demos (inmates/demos/*) — causing the install failure for all
> the demos during the build.
> > 
> > The do_compile() override is needed to run a plain oe_runmake which hits
> jailhouse's top-level Makefile and builds the full project.
> 
> The default do_compile() does exactly that - calls oe_runmake:
> https://git.openembedded.org/openembedded-core/tree/meta/classes-global/base.bbclass#n399

Yeah you are right, that the default base_do_compile() calls oe_runmake, which would work fine. But, the jailhouse recipe inherits module bbclass,
"inherit module python3native bash-completion deploy "
 which overrides default do_compile() with module_do_compile. resulting in compilation errors if do_compile override is removed.
If I don't use the do-compile override I am still getting build errors. I am unable to remove the module bbclass is required for building jailhouse kernel modules.

> 
> 
> > If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that
> doesn't serve our purpose of completely overriding the do_compile
> > And also I couldn't find an existing bbclass that does "run the top-level
> Makefile and build everything."
> > 
> > > 
> > > 
> > > > Thank you.  I was going to comment on the v1 to not disable buildpaths.
> > > 
> > > +1
>

Re: [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Sadik]

On Tue, Mar 10, 2026 at 07:16 PM, Andrew Davis wrote:

>
> On 3/10/26 3:58 AM, Sadik via lists.yoctoproject.org wrote:
> > On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
> > 
> >>
> >> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
> >> lists.yoctoproject.org wrote:
> >>>
> >>>
> >>> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> >>>> Add -ffile-prefix-map flags to KCFLAGS to remove build path
> >>>> references from kernel module compilation, ensuring reproducible
> >>>> builds and preventing absolute path leakage in binaries.
> >>>>
> >>>> This resolves buildpaths QA warnings during packaging.
> >>>>
> >>>> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> >>>> ---
> >>>>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> >>>>   1 file changed, 2 insertions(+), 2 deletions(-)
> >>>>
> >>>> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>> index 91076c9e..8308f0e5 100644
> >>>> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
> >> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> >>>>   TOOLS_SRC_DIR = "${S}/tools"
> >>>> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> CC="${CC}"
> >> KDIR=${STAGING_KERNEL_BUILDDIR}"
> >>>> -
> >>>> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> CC="${CC}"
> >> KDIR=${STAGING_KERNEL_BUILDDIR} \
> >>>> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
> >> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> >>>>   do_compile() {
> >>>>           oe_runmake V=1
> >>>>   }
> >>
> >> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
> > 
> > Thanks for the review Denys, Apologies for multiple replies was facing some
> issues with relply all in mail.
> > 
> > Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile()
> override. . This is insufficient for jailhouse, which requires building:
> > 1. Kernel modules (driver/jailhouse.ko)
> > 2. Hypervisor binary (hypervisor/jailhouse.bin)
> > 3. Userspace tools (tools/jailhouse, jailhouse-*)
> > 4. Inmate demos (inmates/demos/*) — causing the install failure for all
> the demos during the build.
> > 
> > The do_compile() override is needed to run a plain oe_runmake which hits
> jailhouse's top-level Makefile and builds the full project.
> > 
> 
> Does the default do_compile() not hit the top level Makefile?
Yeah Andrew, the default base_do_compile() calls oe_runmake, which would work fine. But, the jailhouse recipe inherits module bbclass,
"inherit module python3native bash-completion deploy "
If I don't use the do-compile override I am still getting build errors. The module bbclass is required for building jailhouse kernel modules.

> 
> Andrew
> 
> > If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that
> doesn't serve our purpose of completely overriding the do_compile
> > And also I couldn't find an existing bbclass that does "run the top-level
> Makefile and build everything."
> > 
> >>
> >>
> >>> Thank you.  I was going to comment on the v1 to not disable buildpaths.
> >>
> >> +1
> >>
> >>
> >>
> >> 
> >>
> 
>

Re: [meta-ti] [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Andrew Davis]

On 3/10/26 12:08 PM, Sadik via lists.yoctoproject.org wrote:
> On Tue, Mar 10, 2026 at 07:22 PM, Denys Dmytriyenko wrote:
> 
>>
>> On Tue, Mar 10, 2026 at 01:58:45AM -0700, Sadik via lists.yoctoproject.org
>> wrote:
>>> On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
>>>
>>>>
>>>> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
>>>> lists.yoctoproject.org wrote:
>>>>>
>>>>>
>>>>> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
>>>>>> Add -ffile-prefix-map flags to KCFLAGS to remove build path
>>>>>> references from kernel module compilation, ensuring reproducible
>>>>>> builds and preventing absolute path leakage in binaries.
>>>>>>
>>>>>> This resolves buildpaths QA warnings during packaging.
>>>>>>
>>>>>> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
>>>>>> ---
>>>>>>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
>>>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>>
>>>>>> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>> index 91076c9e..8308f0e5 100644
>>>>>> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
>>>> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
>>>>>>   TOOLS_SRC_DIR = "${S}/tools"
>>>>>> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
>> CC="${CC}"
>>>> KDIR=${STAGING_KERNEL_BUILDDIR}"
>>>>>> -
>>>>>> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
>> CC="${CC}"
>>>> KDIR=${STAGING_KERNEL_BUILDDIR} \
>>>>>> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
>>>> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
>>>>>>   do_compile() {
>>>>>>           oe_runmake V=1
>>>>>>   }
>>>>
>>>> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
>>>
>>> Thanks for the review Denys, Apologies for multiple replies was facing some
>> issues with relply all in mail.
>>>
>>> Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the do_compile()
>> override. . This is insufficient for jailhouse, which requires building:
>>> 1. Kernel modules (driver/jailhouse.ko)
>>> 2. Hypervisor binary (hypervisor/jailhouse.bin)
>>> 3. Userspace tools (tools/jailhouse, jailhouse-*)
>>> 4. Inmate demos (inmates/demos/*) — causing the install failure for all
>> the demos during the build.
>>>
>>> The do_compile() override is needed to run a plain oe_runmake which hits
>> jailhouse's top-level Makefile and builds the full project.
>>
>> The default do_compile() does exactly that - calls oe_runmake:
>> https://git.openembedded.org/openembedded-core/tree/meta/classes-global/base.bbclass#n399
> 
> Yeah you are right, that the default base_do_compile() calls oe_runmake, which would work fine. But, the jailhouse recipe inherits module bbclass,
> "inherit module python3native bash-completion deploy"
>   which overrides default do_compile() with module_do_compile. resulting in compilation errors if do_compile override is removed.
> If I don't use the do-compile override I am still getting build errors. I am unable to remove the module bbclass is required for building jailhouse kernel modules.
> 

Split out the kernel module building into its own recipe.

Andrew

>>
>>
>>> If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that
>> doesn't serve our purpose of completely overriding the do_compile
>>> And also I couldn't find an existing bbclass that does "run the top-level
>> Makefile and build everything."
>>>
>>>>
>>>>
>>>>> Thank you.  I was going to comment on the v1 to not disable buildpaths.
>>>>
>>>> +1
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#19692): https://lists.yoctoproject.org/g/meta-ti/message/19692
>> Mute This Topic: https://lists.yoctoproject.org/mt/118225330/3619733
>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>

Re: [meta-ti] [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Ryan Eatmon]

On 3/10/2026 12:58 PM, Andrew Davis via lists.yoctoproject.org wrote:
> On 3/10/26 12:08 PM, Sadik via lists.yoctoproject.org wrote:
>> On Tue, Mar 10, 2026 at 07:22 PM, Denys Dmytriyenko wrote:
>>
>>>
>>> On Tue, Mar 10, 2026 at 01:58:45AM -0700, Sadik via 
>>> lists.yoctoproject.org
>>> wrote:
>>>> On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
>>>>
>>>>>
>>>>> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
>>>>> lists.yoctoproject.org wrote:
>>>>>>
>>>>>>
>>>>>> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
>>>>>>> Add -ffile-prefix-map flags to KCFLAGS to remove build path
>>>>>>> references from kernel module compilation, ensuring reproducible
>>>>>>> builds and preventing absolute path leakage in binaries.
>>>>>>>
>>>>>>> This resolves buildpaths QA warnings during packaging.
>>>>>>>
>>>>>>> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
>>>>>>> ---
>>>>>>>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
>>>>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>>>
>>>>>>> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>>> index 91076c9e..8308f0e5 100644
>>>>>>> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>>> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
>>>>>>> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
>>>>> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
>>>>>>>   TOOLS_SRC_DIR = "${S}/tools"
>>>>>>> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
>>> CC="${CC}"
>>>>> KDIR=${STAGING_KERNEL_BUILDDIR}"
>>>>>>> -
>>>>>>> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
>>> CC="${CC}"
>>>>> KDIR=${STAGING_KERNEL_BUILDDIR} \
>>>>>>> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
>>>>> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
>>>>>>>   do_compile() {
>>>>>>>           oe_runmake V=1
>>>>>>>   }
>>>>>
>>>>> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
>>>>
>>>> Thanks for the review Denys, Apologies for multiple replies was 
>>>> facing some
>>> issues with relply all in mail.
>>>>
>>>> Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the 
>>>> do_compile()
>>> override. . This is insufficient for jailhouse, which requires building:
>>>> 1. Kernel modules (driver/jailhouse.ko)
>>>> 2. Hypervisor binary (hypervisor/jailhouse.bin)
>>>> 3. Userspace tools (tools/jailhouse, jailhouse-*)
>>>> 4. Inmate demos (inmates/demos/*) — causing the install failure for all
>>> the demos during the build.
>>>>
>>>> The do_compile() override is needed to run a plain oe_runmake which 
>>>> hits
>>> jailhouse's top-level Makefile and builds the full project.
>>>
>>> The default do_compile() does exactly that - calls oe_runmake:
>>> https://git.openembedded.org/openembedded-core/tree/meta/classes-global/base.bbclass#n399
>>
>> Yeah you are right, that the default base_do_compile() calls 
>> oe_runmake, which would work fine. But, the jailhouse recipe inherits 
>> module bbclass,
>> "inherit module python3native bash-completion deploy"
>>   which overrides default do_compile() with module_do_compile. 
>> resulting in compilation errors if do_compile override is removed.
>> If I don't use the do-compile override I am still getting build 
>> errors. I am unable to remove the module bbclass is required for 
>> building jailhouse kernel modules.
>>
> 
> Split out the kernel module building into its own recipe.

Agreed.


> Andrew
> 
>>>
>>>
>>>> If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that
>>> doesn't serve our purpose of completely overriding the do_compile
>>>> And also I couldn't find an existing bbclass that does "run the 
>>>> top-level
>>> Makefile and build everything."
>>>>
>>>>>
>>>>>
>>>>>> Thank you.  I was going to comment on the v1 to not disable 
>>>>>> buildpaths.
>>>>>
>>>>> +1
>>>
>>>
>>>
>>>
>>>
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#19694): https://lists.yoctoproject.org/g/meta-ti/message/19694
> Mute This Topic: https://lists.yoctoproject.org/mt/118225330/6551054
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [reatmon@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS

Re: [master][PATCH v2 3/3] ti-jailhouse: Fix buildpaths QA warning

[Sadik]

On Wed, Mar 11, 2026 at 01:05 AM, Ryan Eatmon wrote:

>
> 
> 
> On 3/10/2026 12:58 PM, Andrew Davis via lists.yoctoproject.org wrote:
> > On 3/10/26 12:08 PM, Sadik via lists.yoctoproject.org wrote:
> >> On Tue, Mar 10, 2026 at 07:22 PM, Denys Dmytriyenko wrote:
> >>
> >>>
> >>> On Tue, Mar 10, 2026 at 01:58:45AM -0700, Sadik via 
> >>> lists.yoctoproject.org
> >>> wrote:
> >>>> On Tue, Mar 10, 2026 at 12:28 AM, Denys Dmytriyenko wrote:
> >>>>
> >>>>>
> >>>>> On Mon, Mar 09, 2026 at 12:08:36PM -0500, Ryan Eatmon via
> >>>>> lists.yoctoproject.org wrote:
> >>>>>>
> >>>>>>
> >>>>>> On 3/9/2026 12:01 PM, Mahammed Sadik Shaik wrote:
> >>>>>>> Add -ffile-prefix-map flags to KCFLAGS to remove build path
> >>>>>>> references from kernel module compilation, ensuring reproducible
> >>>>>>> builds and preventing absolute path leakage in binaries.
> >>>>>>>
> >>>>>>> This resolves buildpaths QA warnings during packaging.
> >>>>>>>
> >>>>>>> Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
> >>>>>>> ---
> >>>>>>>   meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc | 4 ++--
> >>>>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
> >>>>>>>
> >>>>>>> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>>> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>>>>> index 91076c9e..8308f0e5 100644
> >>>>>>> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>>>>> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> >>>>>>> @@ -80,8 +80,8 @@ USER_SPACE_CFLAGS = '${CFLAGS}
> >>>>> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
> >>>>>>>   TOOLS_SRC_DIR = "${S}/tools"
> >>>>>>> -EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> >>> CC="${CC}"
> >>>>> KDIR=${STAGING_KERNEL_BUILDDIR}"
> >>>>>>> -
> >>>>>>> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX}
> >>> CC="${CC}"
> >>>>> KDIR=${STAGING_KERNEL_BUILDDIR} \
> >>>>>>> +    KCFLAGS='-ffile-prefix-map=${STAGING_KERNEL_BUILDDIR}/=
> >>>>> -ffile-prefix-map=${STAGING_KERNEL_DIR}/='"
> >>>>>>>   do_compile() {
> >>>>>>>           oe_runmake V=1
> >>>>>>>   }
> >>>>>
> >>>>> Can you move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
> >>>>
> >>>> Thanks for the review Denys, Apologies for multiple replies was 
> >>>> facing some
> >>> issues with relply all in mail.
> >>>>
> >>>> Moving V=1 into EXTRA_OEMAKE is fine, but we can't remove the 
> >>>> do_compile()
> >>> override. . This is insufficient for jailhouse, which requires building:
> >>>> 1. Kernel modules (driver/jailhouse.ko)
> >>>> 2. Hypervisor binary (hypervisor/jailhouse.bin)
> >>>> 3. Userspace tools (tools/jailhouse, jailhouse-*)
> >>>> 4. Inmate demos (inmates/demos/*) — causing the install failure for all
> >>> the demos during the build.
> >>>>
> >>>> The do_compile() override is needed to run a plain oe_runmake which 
> >>>> hits
> >>> jailhouse's top-level Makefile and builds the full project.
> >>>
> >>> The default do_compile() does exactly that - calls oe_runmake:
> >>>
> https://git.openembedded.org/openembedded-core/tree/meta/classes-global/base.bbclass#n399
> >>
> >> Yeah you are right, that the default base_do_compile() calls 
> >> oe_runmake, which would work fine. But, the jailhouse recipe inherits 
> >> module bbclass,
> >> "inherit module python3native bash-completion deploy"
> >>   which overrides default do_compile() with module_do_compile. 
> >> resulting in compilation errors if do_compile override is removed.
> >> If I don't use the do-compile override I am still getting build 
> >> errors. I am unable to remove the module bbclass is required for 
> >> building jailhouse kernel modules.
> >>
> > 
> > Split out the kernel module building into its own recipe.
> 
> Agreed.

Yeah I am sending  an follow up patch for these changes, meanwhile this series is good to go right?

> 
> 
> > Andrew
> > 
> >>>
> >>>
> >>>> If necessary I can send an V3 by moving V=1 into EXTRA_OEMAKE, but that
> >>> doesn't serve our purpose of completely overriding the do_compile
> >>>> And also I couldn't find an existing bbclass that does "run the 
> >>>> top-level
> >>> Makefile and build everything."
> >>>>
> >>>>>
> >>>>>
> >>>>>> Thank you.  I was going to comment on the v1 to not disable 
> >>>>>> buildpaths.
> >>>>>
> >>>>> +1
> >>>
> >>>
> >>>
> >>>
> >>>
> > 
> > 
> > 
> > 
> > 
> 
> -- 
> Ryan Eatmon                reatmon@ti.com
> -----------------------------------------
> Texas Instruments, Inc.  -  LCPD  -  MGTS
>