From: Cary Lewis <cary.lewis@gmail.com>
To: cygwin@cygwin.com
Subject: Re: php memory errors
Date: Mon, 29 Jun 2020 08:39:07 -0400 [thread overview]
Message-ID: <CAEF1h+Wf6tdA9-WzrMLOWAarfaJ3qiD+da-6VhadUdW9TOJZJw@mail.gmail.com> (raw)
In-Reply-To: <872732732.20200619174201@yandex.ru>
Yes, I reported this last week - composer (composer.phar) gives out of
memory errors, despite having max_memory_limit set to -1.
I have tried to compile php myself, but to no avail - php 7.3.19 doesn't
compile, there are errors in the zend framework.
php-7.3.19/Zend/zend_portability.h:381:18: error: ‘sigjmp_buf’ does not
name a type; did you mean ‘jmp_buf’?
381 | # define JMP_BUF sigjmp_buf
| ^~~~~~~~~~
php-7.3.19/Zend/zend_signal.h:46:2: error: ‘siginfo_t’ does not name a type
46 | siginfo_t *siginfo;
php-7.3.19/main/php_config.h:2653:24: error: ‘finite’ was not declared in
this scope; did you mean ‘fwrite’?
2653 | #define zend_finite(a) finite(a)
On Fri, Jun 19, 2020 at 10:52 AM Andrey Repin <anrdaemon@yandex.ru> wrote:
> Greetings, Richard H Lee!
>
> > I've recently gotten out of memory errors with php, with tasks that
> > previously have worked fine.
>
> Which errors? Why don't you run your tasks in native PHP?
>
> > Has anybody else experienced this too?
>
> Useless question.
>
>
> --
> With best regards,
> Andrey Repin
> Friday, June 19, 2020 17:41:23
>
> Sorry for my terrible english...
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
prev parent reply other threads:[~2020-06-29 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 11:38 Richard H Lee
2020-06-19 14:42 ` Andrey Repin
2020-06-29 12:39 ` Cary Lewis [this message]
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=CAEF1h+Wf6tdA9-WzrMLOWAarfaJ3qiD+da-6VhadUdW9TOJZJw@mail.gmail.com \
--to=cary.lewis@gmail.com \
--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).