From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: starting a quest to make some ruby recipes buildable/installable
Date: Sat, 27 Jun 2020 06:42:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2006270636560.2237067@localhost.localdomain> (raw)
followup to yesterday's cry for help, i've built a
core-image-minimal for x86_64 using "zeus" layers and, at this point,
i'm simply going to start trying to bitbake and IMAGE_INSTALL_append
various ruby gems.
things did not start out well as the very first attempt blew up:
$ bitbake json
but it appears that (zeus-supplied) version 1.8.3 of that recipe has
known issues, so i grabbed the recipe from
meta-cloud-services/meta-openstack (where, for some baffling reason,
many of these ruby gems live), tweaked it thusly:
BPV = "2.3.0"
SRCREV = "92cf5c451a6ec0f3a00e291eb909e57cf38fbea4"
LIC_FILES_CHKSUM = "file://LICENSE;md5=8a960b08d972f43f91ae84a6f00dcbfb"
whereupon it failed on the packaging step thusly:
ERROR: json-2.3.0-r0 do_package_qa: QA Issue:
/usr/lib/ruby/gems/2.5.0/gems/json-2.3.0/lib/json/ext/generator.so
contained in package json requires libcrypt.so.2()(64bit), but no
providers found in RDEPENDS_json? [file-rdeps]
ERROR: json-2.3.0-r0 do_package_qa: QA run found fatal errors. Please
consider fixing them.
ERROR: Logfile of failure stored in:
/home/rpjday/oe/builds/zeus/chef/tmp/work/core2-64-poky-linux/json/2.3.0-r0/temp/log.do_package_qa.2236511
ERROR: Task
(/home/rpjday/oe/dist/layers/meta-cloud-services/meta-openstack/recipes-devtools/ruby/json_git.bb:do_package_qa)
failed with exit code '1'
i don't know enough about ruby recipes to know how to resolve that
libcrypt.so packaging error, so i'm open to suggestions. in the
meantime, i'm going to work my way through numerous recipes and see
how many i can get to build.
rday
reply other threads:[~2020-06-27 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.21.2006270636560.2237067@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox