Don't use:
S = "${WORKDIR}"
move it to separate directory and it will work fine.
On Wed, Apr 24, 2024 at 6:41 PM lukas.palme via lists.openembedded.org
<[email protected]> wrote:
>
> Hello openembedded community!
>
> I hope this is the right place to ask this question,
> https://wiki.yoctoproject.org/wiki/Pseudo_Abort brought me here.
>
> I have a custom recipe which builds fine on the first build, but fails on
> subsequent builds in the do_install step:
>
> ERROR: Task
> (/home/swarco/WindriverLinux22/build/../layers/meta-swarco/meta-vega/recipes-kernel/mymodule/mymodule.bb:do_install)
> failed with exit code '1'
> Pseudo log:
> path mismatch [3 links]: ino 78038 db
> '/home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/package/usr/src/debug/mymodule/1.0-r0/mymodule_public.h'
> req
> '/home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/mymodule_public.h'.
> Setup complete, sending SIGUSR1 to pid 12937.
>
> Yocto is the only one touching the files in between builds. Also the files
> questioned do exist with the noted inode:
>
> swarco@SWFPERWKS065:~/WindriverLinux22$ stat
> /home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/package/usr/src/debug/mymodule/1.0-r0/mymodule_public.h
> File:
> /home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/package/usr/src/debug/mymodule/1.0-r0/mymodule_public.h
> Size: 3146 Blocks: 8 IO Block: 4096 regular file
> Device: 820h/2080d Inode: 78038 Links: 3
> Access: (0644/-rw-r--r--) Uid: ( 1000/ swarco) Gid: ( 1000/ swarco)
> Access: 2024-04-24 18:17:21.182513722 +0200
> Modify: 2024-04-24 18:16:50.402199580 +0200
> Change: 2024-04-24 18:17:19.432495797 +0200
> Birth: 2024-04-24 18:11:59.419201062 +0200
>
> swarco@SWFPERWKS065:~/WindriverLinux22$ stat
> /home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/mymodule_public.h
> File:
> /home/swarco/WindriverLinux22/build/tmp-glibc/work/vegamx8-wrs-linux/mymodule/1.0-r0/mymodule_public.h
> Size: 3146 Blocks: 8 IO Block: 4096 regular file
> Device: 820h/2080d Inode: 78038 Links: 3
> Access: (0644/-rw-r--r--) Uid: ( 1000/ swarco) Gid: ( 1000/ swarco)
> Access: 2024-04-24 18:17:21.182513722 +0200
> Modify: 2024-04-24 18:16:50.402199580 +0200
> Change: 2024-04-24 18:17:19.432495797 +0200
> Birth: 2024-04-24 18:11:59.419201062 +0200
>
> This is the recipe mymodule.bb:
>
> SUMMARY = "mymodule"
> DESCRIPTION = "Recipe for building a mymodule Linux kernel module"
> LICENSE = "GPL-2.0-only"
> LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6"
>
> inherit module
>
> SRC_URI = "file://Makefile \
> file://mymodule_core.c \
> file://mymodule.h \
> file://mymodule_public.h \
> file://mymodule_remote_public.h \
> "
>
> S = "${WORKDIR}"
>
> do_install:append() {
> install -d ${D}${includedir}
> install -m 0755 ${S}/mymodule_public.h ${D}${includedir}/
> }
> # The inherit of module.bbclass will automatically name module packages with
> # "kernel-module-" prefix as required by the oe-core build environment.
>
> RPROVIDES:${PN} += "kernel-module-mymodule"
> FILES:${PN}-dev += "${includedir}/*"
>
> I am doing nothing unusual here.
>
> Additional notes to my setup:
>
> Host machine: Ubuntu 22.04 on WSL
> Linux kernel: linux-imx (NXP)
>
> Does someone have an idea what is happening here? Any help is appreciated!
>
> Kind regards,
>
> Lukas Palme
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#198690):
https://lists.openembedded.org/g/openembedded-core/message/198690
Mute This Topic: https://lists.openembedded.org/mt/105713810/21656
Mute
#pseudo:https://lists.openembedded.org/g/openembedded-core/mutehashtag/pseudo
Mute
#kirkstone:https://lists.openembedded.org/g/openembedded-core/mutehashtag/kirkstone
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
