Re: Building Bedrockdb in 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

Re: Building Bedrockdb in cygwin

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 i

Re: Building Bedrockdb in 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/Expe

Re: Building Bedrockdb in 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 tha

Re: Pinentry-curses on cygwin environment

Hi Thomas, below my detailed items: What package? Reference, download link? How did you compile? I downloaded the package directly from gpg site into download page version. The version of pinentry package 1.1.0 (2017-12-03). I compile with read me process indicated which is included i

Re: Building Bedrockdb in 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 mu

Re: Building Bedrockdb in 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...

Re: Building Bedrockdb in 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/ARMmbe

Re: Building Bedrockdb in 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 ch

Re: Building Bedrockdb in 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 he

Re: Building Bedrockdb in 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.

Re: Building Bedrockdb in 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

Re: Building Bedrockdb in 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: c49b808ae490f03d665d

Re: Why is __unix__ defined, and not __WINDOWS__ ?

On Mon, 2019-05-13 at 16:49 +0200, Agner Fog wrote: > On 13/05/2019 07.39, Brian Inglis wrote: > > Not quite I believe Cygwin 64 bit programs follow the Unix 64 bit LP64 C > > programming memory model and the System V AMD64 ABI *NOT* the Windows 64 bit > > ILP64 C programming memory model and Micro

Re: SSHD Service shuts down after a while after latest library updates

On Sun, May 12, 2019 at 8:31 AM L A Walsh wrote: > This has been a feature of Windows since win98. Not officially, mind > you, but any scheduled task in windows would eventually become > unscheduled and stop running with out any notification. I've never seen this behavior on any Windows machine (

Re: Why is __unix__ defined, and not __WINDOWS__ ?

On 13/05/2019 07.39, Brian Inglis wrote: Not quite I believe Cygwin 64 bit programs follow the Unix 64 bit LP64 C programming memory model and the System V AMD64 ABI *NOT* the Windows 64 bit ILP64 C programming memory model and Microsoft x64 calling convention; see: http://www.unix.org/ve

Re: Why is __unix__ defined, and not __WINDOWS__ ?

On Sun, 12 May 2019 22:40:48, Brian Inglis wrote: > On 2019-05-12 14:54, Houder wrote: > > On Sun, 12 May 2019 13:33:30, Mike Gran via cygwin" wrote: > > >> I think these days the canonical defines are (somebody correct me if > >> I'm wrong) > >> __CYGWIN__ for Cygwin > >> _WIN32 as 1 on Min

RE: Why is __unix__ defined, and not __WINDOWS__ ?

Dear Agner, > But the compiler generates a Windows executable following most of the > Windows ABI (object file format, calling convention, etc.) Still cygwin is intentionally very different from Windows, e.g. on Cygwin you use / as path separator, on Windows you use \ as path separator. Cygwin c