Out-of-tree module errors installing its udev rule
I've got a strange (to me) problem with the recipe for an out-of-tree kernel module. I'm trying to add a udev rule for the driver - in itself the recipe does the build ok, but building the full rootfs image throws up a "QA Issue:
linmux: Files/directories were installed but not shipped in any package" error.
I have
inherit module
.
SRC_URI += " file://65-linmuxcfg-devnode.rules "
S = "${WORKDIR}"
FILES_{PN} += "${base_libdir}/udev/rules.d/65-linmuxcfg-devnode.rules"
do_install_append(){
install -d ${D}${base_libdir}/udev/rules.d/
install -m 0644 ${WORKDIR}/65-linmuxcfg-devnode.rules${D}${base_libdir}/udev/rules.d
}
Is this because it's an out-of-tree module, or some other [obvious] mistake?
Thanks
Quoted 25 lines · On 13 February 2017 at 15:56, <[email protected]> wrote:
inherit module
…
SRC_URI+= " file://65-linmuxcfg-devnode.rules "S = "${WORKDIR}"
FILES_{PN} += "${base_libdir}/udev/rules.d/65-linmuxcfg-devnode.rules"
do_install_append(){
install -d ${D}${base_libdir}/udev/rules.d/ install -m 0644 ${WORKDIR}/65-linmuxcfg-devnode.rules${D}${base_libdir}/udev/rules.d
Quoted 10 lines
}
Is this because it’s an out-of-tree module, or some other [obvious] mistake?
Thanks
If that's a literal copy and paste then you forgot the $ in FILES_${PN}.
Also udev rules go into ${nonarch_base_libdir}.
Ross
Quoted 21 lines · Ross
Quoted 16 lines · On 13 February 2017 at 15:56, <[email protected]> wrote:
inherit module
…
SRC_URI+= " file://65-linmuxcfg-devnode.rules "S = "${WORKDIR}"
FILES_{PN} += "${base_libdir}/udev/rules.d/65-linmuxcfg-devnode.rules"
do_install_append(){
install -d ${D}${base_libdir}/udev/rules.d/
install -m 0644 ${WORKDIR}/65-linmuxcfg-devnode.rules ${D}${base_libdir}/udev/rules.d
Quoted 8 lines
Quoted 5 lines
}
Is this because it’s an out-of-tree module, or some other [obvious] mistake?
Thanks
If that's a literal copy and paste then you forgot the $ in FILES_${PN}.
Sigh...... "wood for the trees"...... thanks Ross.....! :S
Quoted 2 lines
Also udev rules go into ${nonarch_base_libdir}.
Oh ok, hadn't encounter that var. What's the reasoning? (i.e. where would that be pointing in comparison to ${base_libdir}
Quoted 1 line
Ross
Quoted 5 lines · Colin Helliwell
Quoted 1 line
Also udev rules go into ${nonarch_base_libdir}.
Oh ok, hadn't encounter that var. What's the reasoning? (i.e. where would that be pointing in comparison to ${base_libdir}
udev rules are arch-independent so udev looks in /lib, whereas $libdir can change depending on multilib (it may be /lib64).
Ross