From: "Michael Lynch" <mlynch@hi-techniques.com>
To: bitbake-devel@lists.openembedded.org
Subject: Dependencies ?
Date: Fri, 24 May 2024 06:57:42 -0700 [thread overview]
Message-ID: <lfcT.1716559062178660500.wc5p@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
Hi all,
I hope this is the correct place to ask this. I'm in the process of updating from yocto kirkstone branches to yocto scarthgap branches and ran into an issue that brought up a question about yocto/bitbake dependencies. My normal work flow for updating is to start with an empty directory tree, clone all of the layers, checkout the specific branch (scarthgap) for each and do a fresh build of core-image-minimal. That all went smoothly except for a couple of recipes in the meta-intel layer. After messing around with it a bit and not finding a solution on my own I posted a message in the meta-intel forum. The response was that the recipes I was trying to build are not compatible with the version of clang from the scarthgap branch of meta-clang and that I needed to use the mickeldore branch of meta-clang. So here are my questions, first, is there some way to find out if a recipe depends on specific versions of items? Second, is there a way for yocto/bitbake to inform the user when there is a specific version dependency issue instead of the recipe simply failing to build? Thanks and mostly just curious.
-- Mike
[-- Attachment #2: Type: text/html, Size: 1206 bytes --]
next reply other threads:[~2024-05-24 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:57 Michael Lynch [this message]
2024-05-24 14:14 ` [bitbake-devel] Dependencies ? Quentin Schulz
2024-05-24 14:59 ` Alexander Kanavin
2024-05-24 15:33 ` Michael Lynch
2024-05-24 17:06 ` [bitbake-devel] " Alexander Kanavin
2024-05-27 3:50 ` Mittal, Anuj
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=lfcT.1716559062178660500.wc5p@lists.openembedded.org \
--to=mlynch@hi-techniques.com \
--cc=bitbake-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.