public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Building Bedrockdb in cygwin
@ 2019-05-08 19:00 Jose Isaias Cabrera
  2019-05-13 18:17 ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-08 19:00 UTC (permalink / raw)
  To: 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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-08 19:00 Building Bedrockdb in cygwin Jose Isaias Cabrera
@ 2019-05-13 18:17 ` Jose Isaias Cabrera
  2019-05-13 18:48   ` Jack
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 18:17 UTC (permalink / raw)
  To: cygwin


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é




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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 18:17 ` Jose Isaias Cabrera
@ 2019-05-13 18:48   ` Jack
  2019-05-13 19:01     ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Jack @ 2019-05-13 18:48 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 18:48   ` Jack
@ 2019-05-13 19:01     ` Jose Isaias Cabrera
  2019-05-13 19:09       ` Achim Gratz
  2019-05-13 19:21       ` Jack
  0 siblings, 2 replies; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 19:01 UTC (permalink / raw)
  To: Jack, cygwin


Jack, on Monday, May 13, 2019 02:47 PM, wrote...
>On 2019.05.13 14:17, Jose Isaias Cabrera wrote:
>I know nothing about Bedrock, but I'd ask what you did before running
>"make."  Did you do ./configure?

Thanks Jack for the prompt reply. No, there is no configure.


> Is there perhaps an autogen.sh to
>run?
No, no autogen.sh either.

>  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".

Thanks. This is what the README.md says,

$ cat README.md
# Expensify/Bedrock/
This public repo contains the Bedrock database server.  For more information on what that is, please see http://bedrockdb.com  The directories in this repo include:

* `/` - Contains the main Bedrock source
* `/docs` - Source for the public website (hosted via GitHub Pages): http://bedrockdb.com
* `/libstuff` - A general purpose C++ framework for cross-platform application development
* `/mbedtls` - The mbed TLS from here: https://tls.mbed.org/
* `/plugins` - The various plugins provided "out of the box" to Bedrock
* `/sqlitecluster` - The distributed transaction framework built atop sqlite: http://sqlite.org

So, it looks like the root (c49b808ae490f03d665df5faae457f613aa31aaf) does not exists... Thanks for the quick reply, though.

josé


--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  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
  1 sibling, 1 reply; 19+ messages in thread
From: Achim Gratz @ 2019-05-13 19:09 UTC (permalink / raw)
  To: cygwin

Jose Isaias Cabrera writes:
> * `/` - Contains the main Bedrock source
> * `/docs` - Source for the public website (hosted via GitHub Pages): http://bedrockdb.com
> * `/libstuff` - A general purpose C++ framework for cross-platform application development
> * `/mbedtls` - The mbed TLS from here: https://tls.mbed.org/
> * `/plugins` - The various plugins provided "out of the box" to Bedrock
> * `/sqlitecluster` - The distributed transaction framework built atop sqlite: http://sqlite.org
>
> So, it looks like the root (c49b808ae490f03d665df5faae457f613aa31aaf) does not exists... Thanks for the quick reply, though.

The submodule might look in the wrong place as clearly it is available here:

https://github.com/ARMmbed/mbedtls/commit/c49b808ae490f03d665df5faae457f613aa31aaf


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 19:01     ` Jose Isaias Cabrera
  2019-05-13 19:09       ` Achim Gratz
@ 2019-05-13 19:21       ` Jack
  2019-05-13 20:15         ` Jose Isaias Cabrera
  1 sibling, 1 reply; 19+ messages in thread
From: Jack @ 2019-05-13 19:21 UTC (permalink / raw)
  To: cygwin

On 2019.05.13 15:01, Jose Isaias Cabrera wrote:
> So, it looks like the root (c49b808ae490f03d665df5faae457f613aa31aaf)  
> does not exists... Thanks for the quick reply, though.
This issue is that at that point, the higher level make assumes that  
mbedtls is a git repository.

> cd mbedtls && git checkout -q c49b808ae490f03d665df5faae457f613aa31aaf
> fatal: reference is not a tree:  
> c49b808ae490f03d665df5faae457f613aa31aaf
I don't fully understand the git submodules, but something in the main  
git repository should have the info about where the git submodule's  
upstream repository is.  I'll guess here that you started by unpacking  
a tarball, and not cloning the Bedrock git repository, and that they  
failed to include the main .git folder in the tarball.  You'll probably  
either need to start by a git clone, or have them tell you how to  
manually specify the missing submodule information.

