Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] PHP 5.5.15
Date: Mon, 25 Aug 2014 00:01:52 -0700	[thread overview]
Message-ID: <20140825070152.GG1014@haswell> (raw)
In-Reply-To: <20140821111443.GX3660@jama>

On 14-08-21 13:14:43, Martin Jansa wrote:
> On Thu, Aug 21, 2014 at 12:13:05PM +0200, zboszor@pr.hu wrote:
> > > Hello,
> > >
> > > as a follow-up to my yesterday's mail about "[PATCH] Allow using a more
> > > recent php", here's the proof of the pudding.
> > >
> > > I needed GD support in PHP, and it turned out that PHP 5.4.x only supports
> > > GD 2.0, while current OE has 2.1. Not wanting to downgrade GD, I chose to
> > > upgrade PHP.
> > >
> > > I had to update imap-fix-autofoo.patch so it applies cleanly and I also
> > > had to fix https://bugs.php.net/bug.php?id=66103 so it can be cross
> > > compiled. (I also submitted the patch at the link).
> > >
> > > I enabled more extensions in PHP than what was in the previous version,
> > > this is what I needed locally.
> > >
> > > Comments?
> > >
> > > Feel free to use it in any way.
> > 
> > This time with the patch attached. :-)
> 
> Can you please send inline patch (preferably with git send-email as
> README suggests)?
> 
> There is also issue with some files not being tracked by sstate:
> [^/]*/usr/lib/php/\.channels.*
> [^/]*/usr/lib/php/\.registry.*
> [^/]*/usr/lib/php/\.depdb.*
> [^/]*/usr/lib/php/\.filemap
> [^/]*/usr/lib/php/\.lock
> 

they should be packaged in FILES_${PN}-pear, so sstate should track them
is it because they start with a 'dot' ?



      reply	other threads:[~2014-08-25  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 10:08 [PATCH] PHP 5.5.15 zboszor
2014-08-21 10:13 ` zboszor
2014-08-21 11:14   ` Martin Jansa
2014-08-25  7:01     ` Khem Raj [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=20140825070152.GG1014@haswell \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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