Hello Alex,
Your guess was right. In principle, the messages in the log.do_package file
were also correct.
I overlooked the whole time that the link for a rtl8723 file points to a
rtl8821 file.
My bbappend now looks like this:
FILES:${PN}-rtl8723 += “ ${nonarch_base_libdir}/firmware/rtl_bt/rtl8723*.bin”
PACKAGES =+ “${PN}-rtlbt-common”
FILES:${PN}-rtlbt-common =
“${nonarch_base_libdir}/firmware/rtl_bt/rtl8821c_config.bin”
RDEPENDS:${PN}-rtl8821 += “${PN}-rtlbt-common”
RDEPENDS:${PN}-rtl8723 += “${PN}-rtlbt-common”
Thanks again for your support!
Best regards,
Matthias
-----Ursprüngliche Nachricht-----
Von: Alexander Kanavin <alex.kana...@gmail.com>
Gesendet: Dienstag, 22. Oktober 2024 11:11
An: Matthias Klein <matthias.kl...@optimeas.de>
Cc: yocto@lists.yoctoproject.org
Betreff: Re: [yocto] Strange problem when extending the linux-firmware package
I guess your firmware-specific package contains a symlink to something in the
'main' linux-firmware package? This is where the dependency comes from. Then
you need to figure out why it goes to the main package and not to the specific
one.
Check what goes where in ${WORKDIR}/package-split/. Then again use bitbake -e
to see the rules for FILES for various packages.
Alex
On Tue, 22 Oct 2024 at 11:07, Matthias Klein <matthias.kl...@optimeas.de> wrote:
>
> Hello Alex,
>
> I have made a small step forward.
>
> Even without my customization, some packages are “broken” in terms of
> dependencies.
> The cause lies in generated links for which messages appear in log.do_package:
>
> DEBUG: Executing python function package_fixsymlinks ...
> DEBUG: linux-firmware-qcom-vpu-1.0 contains dangling link
> /usr/lib/firmware/qcom/vpu/vpu20_p4.mbn
> DEBUG: target found in linux-firmware
> ...
>
> This changes the dependencies in the ipk files:
> Depends: linux-firmware, linux-firmware-qcom-license
> Source: linux-firmware_20240909.bb
>
> Normal packages have no dependency on linux-firmware:
> Depends: linux-firmware-rtl-license
> Source: linux-firmware_20240909.bb
>
> In an older scarthgap with linux-firmware version 20240312 much less of these
> links were recognized as “dangling”.
>
> Do you have any idea why the mechanism with the links no longer works
> properly and leads to the dependencies on linux-firmware?
>
> Best regards,
> Matthias
>
> -----Ursprüngliche Nachricht-----
> Von: Alexander Kanavin <alex.kana...@gmail.com>
> Gesendet: Montag, 21. Oktober 2024 12:16
> An: yocto@lists.yoctoproject.org; Matthias Klein
> <matthias.kl...@optimeas.de>
> Betreff: Re: [yocto] Strange problem when extending the linux-firmware
> package
>
> You need to run 'bitbake -e linux-firmware' and check how RDEPENDS is formed.
>
> Alex
>
> On Mon, 21 Oct 2024 at 10:33, Matthias Klein via lists.yoctoproject.org
> <matthias.klein=optimeas...@lists.yoctoproject.org> wrote:
> >
> > Hello,
> >
> >
> >
> > a few months ago I added Bluetooth firmware via a linux-firmware_%.bbappend
> > file with the following line:
> >
> >
> >
> > FILES:${PN}-rtl8723 += “
> > ${nonarch_base_libdir}/firmware/rtl_bt/rtl8723*.bin”
> >
> >
> >
> > I had added the linux-firmware-rtl8723 package to my image. Until a few
> > days ago, this worked wonderfully.
> >
> > Since about October 18 or 19, adding the files
> > ${nonarch_base_libdir}/firmware/rtl_bt/rtl8723*.bin causes all firmware
> > packages to end up in the image.
> >
> > In a way that is unexplainable to me, the package linux-firmware-rtl8723
> > seems to get a dependency on linux-firmware, which causes all firmware
> > packages to end up in the image.
> >
> >
> >
> > Does anyone have any idea what is happening here?
> >
> >
> >
> > Best regards,
> >
> > Matthias
> >
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64084): https://lists.yoctoproject.org/g/yocto/message/64084
Mute This Topic: https://lists.yoctoproject.org/mt/109128695/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
