>> On May 30, 2017, at 11:47 AM, Richard H Lee wrote:
>>
>> Yaakov,
>>
>> I probably should have copied you in on the last message to get your
>> attention.
>>
>> It's just a simple patch to fix this page size issue with php on Cygwin.
>> Would be grateful if you could review and possibly acce
I'm sure he will tell you himself soon enough, but no you shouldn't have.
Emails re packages should go to the list, not to the package maintainers
directly. If you want to ping a previous message, ping the list, not the person.
> On May 30, 2017, at 11:47 AM, Richard H Lee wrote:
>
> Yaakov,
>
Yaakov,
I probably should have copied you in on the last message to get your
attention.
It's just a simple patch to fix this page size issue with php on Cygwin.
Would be grateful if you could review and possibly accept this patch, as
it has been confirmed and does affect several people.
Ri
On Fri, May 26, 2017 at 12:11 AM, Richard H Lee wrote:
> On 25/05/2017 08:50, Sky Diver wrote:
> PHP 5.5.9, PHP 5.6.2 on Cygwin?
> Were they even released on Cygwin?
Sure did. Requires a bit of digging through the "cygwin time machine"
archive but they are all there.
> Unfortunately, I think memca
On 25/05/2017 08:50, Sky Diver wrote:
Since then I went back in time and installed PHP 5.5.9, PHP 5.6.20 but
the result is the same.
PHP 5.5.9, PHP 5.6.2 on Cygwin?
Were they even released on Cygwin?
So I might end up following your steps in order to build PHP, hoping I
could enable built-in m
On Mon, May 22, 2017 at 9:38 PM, Richard H Lee wrote:
> Just in case Sky Diver or anyone else is interested in compiling php from
> Cygports, here are some simple steps to do so.
Thanks Richard, I may try this at some point, but am currently
experiencing other instabilities.
For some reason, I sta
On 18/05/2017 08:42, Sky Diver wrote:
I may compile php from cygports
Just in case Sky Diver or anyone else is interested in compiling php
from Cygports, here are some simple steps to do so. It's not really
difficult and most of the time it takes up is downloading the packages
and compiling
On 18/05/2017 08:42, Sky Diver wrote:
Any idea when your fix will get released as an official cygwin PHP
package?
Hi Yaakov,
I can see you're really busy with package maintenance and all, but I was
wondering if you could review and merge my patch for this issue. It's
basically changing the def
On Thu, May 18, 2017 at 3:34 PM, Andrey Repin wrote:
> Please don't top-post, and don't quote raw email addresses.
Fair enough.
On Thu, May 18, 2017 at 3:59 PM, Richard H Lee wrote:
> On 18/05/2017 13:34, Andrey Repin wrote:
>>
>> Try turning pcre.jit off, it was known to be a problem in the past.
On 18/05/2017 13:34, Andrey Repin wrote:
Try turning pcre.jit off, it was known to be a problem in the past.
This is already turned off in the cygport patches.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://
Greetings, Sky Diver!
Please don't top-post, and don't quote raw email addresses.
> On Wed, May 17, 2017 at 11:24 PM, Richard H Lee wrote:
>> On 17/05/2017 20:17, Sky Diver wrote:
>>>
>>> Running "composer install" with the following composer.json ends up in
>>> a segmentation fault.
>>>
>>>
Thanks Richard, you've hit the nail right on the head.
Running PHP on that specific file does produce the segfault.
I'm currently running composer via "Bash on Ubuntu on Windows". I may
compile PHP from cygports later but currently I need to make up for
lost time at work over this.
Any idea when y
On 17/05/2017 20:17, Sky Diver wrote:
Running "composer install" with the following composer.json ends up in
a segmentation fault.
-- START ---
{
"require": {
"propel/propel": "~2.0@dev"
},
"config": {
"optimize-autoloader": true
}
}
Hi,
Running "composer install" with the following composer.json ends up in
a segmentation fault.
-- START ---
{
"require": {
"propel/propel": "~2.0@dev"
},
"config": {
"optimize-autoloader": true
}
}
-- END -
(*) Note: when "opt
14 matches
Mail list logo
