From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: DISTRO_PR, ipkg dependencies, and meta toolchains...
Date: Sat, 01 Nov 2008 01:11:15 -0500 [thread overview]
Message-ID: <490BF303.1030701@dls.net> (raw)
Consider the control data for openssl-dev (exerpts):
Package: openssl-dev
Version: 0.9.7g-r7.1
...
Depends: openssl (= 0.9.7g-r7), libcrypto0.9.7, libssl0.9.7
Recommends: libc6-dev, libgcc-dev, libcrypto-dev...
Note in particular the openssl-dev version number, which has the
DISTRO_PR appended to make it "-r7.1" instead of just "-r7".
But in the dependencies, it lists the specific version of the
corresponding runtime -- without the DISTRO_PR. And of course, that
specific version doesn't exist (or rather, if it exists in someone's
environment, it would be a left-over ipkg from before the DISTRO_PR was
added).
One place this bites us is in the SDK assembling (bitbake
meta-toolchain-<whatever>):
| Collected errors:
| * ERROR: Cannot satisfy the following dependencies for
task-fso-toolchain-target:
| * openssl (= 0.9.7g-r7) *
Poking about I can find a place in the appropriate bbclass files to hack
things up so that my specific problem will be resolved -- but I'd prefer
that someone who understands just how much of the rdepends/rrecommends
needs this treatment offer some advice first. (And of course, I should
warn anyone who cares that I know Perl far better than Python, a fact
that would almost certainly end up reflected in the patch I would write!)
Mike (mwester)
next reply other threads:[~2008-11-01 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 6:11 Mike (mwester) [this message]
2008-11-03 2:19 ` [RFC] Re: DISTRO_PR, ipkg dependencies, and meta toolchains Mike (mwester)
2008-11-03 4:30 ` Tom Rini
2008-11-03 12:47 ` Holger Freyther
2008-11-03 13:28 ` Otavio Salvador
2008-11-03 14:45 ` Mike (mwester)
2008-11-03 17:55 ` Otavio Salvador
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=490BF303.1030701@dls.net \
--to=mwester@dls.net \
--cc=openembedded-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox