From: Richard H Lee <ricardohenrylee@gmail.com>
To: cygwin@cygwin.com
Subject: Memcache/d (Orig: Re: Composer segfault on multiple configurations)
Date: Thu, 25 May 2017 21:21:00 -0000 [thread overview]
Message-ID: <d631b3cc-e3ee-42cb-2ef8-deb6d5889a53@gmail.com> (raw)
In-Reply-To: <CADWQZEvGRcTXPOE4DifgidT93eenTtmR=ggLUashUtJMt8eS7w@mail.gmail.com>
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 memcache support while at it (Bash on Ubuntu on
> Windows, for example, has memcache and memcached included out of the
> box).
Unfortunately, I think memcache is a separate package from php and it
would not be compiled in by cygports.
From what I read memcache is rather unmaintained and should be
deprecated. Memcached should be used instead.
https://github.com/oerdnj/deb.sury.org/issues/186#issuecomment-186217296
Memcache can't really be compiled for php7. Memcached can be. Taking a
quick look at memcached, the memcached server compiles fine on cygwin
except for one minor printf statement. Libmemcached, which php-memcached
relies upon, requires a little bit more work (it's that whole "undefined
symbols in shared libraries" thing). You possibly may want to consider
moving your code from memcache to memcached.
For most websites memcache/d is optional. If the website detects that
memcache/d is not present during setup, it simply does not use it.
Usually people just don't use it for development and then turn it on for
production. That is unless you specifically want to run memcache/d code
on Cygwin.
--
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
next prev parent reply other threads:[~2017-05-25 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 19:32 Composer segfault on multiple configurations Sky Diver
2017-05-17 20:47 ` Richard H Lee
2017-05-18 11:02 ` Sky Diver
2017-05-18 12:35 ` Andrey Repin
2017-05-18 13:33 ` Richard H Lee
2017-05-18 14:32 ` Sky Diver
2017-05-19 19:26 ` [ATTN: Yaakov Selkowitz / PHP maintainer] " Richard H Lee
2017-05-30 18:59 ` Richard H Lee
2017-05-30 20:47 ` Vince Rice
2017-05-31 1:02 ` Vince Rice
2017-05-22 19:54 ` Richard H Lee
2017-05-25 7:56 ` Sky Diver
2017-05-25 21:21 ` Richard H Lee [this message]
2017-05-27 10:51 ` Memcache/d (Orig: Re: Composer segfault on multiple configurations) Sky Diver
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=d631b3cc-e3ee-42cb-2ef8-deb6d5889a53@gmail.com \
--to=ricardohenrylee@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).