From: Worik Stanton <worik.stanton@tirotech.co.nz>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: yocto@lists.yoctoproject.org, Khem Raj <raj.khem@gmail.com>
Subject: Re: [yocto] Warning about "no-recipes"
Date: Fri, 10 May 2024 16:27:04 +1200 [thread overview]
Message-ID: <CANuMBWFAj7k1EaKEjGdmSP0WiPZg=0H=vvmS1g3sJMjhL8_-ng@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj8fD0sqYWum7Otyy=dZezCuk53AV_Vj1sMoZG5zo38Eug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3936 bytes --]
Thank you for everybodies' help
Following the suggestions I made the (in hindsight) obvious discovery that
the warning is generated in a recipe from somewhere else, namely
"meta-toradex-nxp". The person who built this system has pinned
meta-toradex-nxp to a particular commit from 2021. I do not know what they
were thinking, I am fairly confident they knew what they were doing.
I will leave it there as this is a warning. While it is an otherwise clean
build, and I crave clean builds, there are actually problems that are real
roadblocks that I need to fix (another subject)
Next time I hope I can provide the necessary information faster. It is
difficult to know what to provide as I am diving into the middle of two
large projects that use different styles.
Once again thank you for your help.
Worik
> I expect it is that latter directory my warning is originating from.
>
> The warning is:
> WARNING: No recipes in default available for:
>
> /home/yocto/thisbuild-yocto/layers/openembedded-core/../meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
>
> What this means is bitbake is looking for recipe file called
> gstreamer1.0-plugins-base_1.20.0.imx.bb and can't find it anywhere in
> configured layers. This can happen for multiple reasons:
>
> 1. That recipe file used to be available, but someone updated the
> layer containing it to a different revision where the file was either
> removed or updated to a different version (which is encoded into the
> filename). You need to find out whether that has happened, and either
> revert to the original revision, or rename the bbappend to match. Try
> using 'find' command with a generous wildcard expression to see what
> would roughly match in the overall tree.
>
>
>
Yes, this:
yocto@toradex-build:~/toradex-yocto$ find . -name
"gstreamer*-plugins-base*.bb"
./layers/openembedded-core/meta/recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.5.bb
./layers/meta-freescale/recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.3.imx.bb
My naive view is that I need to find where it is requiring
"recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bb" and
change that to "recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.5.imx.bb"
This is in somebody else's repository, we import it with a recursive git
clone pinned at a particular commit (it is using a git idiom
3. The file is not available in any of the layers. You need to go over
> the list of required layers in documentation for meta-this-build-nxp,
> and find everything you can about layers it depends on, and perhaps
> look at commit history for bbappend as well to find out
> which layer it's meant to be used with.
>
>
"thisbuild-nxp" is "toradex-nxp.
Reading the Readme it depends on:
yocto@toradex-build:~/toradex-yocto$ grep URI
layers/meta-toradex-nxp/README
URI: git://git.openembedded.org/bitbake
URI: git://git.openembedded.org/openembedded-core
URI: git://git.yoctoproject.org/meta-freescale
URI: https://github.com/Freescale/meta-freescale-3rdparty.git
URI: git://git.toradex.com/meta-toradex-bsp-common
Is that where I start with "layers it depends on"?
The commit history seems to indicate "gstreamer1.0-plugins-base" is the
layer if is supposed to be used with:
yocto@toradex-build:~/toradex-yocto/layers/meta-toradex-nxp$ git log --
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
commit bd7f3d8596e984d42afa1c9b30fd635fb02fc040
Author: Max Krummenacher <max.krummenacher@toradex.com>
Date: Mon Sep 19 14:20:44 2022 +0200
gstreamer1.0-plugins-base: follow version change
The code the patch removes is still present, keep the patch also
with the new version.
Related-to: ELB-4665
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Without a specific look at your setup it's hard to say much more.
>
> Alex
>
[-- Attachment #2: Type: text/html, Size: 7275 bytes --]
next prev parent reply other threads:[~2024-05-10 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 1:28 Warning about "no-recipes" Worik Stanton
2024-05-08 1:38 ` [yocto] " Khem Raj
2024-05-08 1:53 ` Worik Stanton
2024-05-08 2:05 ` Khem Raj
2024-05-08 3:38 ` Worik Stanton
2024-05-08 5:44 ` Khem Raj
2024-05-08 21:18 ` Worik Stanton
2024-05-09 16:42 ` Alexander Kanavin
2024-05-10 4:27 ` Worik Stanton [this message]
2024-05-08 8:20 ` Alexander Kanavin
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='CANuMBWFAj7k1EaKEjGdmSP0WiPZg=0H=vvmS1g3sJMjhL8_-ng@mail.gmail.com' \
--to=worik.stanton@tirotech.co.nz \
--cc=alex.kanavin@gmail.com \
--cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).