public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Cary Lewis <cary.lewis@gmail.com>
Cc: km2z7kca0oge@opayq.com, cygwin@cygwin.com
Subject: Re: Cygwin PHP (all available versions) has a hard 4MB memory limit
Date: Tue, 4 Aug 2020 09:58:01 -0400	[thread overview]
Message-ID: <38dc6236-f6e7-1e2e-7fd7-5a52e79c29da@cornell.edu> (raw)
In-Reply-To: <CAEF1h+UHng8F=1LvnVDjeaFzasVUi-osWmcW0EdRD94pisDqxA@mail.gmail.com>

[Once again, please don't top-post on this list.]

On 8/4/2020 9:35 AM, Cary Lewis wrote:
> Thank you Ken, I followed your instructions and I am now able to use https and 
> composer with your versions of php.
> 
> Did you have to apply any of the cygport patches?

I applied all of them except for one hunk of one of them.  Yaakov, the 
(retiring) php maintainer, had reasons for applying the patches, and I'm not 
going to second-guess him.  The next maintainer (who won't be me) can look into 
it more thoroughly if s/he wants.

> I hope that the offical cygwin repos and mirros get updated.

I'll see what I can do.

Ken

  reply	other threads:[~2020-08-04 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 21:39 km2z7kca0oge
2020-07-17 22:39 ` Brian Inglis
2020-07-18  7:29 ` Andrey Repin
2020-07-19  2:11 ` Ken Brown
2020-07-21 20:45   ` Ken Brown
2020-08-04  1:57     ` Cary Lewis
2020-08-04 10:45       ` Ken Brown
2020-08-04 13:35         ` Cary Lewis
2020-08-04 13:58           ` Ken Brown [this message]
2020-07-18 15:33 km2z7kca0oge
2020-07-18 17:32 ` Brian Inglis
2020-07-18 15:54 km2z7kca0oge
2020-07-21 20:58 km2z7kca0oge

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=38dc6236-f6e7-1e2e-7fd7-5a52e79c29da@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cary.lewis@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=km2z7kca0oge@opayq.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).