However, in doing a bit of searching, I just found a stackoverflow  
answer which includes "This is the most common problem with submodules.  
The commit that you are on in the outer repository has a reference to a  
commit in the submodule that someone did not push up yet. It's a  
dependency problem. Always push from the inside-out. This is most  
likely not something you did wrong, but someone else that's working in  
the repository. "    This implies that mbedtls does have a .git folder,  
but that particular commit is not yet available.  Try doing a "git  
pull" when in that subdirectory.  Otherwise, wait for a response from  
the Bedrock team.

Jack
--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 19:09       ` Achim Gratz
@ 2019-05-13 19:24         ` Jose Isaias Cabrera
  0 siblings, 0 replies; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 19:24 UTC (permalink / raw)
  To: Achim Gratz, cygwin


Achim Gratz, on Monday, May 13, 2019 03:09 PM, wrote...

>> So, it looks like the root (c49b808ae490f03d665df5faae457f613aa31aaf) does not exists... Thanks for the quick reply, though.
>
>The submodule might look in the wrong place as clearly it is available here:
>
>https://github.com/ARMmbed/mbedtls/commit/c49b808ae490f03d665df5faae457f613aa31aaf

This is what the Makefile has,

[snip]
# The mbedtls libraries are all built the same way.
mbedtls/library/libmbedcrypto.a mbedtls/library/libmbedtls.a mbedtls/library/libmbedx509.a:
        git submodule init
        git submodule update
        cd mbedtls && git checkout -q c49b808ae490f03d665df5faae457f613aa31aaf
        cd mbedtls && $(MAKE) no_test && touch library/libmbedcrypto.a && touch library/libmbedtls.a && touch library/libmbedx509.a
[snip]

and this is my error I am getting right at that spot:

$ 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.

Question: does it matter that I did a 'git init' before starting this?  Thanks for any help.

josé

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 19:21       ` Jack
@ 2019-05-13 20:15         ` Jose Isaias Cabrera
  2019-05-13 20:23           ` Jack
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 20:15 UTC (permalink / raw)
  To: Jack, cygwin


Jack, on Monday, May 13, 2019 03:21 PM, wrote...
>On 2019.05.13 15:01, Jose Isaias Cabrera wrote:

>upstream repository is.  I'll guess here that you started by unpacking
>a tarball, and not cloning the Bedrock git repository, and that they
Yep, that's what happened.  The reason why was this...

$ git clone https://github.com/Expensify/Bedrock.git
Cloning into 'Bedrock'...
fatal: unable to access 'https://github.com/Expensify/Bedrock.git/': Out of memory

So, I downloaded the tarball and...

>either need to start by a git clone, or have them tell you how to
>manually specify the missing submodule information.
Yeah, they are not responding. So, I guess I'll have to figure this one out the hard way...

>However, in doing a bit of searching, I just found a stackoverflow
>answer which includes "This is the most common problem with submodules.
Yeah, I read that one, amongst other git suggestions.  One of them was doing a 'git init'.

>the repository. "    This implies that mbedtls does have a .git folder,
>but that particular commit is not yet available.  Try doing a "git
>pull" when in that subdirectory.  Otherwise, wait for a response from

I'll give this a try...

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 20:15         ` Jose Isaias Cabrera
@ 2019-05-13 20:23           ` Jack
  2019-05-13 20:37             ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Jack @ 2019-05-13 20:23 UTC (permalink / raw)
  To: cygwin

On 2019.05.13 16:15, Jose Isaias Cabrera wrote:
[snip.....]
> $ git clone https://github.com/Expensify/Bedrock.git
> Cloning into 'Bedrock'...
> fatal: unable to access 'https://github.com/Expensify/Bedrock.git/':  
> Out of memory
I think that means you.  Do you have enough disk space?

Before doing much else, however, please confirm that that subdirectory  
does have a .git folder.  If so, the git pull should work.  If not, it  
wont.
--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 20:23           ` Jack
@ 2019-05-13 20:37             ` Jose Isaias Cabrera
  2019-05-13 21:26               ` Jack
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 20:37 UTC (permalink / raw)
  To: Jack, cygwin


Jack, on Monday, May 13, 2019 04:22 PM, wrote...
>On 2019.05.13 16:15, Jose Isaias Cabrera wrote:
>[snip.....]
>> $ git clone https://github.com/Expensify/Bedrock.git
>> Cloning into 'Bedrock'...
>> fatal: unable to access 'https://github.com/Expensify/Bedrock.git/':
>> Out of memory
>I think that means you.  Do you have enough disk space?

$ df -a
Filesystem      Size  Used Avail Use% Mounted on
C:/cygwin/bin      -     -     -    - /usr/bin
C:/cygwin/lib      -     -     -    - /usr/lib
C:/cygwin       280G   67G  213G  24% /
B:              4.0G   91M  3.9G   3% /cygdrive/b
C:                 -     -     -    - /cygdrive/c
D:              183G   18G  165G  10% /cygdrive/d


>
>Before doing much else, however, please confirm that that subdirectory
>does have a .git folder.  If so, the git pull should work.  If not, it
>wont.

You are right.  There is no .git folder within mbedtls. Hmmm...

I am not a git guy.  Do I do a 'git init' to get a .git folder created?


--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 20:37             ` Jose Isaias Cabrera
@ 2019-05-13 21:26               ` Jack
  2019-05-13 21:58                 ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Jack @ 2019-05-13 21:26 UTC (permalink / raw)
  To: cygwin

