From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-devel@lists.openembedded.org>
Subject: bitcoin recipe
Date: Thu, 7 Aug 2014 14:29:14 +0200 [thread overview]
Message-ID: <53E3711A.7000002@topic.nl> (raw)
Just out of curiousity, I tried to build bitcoin for an ARM target using bitbake.
Googling a bit reveils tons of claims of people having compiled it for their
board (e.g. the raspberry pi), and very likely, some of them were using OE.
Somewhere, someone knows how to do this...
Strangely, i couldn't find a recipe online. So i did a quick try with this recipe:
SUMMARY = "Bitcoin miner"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=9eef91148a9b14ec7f9df333daebc746"
# https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md
DEPENDS += "boost db"
SRCREV = "5e94d0036a76ea9d63e4ed17b12554caef7f55da"
SRC_URI = "git://github.com/bitcoin/bitcoin/"
S = "${WORKDIR}/git"
inherit pkgconfig autotools
# Workarounds...
EXTRA_OECONF += "\
--with-incompatible-bdb \
--with-boost-libdir=${STAGING_LIBDIR} \
"
This didn't get very far, apparently the bitcoin people aren't very aware of
crosscompiling...
It fails to configure with a cryptic message like this:
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
configure: error: Could not find a version of the boost_chrono library!
A similar one about the boost_system library was fixed using the
"--with-boost-libdir=${STAGING_LIBDIR}" hack, but this one has me baffled.
Met vriendelijke groet / kind regards,
Mike Looijmans
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt FPGA experts
http://topic.nl/vacatures/word-jij-onze-nieuwe-fpga-expert/
reply other threads:[~2014-08-07 12:34 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=53E3711A.7000002@topic.nl \
--to=mike.looijmans@topic.nl \
--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 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.