mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Kalle Ladefoged Pedersen <klp@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] Enable support for the phar extension in PHP5.
Date: Thu, 14 Jan 2016 08:03:47 +0000	[thread overview]
Message-ID: <57A4BCD81EAD9E4DA78858E805316821010A585480@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <20151217111026.GK27568@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2734 bytes --]

Hi Michael,

It works fine with our build setup for an Freescale i.MX28 processor with PHP 5.5.30 and lighttpd 1.4.39
We use OSELAS.Toolchain-2014.12.1 (arm-v5te-linux-gnueabi/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized) and ptxdist-2015.10.0 for compiling.

We tried to see if we could reproduce the error that you got but we didn’t succeed.
Can you please let me know what setup you are running? 


Venlig hilsen / Best regards
Kamstrup A/S
Kalle Ladefoged Pedersen
Student programmer
Technology

Kamstrup A/S
Industrivej 28
DK-8660 Skanderborg
T: +45 89 93 10 00
D: +45 89 93 16 18

klp@kamstrup.com
kamstrup.com


-----Original Message-----
From: ptxdist [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Michael Olbrich
Sent: 17. december 2015 12:11
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] Enable support for the phar extension in PHP5.

On Thu, Dec 17, 2015 at 11:45:09AM +0100, Michael Olbrich wrote:
> 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...

and it fails with:

[...]
Generating phar.php
[...]/build-target/php-5.5.30/sapi/cli/php: Argument list too long

Which is bogus because [...]/build-target/php-5.5.30/sapi/cli/php is a target binary. There is a cross-compiling problem here.

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

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3551 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-01-14  8:03 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
2015-12-17 11:10     ` Michael Olbrich
2016-01-14  8:03       ` Kalle Ladefoged Pedersen [this message]
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=57A4BCD81EAD9E4DA78858E805316821010A585480@Exchange2010.kamstrup.dk \
    --to=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