On 2019.05.13 16:37, Jose Isaias Cabrera wrote:
> Jack, on Monday, May 13, 2019 04:22 PM, wrote...
> >On 2019.05.13 16:15, Jose Isaias Cabrera wrote:
> >[snip.....]
> >> $ git clone https://github.com/Expensify/Bedrock.git
> >> Cloning into 'Bedrock'...
> >> fatal: unable to access  
> 'https://github.com/Expensify/Bedrock.git/':
> >> Out of memory
> >I think that means you.  Do you have enough disk space?
> $ df -a
> Filesystem      Size  Used Avail Use% Mounted on
> C:/cygwin/bin      -     -     -    - /usr/bin
> C:/cygwin/lib      -     -     -    - /usr/lib
> C:/cygwin       280G   67G  213G  24% /
> B:              4.0G   91M  3.9G   3% /cygdrive/b
> C:                 -     -     -    - /cygdrive/c
> D:              183G   18G  165G  10% /cygdrive/d
Which drive are you trying to build on?  B: 3.9G might well not be  
enough room.  C: and D: seem to have enough space.
> 
>> Before doing much else, however, please confirm that that  
>> subdirectory does have a .git folder.  If so, the git pull should  
>> work.  If not, it wont.
> You are right.  There is no .git folder within mbedtls. Hmmm...
> 
> I am not a git guy.  Do I do a 'git init' to get a .git folder  
> created?
The problem is you can't just create a new git repo from thin air.  You  
need to pull it from the mbedtls site.  The Bedrock repository contains  
the bits that tell the git submodule commands how to do that - that's  
what is missing from the tarball.  I suppose you could go to the dir  
one above mbedtls and try cloning that repository, which should then  
have all the pieces Bedrock seems to expect.
--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 21:26               ` Jack
@ 2019-05-13 21:58                 ` Jose Isaias Cabrera
  2019-05-14  3:29                   ` Brian Inglis
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-13 21:58 UTC (permalink / raw)
  To: Jack, cygwin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1921 bytes --]


Jack, on Monday, May 13, 2019 05:26 PM, wrote...​
>On 2019.05.13 16:37, Jose Isaias Cabrera wrote:​
>> Jack, on Monday, May 13, 2019 04:22 PM, wrote...​
>> >On 2019.05.13 16:15, Jose Isaias Cabrera wrote:​
>> >[snip.....]​
>> >> $ git clone https://github.com/Expensify/Bedrock.git​
>> >> Cloning into 'Bedrock'...​
>> >> fatal: unable to access  ​
>> 'https://github.com/Expensify/Bedrock.git/':​
>> >> Out of memory​
>> >I think that means you.  Do you have enough disk space?​
>> $ df -a​
>> Filesystem      Size  Used Avail Use% Mounted on​
>> C:/cygwin/bin      -     -     -    - /usr/bin​
>> C:/cygwin/lib      -     -     -    - /usr/lib​
>> C:/cygwin       280G   67G  213G  24% /​
>> B:              4.0G   91M  3.9G   3% /cygdrive/b​
>> C:                 -     -     -    - /cygdrive/c​
>> D:              183G   18G  165G  10% /cygdrive/d​
>Which drive are you trying to build on?  B: 3.9G might well not be  ​
>enough room.  C: and D: seem to have enough space.​
​
I am trying to install it on c: so it has enough information.  I did see this reference [1] on stackoverflow, which is points to a memory problem. I am running a 32 bit instance of cygwin, so, it may not have enough memory for the whole clone process.  I will try tomorrow to reboot and try it without any applications.  This may provide the "memory" needed.  Is there any way to assign more memory to the cygwin terminal through windows?  Thanks for all your help.  I really appreciate it.​
​
josé​
​
[1] https://stackoverflow.com/questions/7607970/git-clone-fails-with-out-of-memory-error-fatal-out-of-memory-malloc-failed​


\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-13 21:58                 ` Jose Isaias Cabrera
@ 2019-05-14  3:29                   ` Brian Inglis
  2019-05-14 13:51                     ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Brian Inglis @ 2019-05-14  3:29 UTC (permalink / raw)
  To: cygwin

On 2019-05-13 15:58, Jose Isaias Cabrera wrote:
> 
> Jack, on Monday, May 13, 2019 05:26 PM, wrote...​
>> On 2019.05.13 16:37, Jose Isaias Cabrera wrote:​
>>> Jack, on Monday, May 13, 2019 04:22 PM, wrote...​
>>>> On 2019.05.13 16:15, Jose Isaias Cabrera wrote:​
>>>> [snip.....]​
>>>>> $ git clone https://github.com/Expensify/Bedrock.git​
>>>>> Cloning into 'Bedrock'...​
>>>>> fatal: unable to access  ​
>>> 'https://github.com/Expensify/Bedrock.git/':​
>>>>> Out of memory​
>>>> I think that means you.  Do you have enough disk space?​
>>> $ df -a​
>>> Filesystem      Size  Used Avail Use% Mounted on​
>>> C:/cygwin/bin      -     -     -    - /usr/bin​
>>> C:/cygwin/lib      -     -     -    - /usr/lib​
>>> C:/cygwin       280G   67G  213G  24% /​
>>> B:              4.0G   91M  3.9G   3% /cygdrive/b​
>>> C:                 -     -     -    - /cygdrive/c​
>>> D:              183G   18G  165G  10% /cygdrive/d​
>> Which drive are you trying to build on?  B: 3.9G might well not be  ​
>> enough room.  C: and D: seem to have enough space.​
> ​
> I am trying to install it on c: so it has enough information.  I did see this reference [1] on stackoverflow, which is points to a memory problem. I am running a 32 bit instance of cygwin, so, it may not have enough memory for the whole clone process.  I will try tomorrow to reboot and try it without any applications.  This may provide the "memory" needed.  Is there any way to assign more memory to the cygwin terminal through windows?  Thanks for all your help.  I really appreciate it.​
> [1] https://stackoverflow.com/questions/7607970/git-clone-fails-with-out-of-memory-error-fatal-out-of-memory-malloc-failed​

You might want to try installing WSL then follow the Ubuntu instructions to
figure out what the build resource requirements are.
Then use the peflags settings in
	https://cygwin.com/cygwin-ug-net/setup-maxmem.html
after applying the linked MS settings if you are running 32 bit Windows.
If you are running 64 bit Windows, you should run 64 bit Cygwin if you need more
than 4GB memory total for maximum heap after rebasing for all exes and dlls.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14  3:29                   ` Brian Inglis
@ 2019-05-14 13:51                     ` Jose Isaias Cabrera
  2019-05-14 16:18                       ` Brian Inglis
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-14 13:51 UTC (permalink / raw)
  To: cygwin, Brian.Inglis


Brian Inglis, on Monday, May 13, 2019 11:29 PM, wrote...
>You might want to try installing WSL then follow the Ubuntu instructions to
I am trying to make this work from work.  And I am running Windows 7, which does not support WSL.

>figure out what the build resource requirements are.
>Then use the peflags settings in
>        https://cygwin.com/cygwin-ug-net/setup-maxmem.html
This is a good advice.  I tried running this command,

