From: Jack <ostroffjh@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Building Bedrockdb in cygwin
Date: Mon, 13 May 2019 18:48:00 -0000 [thread overview]
Message-ID: <CSNLP7TH.D7FQMYDZ.AT2HLPXU@UOMQDYVY.E62MSTDE.G5TNA5M5> (raw)
In-Reply-To: <DB7PR01MB538676A591DE01AAC66B13A4DE0F0@DB7PR01MB5386.eurprd01.prod.exchangel abs.com> (from jicman@outlook.com on Mon May 13 14:17:01 2019)
On 2019.05.13 14:17, Jose Isaias Cabrera wrote:
>
> Greetings!
>
> I am trying to build Bedrockdb in cygwin. Running make gives me this
> output:
>
> e608313@HOR711318E ~/Bedrock-master
> $ make
> git submodule init
> git submodule update
> cd mbedtls && git checkout -q c49b808ae490f03d665df5faae457f613aa31aaf
> fatal: reference is not a tree:
> c49b808ae490f03d665df5faae457f613aa31aaf
> make: *** No rule to make target 'mbedtls/library/libmbedcrypto.a',
> needed by 'libstuff/libstuff.d'. Stop.
>
> Any thoughts? I tried getting help from the bedrock group, but their
> google group has not been updated since 2017. So, I thought that I
> would try it here. Any guidance would be appreciated. Thanks.
>
> josé
I know nothing about Bedrock, but I'd ask what you did before running
"make." Did you do ./configure? Is there perhaps an autogen.sh to
run? In applications I've compiled which use git submodules, it's
often been autogen.sh which actually initialized them, which must be
done before updating them, and I seem to recall that it's something
that needs to be done prior to the "git submodule init".
Jack
>
>
>
>
> From: Jose Isaias Cabrera
> Sent: Wednesday, May 8, 2019 03:00 PM
> To: cygwin@cygwin.com
> Subject: Building Bedrockdb in cygwin
>
>
> Greetings.
>
> Has anyone tried to build Bedrockdb[1] in cygwin? Thanks.
>
> josé
>
>
> [1] https://bedrockdb.com/
> Bedrock by Expensify - Bedrock – Rock-solid distributed
> data<https://bedrockdb.com/>
> Bedrock – Rock-solid distributed data. Bedrock is a simple, modular,
> WAN-replicated, Blockchain-based data foundation for global-scale
> applications.
> bedrockdb.com
>
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-05-13 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 19:00 Jose Isaias Cabrera
2019-05-13 18:17 ` Jose Isaias Cabrera
2019-05-13 18:48 ` Jack [this message]
2019-05-13 19:01 ` Jose Isaias Cabrera
2019-05-13 19:09 ` Achim Gratz
2019-05-13 19:24 ` Jose Isaias Cabrera
2019-05-13 19:21 ` Jack
2019-05-13 20:15 ` Jose Isaias Cabrera
2019-05-13 20:23 ` Jack
2019-05-13 20:37 ` Jose Isaias Cabrera
2019-05-13 21:26 ` Jack
2019-05-13 21:58 ` Jose Isaias Cabrera
2019-05-14 3:29 ` Brian Inglis
2019-05-14 13:51 ` Jose Isaias Cabrera
2019-05-14 16:18 ` Brian Inglis
2019-05-14 16:27 ` Jose Isaias Cabrera
2019-05-14 17:11 ` Jose Isaias Cabrera
2019-05-14 22:17 ` Csaba Ráduly
2019-05-15 12:24 ` Jose Isaias Cabrera
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=CSNLP7TH.D7FQMYDZ.AT2HLPXU@UOMQDYVY.E62MSTDE.G5TNA5M5 \
--to=ostroffjh@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).