From: Bruno Thomsen <bth@kamstrup.com>
To: ptxdist@pengutronix.de
Cc: Kalle Ladefoged Pedersen <klp@kamstrup.com>, bth@kamstrup.com
Subject: [ptxdist] [PATCH] php5: enable support for the phar extension.
Date: Mon, 27 Jun 2016 13:26:49 +0200 [thread overview]
Message-ID: <1467026809-8259-2-git-send-email-bth@kamstrup.com> (raw)
In-Reply-To: <1467026809-8259-1-git-send-email-bth@kamstrup.com>
v2:
- use ptx/endis
- phar extension is broken in cli.
Signed-off-by: Bruno Thomsen <bth@kamstrup.com>
Signed-off-by: Kalle Ladefoged Pedersen <klp@kamstrup.com>
---
rules/php5.in | 11 +++++++++++
rules/php5.make | 2 +-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/rules/php5.in b/rules/php5.in
index d2f7baa..a9286e4 100644
--- a/rules/php5.in
+++ b/rules/php5.in
@@ -289,6 +289,17 @@ config PHP5_EXT_PEAR
help
pear
+config PHP5_EXT_PHAR
+ bool
+ prompt "phar"
+ depends on !PHP5_SAPI_CLI
+ help
+ The phar extension provides a way to put entire PHP applications
+ into a single file called "phar" (PHP Archive) for easy
+ distribution and installation. The phar extension also provides
+ a file-format abstraction method for creating and manipulating
+ tar and zip files through the PharData class.
+
endmenu
endif
diff --git a/rules/php5.make b/rules/php5.make
index cc9dc8e..33e842c 100644
--- a/rules/php5.make
+++ b/rules/php5.make
@@ -48,7 +48,7 @@ PHP5_CONF_ENV := \
#
PHP5_AUTOCONF := \
$(CROSS_AUTOCONF_USR) \
- --disable-phar \
+ --$(call ptx/endis, PTXCONF_PHP5_EXT_PHAR)-phar \
--with-config-file-path=/etc/php5 \
--enable-opcache=no \
--without-iconv
--
2.5.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-06-27 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:26 [ptxdist] [PATCHv2] " Bruno Thomsen
2016-06-27 11:26 ` Bruno Thomsen [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=1467026809-8259-2-git-send-email-bth@kamstrup.com \
--to=bth@kamstrup.com \
--cc=klp@kamstrup.com \
--cc=ptxdist@pengutronix.de \
/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