$ peflags --cygwin-heap git.exe
git.exe: skipped because nonexistent

how do I add more memory to git.exe using peflags?  I read the site you mentioned above, and it's not very clear as to how it can be done.  There is actually a mistake in the documentation: the third sentence reads,

"In some cases, this problem can be solved by changing a field in the file header which is utilized by Cygwin since to keep the initial size of the application heap."

I think the word "since" after Cygwin, is not needed. Thanks.

josé




--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14 13:51                     ` Jose Isaias Cabrera
@ 2019-05-14 16:18                       ` Brian Inglis
  2019-05-14 16:27                         ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Brian Inglis @ 2019-05-14 16:18 UTC (permalink / raw)
  To: cygwin

On 2019-05-14 07:51, Jose Isaias Cabrera wrote:
> 
> Brian Inglis, on Monday, May 13, 2019 11:29 PM, wrote...
>> You might want to try installing WSL then follow the Ubuntu instructions to
> I am trying to make this work from work.  And I am running Windows 7, which 
> does not support WSL.
>> figure out what the build resource requirements are.
>> Then use the peflags settings in
>>        https://cygwin.com/cygwin-ug-net/setup-maxmem.html
> This is a good advice.  I tried running this command,
> $ peflags --cygwin-heap git.exe
> git.exe: skipped because nonexistent

Supply a path name:
$ peflags --cygwin-heap /bin/git
/bin/git.exe: initial Cygwin heap size: 0 (0x0) MB

