From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Bitbake dependency failure with git fetcher
Date: Sat, 08 Oct 2011 17:06:47 +0200 [thread overview]
Message-ID: <4E906707.3000005@eukrea.com> (raw)
In-Reply-To: <5F487E45-9539-4DE6-AF5F-5664351F86C9@dominion.thruhere.net>
Hi,
Le 08/10/2011 12:27, Koen Kooi a écrit :
>
> Op 8 okt. 2011, om 10:08 heeft Richard Purdie het volgende geschreven:
>
>> On Sat, 2011-10-08 at 01:29 +0200, Koen Kooi wrote:
>>> Everytime openssl and a git recipe get changed at the same time, I end
>>> up with:
>>>
>>> | /angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/git.real: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
>>>
>>> Why is bitbake not resolving the git-native -> openssl-native dep
>>> before invoking the git fetcher?
>>
>> I suspect you're using rm_work?
>
> Yes I do
same thing here, and same issue when updating git.
Eric
next prev parent reply other threads:[~2011-10-08 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 23:29 Bitbake dependency failure with git fetcher Koen Kooi
2011-10-08 8:08 ` Richard Purdie
2011-10-08 10:27 ` Koen Kooi
2011-10-08 15:06 ` Eric Bénard [this message]
2011-10-19 2:00 ` Joel A Fernandes
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=4E906707.3000005@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-core@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