Yup, thank you Bruce:

Using
IMAGE_FSTYPES_remove += "wic"

Didn't do it for me, but

IMAGE_TYPES_remove += "wic"

did the trick. 

I would recommend that you go for a systemd drop-in file [1].
That would be something like a small snippet placed to /etc/systemd/system/dbus-org.bluez.service/override.conf

In that file place something like
[Service]
ExecStart=
ExecStart=<new command line with your custom options>

this way you don't need to alter the upstream recipe with weird sed hacks or similar.

This drop-in file could be packaged by any recipe or bbappend.

[1] https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

Are you able to resolve this issue ? I am seeing the similar issue
p: cannot stat ‘Module.symvers’: No such file or directory
WARNING: /home/jojan.vazhaeparampil/workspace/distro/build/tmp/work/cyclone5-poky-linux-gnueabi/linux-altera/5.8+gitAUTOINC+eb446787ab-r0/temp/run.do_shared_workdir.21085:1 exit 1 from 'cp Module.symvers $kerneldir/'

On Mon, Dec 28, 2020 at 7:12 PM Howard <howard.egan@...> wrote:

Hi:

Was wondering if there was a way to exclude wic image from being built.

If you remove "wic" from the IMAGE_TYPES, it won't be built.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-IMAGE_TYPES

Bruce

Many thanks, and Happy New year.
Howard

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

On Mon, Dec 28, 2020 at 2:06 PM p32 via lists.yoctoproject.org
<p32=tuta.io@...> wrote:

Hello,

The execution of "make scripts prepare" did actually solve the issue, thank you very much for your help!

However, the need to manually execute this command on the target platform made me look into the kernel-devsrc recipe (https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/kernel-devsrc.bb?h=zeus) to see if it is possible to let the build host execute this step. Some comments imply that this is the case. Consider, for instance, the one in line 257:

Ensure we don't race against "make scripts" during cpio

Unfortunately, I was unable to figure out how to do this. Is there a way to let the recipe trigger this step automatically?

Nope. There is no way to do this on the build host. Not without
complex use of qemu-user to generate and package for the target
architecture. We cannot package the output of scripts in the target
package, since it matches the host architecture and this will trigger
a QA error.

If you happen to be x86 build host and x86 target (or ARM/ARM), you
can partially get away with just invoking the steps .. but this needs
to be in your own layer and is a hack, and not appropriate for core.

About 4 years ago, we were partially through doing this work, when the
person doing the qemu parts stopped working on the project. The
partial work is captured in bugzilla.

Cheers,

Bruce

Thanks!

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Hi:

Was wondering if there was a way to exclude wic image from being built.  

Many thanks, and Happy New year.
Howard

friend recently asked me for recommendations for entry-level,
linux-based drones whose software is generated by yocto project, so it
could be used as a learning experience. as in, the fun would be in
the creation and customization of the software, not just playing with
the drone.

i didn't have an immediate answer ... i recall that qualcomm has
linux-based drone components:

https://developer.qualcomm.com/hardware/qualcomm-flight-pro

and i'm aware of https://www.dronecode.org/, focused on OSS drone
projects.

any thoughts on linux-based drones where one would build the
software using yocto project?

rday

Hello,

The execution of "make scripts prepare" did actually solve the issue, thank you very much for your help!

However, the need to manually execute this command on the target platform made me look into the kernel-devsrc recipe (https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/kernel-devsrc.bb?h=zeus) to see if it is possible to let the build host execute this step. Some comments imply that this is the case. Consider, for instance, the one in line 257:

Ensure we don't race against "make scripts" during cpio

Unfortunately, I was unable to figure out how to do this. Is there a way to let the recipe trigger this step automatically?

Thanks!

On 12/28/20 7:33 AM, Raghu Icecraft Software Trainings wrote:

Paul,
Thanks for the reply.
I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1

Can you please let me know how to verify the yocto version running on
target.

You might have better luck on the meta-xilinx mailing list. They should
know the details for their BSP.

More info on Xilnx layers and a pointer to subscribe info to the mailing
list is here:

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto

Philip

Thanks,
Raghu

On Mon, Dec 28, 2020 at 5:31 PM Paul Barker <pbarker@...> wrote:

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to

find chpasswd utility because of which i am unable to set password to my
root-user.

Can you please let me know if the chpasswd utility has been changed or

modified please.

Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group

On 28.12.2020 15:40, p32 via lists.yoctoproject.org wrote:

Hello everyone,

I am using the Yocto-based build system provided by NXP (primarily via the meta-freescale layer) to create Linux images for an i.MX 8M board and would like to develop small kernel modules without going through the build process of the entire image after each modification. Therefore, I would prefer to compile the kernel modules on the target architecture and have added the following items to the IMAGE_INSTALL variable via my local.conf:
 - packagegroup-core-buildessential
 - kernel-modules
 - kernel-dev
 - kernel-devsrc

I then tried to follow the the official build instructions (https://www.kernel.org/doc/html/latest/kbuild/modules.html) on the target but was unable to create a kernel module:
imx8mqevk:~# make -C /lib/modules/$(uname -r)/build M=$PWD
make: Entering directory '/lib/modules/5.4.47-2.2.0+g5ec03d06f54e/build'
  CC [M]  /root/hello.o
In file included from ./include/linux/types.h:6,
                 from ./include/linux/list.h:5,
                 from ./include/linux/module.h:9,
                 from /root/hello.c:1:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
    [...]
compilation terminated.

Hi,

You need to run "make scripts prepare" in /usr/src/kernel before trying to compile kernel modules on target.

Ovidiu

What am I missing here? Is there something else I have to do on the target before I can compile kernel modules on the target?

For the sake of completeness: The build is based on the Zeus release and the following repo manifest file:
https://source.codeaurora.org/external/imx/imx-manifest/tree/imx-5.4.47-2.2.0.xml?h=imx-linux-zeus

Thanks!

Hello everyone,

I am using the Yocto-based build system provided by NXP (primarily via the meta-freescale layer) to create Linux images for an i.MX 8M board and would like to develop small kernel modules without going through the build process of the entire image after each modification. Therefore, I would prefer to compile the kernel modules on the target architecture and have added the following items to the IMAGE_INSTALL variable via my local.conf:
 - packagegroup-core-buildessential
 - kernel-modules
 - kernel-dev
 - kernel-devsrc

I then tried to follow the the official build instructions (https://www.kernel.org/doc/html/latest/kbuild/modules.html) on the target but was unable to create a kernel module:
imx8mqevk:~# make -C /lib/modules/$(uname -r)/build M=$PWD
make: Entering directory '/lib/modules/5.4.47-2.2.0+g5ec03d06f54e/build'
  CC [M]  /root/hello.o
In file included from ./include/linux/types.h:6,
                 from ./include/linux/list.h:5,
                 from ./include/linux/module.h:9,
                 from /root/hello.c:1:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
    [...]
compilation terminated.

What am I missing here? Is there something else I have to do on the target before I can compile kernel modules on the target?

For the sake of completeness: The build is based on the Zeus release and the following repo manifest file:
https://source.codeaurora.org/external/imx/imx-manifest/tree/imx-5.4.47-2.2.0.xml?h=imx-linux-zeus

Thanks!

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the chpasswd utility has been changed or modified please.

Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group