$ peflags -v /bin/git
/bin/git:
coff(0x022f[+relocs_stripped,+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
pe(0x8000[+tsaware])

$ peflags -d -f -n -i -s -b -W -t -w -l -S -x -X -y -Y -z -v /bin/git
/bin/git: coff(0x022f[-wstrim,+bigaddr,+sepdbg])
pe(0x8000[-dynamicbase,-forceinteg,-nxcompat,-no-isolation,-no-seh,-no-bind,-wdmdriver,+tsaware])
          stack reserve size      : 2097152 (0x200000) bytes
          stack commit size       : 4096 (0x1000) bytes
          Win32 heap reserve size : 1048576 (0x100000) bytes
          Win32 heap commit size  : 4096 (0x1000) bytes
          initial Cygwin heap size: 0 (0x0) MB

> how do I add more memory to git.exe using peflags?  I read the site you
> mentioned above, and it's not very clear as to how it can be done. 

$ peflags --cygwin-heap=2048 /bin/git
/bin/git: initial Cygwin heap size: 2048 (0x800) MB
$ peflags --cygwin-heap=0 /bin/git
/bin/git: initial Cygwin heap size: 0 (0x0) MB

> There is actually a mistake in the documentation: the third sentence reads,
> "In some cases, this problem can be solved by changing a field in the file 
> header which is utilized by Cygwin since to keep the initial size of the 
> application heap."
> I think the word "since" after Cygwin, is not needed.

Patch years ago to one doc source line removed "version 1.7.10" but left "since"
on the previous doc source line.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14 16:18                       ` Brian Inglis
@ 2019-05-14 16:27                         ` Jose Isaias Cabrera
  2019-05-14 17:11                           ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-14 16:27 UTC (permalink / raw)
  To: cygwin, Brian.Inglis


Thanks, sir.


From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> on behalf of Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Sent: Tuesday, May 14, 2019 12:18 PM
To: cygwin@cygwin.com
Subject: Re: Building Bedrockdb in cygwin

On 2019-05-14 07:51, Jose Isaias Cabrera wrote:
>
> Brian Inglis, on Monday, May 13, 2019 11:29 PM, wrote...
>> You might want to try installing WSL then follow the Ubuntu instructions to
> I am trying to make this work from work.  And I am running Windows 7, which
> does not support WSL.
>> figure out what the build resource requirements are.
>> Then use the peflags settings in
>>        https://cygwin.com/cygwin-ug-net/setup-maxmem.html
> This is a good advice.  I tried running this command,
> $ peflags --cygwin-heap git.exe
> git.exe: skipped because nonexistent

Supply a path name:
$ peflags --cygwin-heap /bin/git
/bin/git.exe: initial Cygwin heap size: 0 (0x0) MB

$ peflags -v /bin/git
/bin/git:
coff(0x022f[+relocs_stripped,+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
pe(0x8000[+tsaware])

$ peflags -d -f -n -i -s -b -W -t -w -l -S -x -X -y -Y -z -v /bin/git
/bin/git: coff(0x022f[-wstrim,+bigaddr,+sepdbg])
pe(0x8000[-dynamicbase,-forceinteg,-nxcompat,-no-isolation,-no-seh,-no-bind,-wdmdriver,+tsaware])
          stack reserve size      : 2097152 (0x200000) bytes
          stack commit size       : 4096 (0x1000) bytes
          Win32 heap reserve size : 1048576 (0x100000) bytes
          Win32 heap commit size  : 4096 (0x1000) bytes
          initial Cygwin heap size: 0 (0x0) MB

> how do I add more memory to git.exe using peflags?  I read the site you
> mentioned above, and it's not very clear as to how it can be done.

$ peflags --cygwin-heap=2048 /bin/git
/bin/git: initial Cygwin heap size: 2048 (0x800) MB
$ peflags --cygwin-heap=0 /bin/git
/bin/git: initial Cygwin heap size: 0 (0x0) MB

> There is actually a mistake in the documentation: the third sentence reads,
> "In some cases, this problem can be solved by changing a field in the file
> header which is utilized by Cygwin since to keep the initial size of the
> application heap."
> I think the word "since" after Cygwin, is not needed.

Patch years ago to one doc source line removed "version 1.7.10" but left "since"
on the previous doc source line.

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14 16:27                         ` Jose Isaias Cabrera
@ 2019-05-14 17:11                           ` Jose Isaias Cabrera
  2019-05-14 22:17                             ` Csaba Ráduly
  0 siblings, 1 reply; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-14 17:11 UTC (permalink / raw)
  To: cygwin, Brian.Inglis


So, finally, I was able to to through the git problem: I needed to set the correct proxy syntax, here it is in case someone ever gets a git out of memory error:

git config --global http.proxy http://proxyuser:proxypwd@proxy.server.com:8080

and

change proxyuser to your proxy user
change proxypwd to your proxy password
change proxy.server.com to the URL of your proxy server
change 8080 to the proxy port configured on your proxy server

However, having jumped that huddle, I encountered a new one, which is probably easier to deal with. The make command does a lot of work, but once it's going to start compiling, I get,

[good stuff clipped]
  CC    util/pem2der.c
  CC    util/strerror.c
  CC    x509/cert_app.c
  CC    x509/crl_app.c
  CC    x509/cert_req.c
  CC    x509/cert_write.c
  CC    x509/req_app.c
make[2]: Leaving directory '/home/e608313/Bedrock/mbedtls/programs'
make[1]: Leaving directory '/home/e608313/Bedrock/mbedtls'
g++-6 -g -std=c++14 -fpic -O2 -Wall -Werror -Wformat-security -DGIT_REVISION=ce62c88 -I/home/e608313/Bedrock -I/home/e608313/Bedrock/mbedtls/include -MMD -MF libstuff/libstuff.d -MT libstuff/libstuff.h.gch -c libstuff/libstuff.h
make: g++-6: Command not found
make: *** No rule to make target 'libstuff/libstuff.d', needed by '.build/libstuff/libstuff.d'.  Stop.

So, it appears that I need something called g++-6. I have both gcc and g++

$ ls /usr/bin/g++*
/usr/bin/g++.exe*

So, the question is, what is g++-6, and how to I get it?  I tried to find it with cygwin's setup, but it's not on the distro.  I tried to duckduckgo it, but I didn't get anything useful.  Thoughts?  Thanks

josé




--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14 17:11                           ` Jose Isaias Cabrera
@ 2019-05-14 22:17                             ` Csaba Ráduly
  2019-05-15 12:24                               ` Jose Isaias Cabrera
  0 siblings, 1 reply; 19+ messages in thread
From: Csaba Ráduly @ 2019-05-14 22:17 UTC (permalink / raw)
  To: cygwin

On 14/05/2019 19:11, Jose Isaias Cabrera wrote:
(snip)

> However, having jumped that huddle, I encountered a new one, which is probably easier to deal with. The make command does a lot of work, but once it's going to start compiling, I get,
> 
> [good stuff clipped]
>    CC    util/pem2der.c
>    CC    util/strerror.c
>    CC    x509/cert_app.c
>    CC    x509/crl_app.c
>    CC    x509/cert_req.c
>    CC    x509/cert_write.c
>    CC    x509/req_app.c
> make[2]: Leaving directory '/home/e608313/Bedrock/mbedtls/programs'
> make[1]: Leaving directory '/home/e608313/Bedrock/mbedtls'
> g++-6 -g -std=c++14 -fpic -O2 -Wall -Werror -Wformat-security -DGIT_REVISION=ce62c88 -I/home/e608313/Bedrock -I/home/e608313/Bedrock/mbedtls/include -MMD -MF libstuff/libstuff.d -MT libstuff/libstuff.h.gch -c libstuff/libstuff.h
> make: g++-6: Command not found
> make: *** No rule to make target 'libstuff/libstuff.d', needed by '.build/libstuff/libstuff.d'.  Stop.
> 
> So, it appears that I need something called g++-6. I have both gcc and g++
> 
> $ ls /usr/bin/g++*
> /usr/bin/g++.exe*
> 
> So, the question is, what is g++-6, and how to I get it?  I tried to find it with cygwin's setup, but it's not on the distro.  I tried to duckduckgo it, but I didn't get anything useful.  Thoughts?  Thanks

g++-6 is version 6 of the C++ compiler in the GNU Compiler Collection.

Cygwin's gcc and g++ is version 7.4.0:
$ g++.exe -dumpversion
7.4.0

Bedrockdb's makefile begins with:

# Set the compiler, if it's not set by the environment.
ifndef GXX
         GXX = g++-6
endif

ifndef CC
         CC = gcc-6
endif

so the C++ compiler (GXX) is set to g++-6 unless GXX is set explicitly.


You need to run make like this:

CC=gcc GXX=g++ make <whatever arguments you gave to make, if any>

This will force make to use g++ instead of g++-6

Hope this helps,

Csaba
-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: Building Bedrockdb in cygwin
  2019-05-14 22:17                             ` Csaba Ráduly
@ 2019-05-15 12:24                               ` Jose Isaias Cabrera
  0 siblings, 0 replies; 19+ messages in thread
From: Jose Isaias Cabrera @ 2019-05-15 12:24 UTC (permalink / raw)
  To: Csaba Ráduly, cygwin


Csaba Ráduly, on Tuesday, May 14, 2019 06:17 PM, wrote...
>On 14/05/2019 19:11, Jose Isaias Cabrera wrote:
[clip]

>You need to run make like this:
>
>CC=gcc GXX=g++ make <whatever arguments you gave to make, if any>
>
>This will force make to use g++ instead of g++-6


Thanks, this works, but I think I have other dependencies.  This is what I now have,

$ CC=gcc GXX=g++ make
g++ -g -std=c++14 -fpic -O2 -Wall -Werror -Wformat-security -DGIT_REVISION=ce62c88 -I/home/e608313/Bedrock -I/home/e608313/Bedrock/mbedtls/include -MMD -MF libstuff/libstuff.d -MT libstuff/libstuff.h.gch -c libstuff/libstuff.h
libstuff/libstuff.h:7:10: fatal error: execinfo.h: No such file or directory
 #include <execinfo.h> // for backtrace
          ^~~~~~~~~~~~
compilation terminated.
make: *** No rule to make target 'libstuff/libstuff.d', needed by '.build/libstuff/libstuff.d'.  Stop.

I did a search on the web on both duckduckgo and google and there is nothing out there.  I can tell you that to build bedrockdb in Ubuntu, you need these steps,

==begin
# Clone out this repo:
git clone https://github.com/Expensify/Bedrock.git

# Install some dependencies
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install gcc-6 g++-6 libpcre++-dev zlib1g-dev

# Build it
cd Bedrock
make
==end

I went and grabbed all the libpcre* and zlib* from cygwin, but I don't know what toolchain is in cygwin.  So, libstuff must be a special file that I don't seem to find on the web.  However, there are some execinfo.h hits, but for different applications.  Any thoughts?  I will go back to the bedrockdb team and see what they say.  Thanks for any input.

josé

--
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

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2019-05-15 12:24 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-08 19:00 Building Bedrockdb in cygwin Jose Isaias Cabrera
2019-05-13 18:17 ` Jose Isaias Cabrera
2019-05-13 18:48   ` Jack
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

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).