Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: evolution-data-server and php-native broken by libxml2 upgrade in oe-core
Date: Thu, 22 Nov 2012 13:38:03 +0100	[thread overview]
Message-ID: <50AE1CAB.7060003@linaro.org> (raw)
In-Reply-To: <20121122123447.GB12637@jama.jama.net>

W dniu 22.11.2012 13:34, Martin Jansa pisze:
> Just FYI:
> 
> meta-gnome/recipes-gnome/eds/evolution-data-server_git.bb
> virtual:native:meta-openembedded/meta-oe/recipes-devtools/php/php_5.3.6.bb
> 
> are broken after lixml2 upgrade from 2.8.0 to 2.9.0 (oe-core rev
> a65ea43e26866ddc60051c52b2eb226507fae346)
> 
> They are pretty low priority for me right now, so I'm just sending this
> e-mail instead of patches :). 
> 
> Hrw is already working on php.

I was working on php 5.4.8 which builds with this libxml2 version for
native but fails for my armv8 target.




  reply	other threads:[~2012-11-22 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 12:34 evolution-data-server and php-native broken by libxml2 upgrade in oe-core Martin Jansa
2012-11-22 12:38 ` Marcin Juszkiewicz [this message]
2012-11-22 16:35 ` Martin Jansa

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=50AE1CAB.7060003@linaro.org \
    --to=marcin.juszkiewicz@linaro.org \
    --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