Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 09:08:45 +0100	[thread overview]
Message-ID: <1318061333.8533.58.camel@ted> (raw)
In-Reply-To: <D3F85958-4E8C-4D2C-B8BD-C7AF341FAF47@dominion.thruhere.net>

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?

Cheers,

Richard




  reply	other threads:[~2011-10-08  8:14 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 [this message]
2011-10-08 10:27   ` Koen Kooi
2011-10-08 15:06     ` Eric Bénard
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=1318061333.8533.58.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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