From: Roger Qiu <roger.qiu@matrix.ai>
To: cygwin@cygwin.com
Subject: Issues with PHP PCRE and with libass4 vs libass5
Date: Fri, 13 Jan 2017 11:08:00 -0000 [thread overview]
Message-ID: <68327490-9d2f-bf30-fc5b-0aed798f2644@matrix.ai> (raw)
Hi All,
I was struggling to get the new PHP version working in cygwin until I
found this: https://www.cygwin.com/ml/cygwin/2016-11/msg00336.html
Is it a good idea to make `pcre.jit=0;` to be false for php-pcre
package? Otherwise there's no other information as to why PHP7 fails now
for many common applications like `composer`.
Another issue is `libass4` no longer exists, and yet it is still
required by things like `mplayer`. I used to use `mplayer` from cygwin
ports relying the `libass4` library from official cygwin packages, but
`libass5` only exists. Is there a way to bring back `libass4` or can
something else can be done?
Thanks,
Roger
--
Founder of Matrix AI
https://matrix.ai/
+61420925975
--
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:[~2017-01-13 11:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68327490-9d2f-bf30-fc5b-0aed798f2644@matrix.ai \
--to=roger.qiu@matrix.ai \
--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).