All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: yocto@lists.yoctoproject.org, pkl2000us@gmail.com
Subject: Re: [yocto] Custom Kernel Recipe Compilation Error.
Date: Tue, 8 Jul 2025 11:06:09 +0200	[thread overview]
Message-ID: <0a3017ff-19f4-4e18-a338-32450acfa8ee@gmail.com> (raw)
In-Reply-To: <CANVomh9M6p+aQS682mfHv-kkF7D-K3ZTUBcXsxBnSv2QgQ8B4g@mail.gmail.com>

On 7/7/25 22:10, C Larbi via lists.yoctoproject.org wrote:
> Hello all
> I am a newbie to the yocto project and on a journey to understand the basics.
>
> My reference hardware for my learning journey is the Orange pi 3b (RK3566 soc)
>
> I have created a bsp layer containing my machine configuration and a
> recipe to build a custom kernel.
>
> The kernel recipe build throws an error on the "do_compile_kernelmodules" task.
> Before writing this, i went through the manual process of compiling
> the same kernel source on my machine and i was able to produce a
> vmlinux file and build the modules.
>
> This is the error from the yocto build process.
>
> |   GEN     Makefile
> |   CALL    /home/cerezo/yocto/tut/poky/build/tmp/work-shared/opi3b/kernel-source/scripts/checksyscalls.sh
> |   CC [M]  drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd/aiutils.o
> |   CC [M]  drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd/siutils.o
> | /home/cerezo/yocto/tut/poky/build/tmp/work-shared/opi3b/kernel-source/drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd/aiutils.c:44:10:
> fatal error: typedefs.h: No such file or directory
> |    44 | #include <typedefs.h>
> |       |          ^~~~~~~~~~~~
> | compilation terminated.
> | make[7]: *** [/home/cerezo/yocto/tut/poky/build/tmp/work-shared/opi3b/kernel-source/scripts/Makefile.build:250:
> drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd/aiutils.o] Error 1
> | make[7]: *** Waiting for unfinished jobs....
>
> Will really appreciate if i can get some pointers as to what i may be
> doing wrong.

This seems to be a recurring problem with this particular vendor kernel
unfortunately. Take a look at this patch which solves the same issue on
a different branch:
https://github.com/riscv/meta-riscv/blob/master/recipes-kernel/linux/linux-orangepi/orangepi-rv2/bcmdhd-fix-typedefs-header-not-found.patch

I think adapting this to your branch should solve your problem too.


>
> KERNEL RECIPE
> https://github.com/AccraNET/meta-orspace-orangepi3b/blob/main/recipes-kernel/linux/linux-orangepi.bb
>
> MACHINE CONFIGURATION
> https://github.com/AccraNET/meta-orspace-orangepi3b/blob/main/conf/machine/opi3b.conf
>
> Best Regards
> Cerezo
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#65623): https://lists.yoctoproject.org/g/yocto/message/65623
> Mute This Topic: https://lists.yoctoproject.org/mt/114034987/6084445
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



  reply	other threads:[~2025-07-08  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 20:10 Custom Kernel Recipe Compilation Error C Larbi
2025-07-08  9:06 ` Gyorgy Sarvari [this message]
2025-07-09  9:32   ` [yocto] " C Larbi
2025-07-10  8:36   ` Paul Gortmaker
2025-07-10 14:35     ` C Larbi
2025-07-11 17:20       ` Paul Gortmaker
2025-07-14 16:18 ` Quentin Schulz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0a3017ff-19f4-4e18-a338-32450acfa8ee@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=pkl2000us@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.