From: JC <jc@vtkloud.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: ruby-dev has a lot of unresolved dependencies (was : requires libcrypto which is not present ??)
Date: Sat, 07 Sep 2013 14:52:48 +0200 [thread overview]
Message-ID: <522B21A0.9000305@vtkloud.com> (raw)
In-Reply-To: <5229F9F4.6030903@vtkloud.com>
Hi,
I auto-follow on this question:
On 06/09/2013 17:51, JC wrote:
>
> I'm trying to install ruby-dev (in order to be able to apply some
> passenger features). Passenger requires ruby-dev
>
> ruby-dev has indeed been built but when I'm trying to install it, I
> can't:
>
> root@qemuarm:~# smart install ruby-dev
> rpmdb: BDB0113 Thread/proc
> Computing transaction...
> error: Can't install ruby-dev-1.9.3+p194-r1.0@armv5te: no package
> provides libcrypto-dev
>
libcrypto-dev is not present because openssl does not generate it (it's
empty, the lib is taken by libcrypto package)
I hacked (may be I'll clean) it by modifying the openssl recipe allowing
libcrypto-dev to be empty.
Then I ran into the same error with libssl-dev so the "hack" is now :
PACKAGES =+ " libcrypto-dev libssl-dev"
ALLOW_EMPTY_libcrypto-dev = "1"
ALLOW_EMPTY_libssl-dev = "1"
Now the next error is :
Computing transaction...error: Can't install
ruby-dev-1.9.3+p194-r1.0@armv5te: no package provides ncurses-libtinfo-dev
That one is trickier. It seems that libtinfo is provided by the package
ncurses-terminfo, not ncurses-libtinfo.
I'm really confused about the status of meta-ruby. I assume I'm not the
only one willing to install ruby-dev am I ?
Is there some basic mistake I made ?
How can yocto even generate the package if it cannot satisfy these
dependencies by itself ?
Thanks for your help... I'm really puzzled now :(
Regards
Jay
prev parent reply other threads:[~2013-09-07 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 15:51 ruby-dev requires libcrypto which is not present ?? JC
2013-09-07 12:52 ` JC [this message]
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=522B21A0.9000305@vtkloud.com \
--to=jc@vtkloud.com \
--cc=yocto@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 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.