public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Building Bedrockdb in cygwin
Date: Tue, 14 May 2019 16:18:00 -0000	[thread overview]
Message-ID: <ef300eee-b752-7f77-92f6-12eeb3803327@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB7PR01MB5386CAE6AEE09B1559E7C867DE080@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>

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

  reply	other threads:[~2019-05-14 16:18 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
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 [this message]
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=ef300eee-b752-7f77-92f6-12eeb3803327@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).