From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] Enable support for the phar extension in PHP5.
Date: Thu, 17 Dec 2015 11:45:09 +0100 [thread overview]
Message-ID: <20151217104509.GF27568@pengutronix.de> (raw)
In-Reply-To: <20151130172022.GA1647@localhost.localdomain>
On Mon, Nov 30, 2015 at 06:20:22PM +0100, Ladislav Michl wrote:
> On Mon, Nov 30, 2015 at 03:09:21PM +0100, Kalle Ladefoged Pedersen wrote:
> > Signed-off-by: Kalle Ladefoged Pedersen <klp@kamstrup.com>
> > Reviewed-by: Bruno Thomsen <bth@kamstrup.com>
> > ---
> > rules/php5.in | 10 ++++++++++
> > rules/php5.make | 7 ++++++-
> > 2 files changed, 16 insertions(+), 1 deletion(-)
> >
> > diff --git a/rules/php5.in b/rules/php5.in
> > index d2f7baa..b88ad1b 100644
> > --- a/rules/php5.in
> > +++ b/rules/php5.in
> [snip]
> > +ifdef PTXCONF_PHP5_EXT_PHAR
> > +PHP5_AUTOCONF += --enable-phar
> > +else
> > +PHP5_AUTOCONF += --disable-phar
> > +endif
> > +
>
> Wouldn't '--$(call ptx/endis, PTXCONF_PHP5_EXT_PHAR)-phar' do better job?
The other options are specified like this as well. So at least it's
consistent. The whole file should be cleaned up. But that needs careful
testing because not all options accept --without-... (or at least they
didn't. ptx/ifdef needs to be used in that case...
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-12-17 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 14:09 Kalle Ladefoged Pedersen
2015-11-30 17:20 ` Ladislav Michl
2015-12-17 10:45 ` Michael Olbrich [this message]
2015-12-17 11:10 ` Michael Olbrich
2016-01-14 8:03 ` Kalle Ladefoged Pedersen
2016-01-18 9:26 ` Michael Olbrich
2016-01-19 12:08 ` Pallavi Kadadi
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=20151217104509.GF27568@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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