Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 02/11] at-spi2: add -core and -atk, for GTK+ 3.8
Date: Tue, 4 Jun 2013 23:38:35 +0200	[thread overview]
Message-ID: <20130604213835.GC30727@jama> (raw)
In-Reply-To: <20130604142627.GA30727@jama>

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

On Tue, Jun 04, 2013 at 04:26:27PM +0200, Martin Jansa wrote:
> On Mon, Jun 03, 2013 at 01:39:32PM -0700, Saul Wold wrote:
> > On 05/31/2013 08:05 AM, Ross Burton wrote:
> > > Signed-off-by: Ross Burton <ross.burton@intel.com>
> > > ---
> > >   meta/recipes-support/atk/at-spi2-atk_2.8.1.bb  |   19 +++++++++++++++++++
> > >   meta/recipes-support/atk/at-spi2-core_2.8.0.bb |   17 +++++++++++++++++
> > >   2 files changed, 36 insertions(+)
> > >   create mode 100644 meta/recipes-support/atk/at-spi2-atk_2.8.1.bb
> > >   create mode 100644 meta/recipes-support/atk/at-spi2-core_2.8.0.bb
> > >
> > 
> > Ross,
> > 
> > I ran into a do_configure issue with this new recipe, the at-spi2-core 
> > failed to configure on my local test machine.
> > 
> > Possibly this is the reason:
> > > configure:13783: checking alignment of char
> > > configure:13819: result: 0
> > > configure:13822: error: Failed to find alignment. Check config.log for details.
> > 
> > Sau!
> 
> Hi, 
> 
> this issue is known:
> http://lists.openembedded.org/pipermail/openembedded-core/2013-February/075178.html

I've send site data for arm, 
http://lists.openembedded.org/pipermail/openembedded-core/2013-June/079485.html

but now I've noticed that ac_cv_alignof_char is also missing in x86_64
version of Ross's patch
http://git.openembedded.org/openembedded-core/commit/?id=8c46ec2edc0197b32d32e0f27d5b60271338b600
so qemux86-64 also fails.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-06-04 21:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 15:05 [PATCH 00/11] GTK+ 3 updates Ross Burton
2013-05-31 15:05 ` [PATCH 01/11] gdk-pixbuf: upgrade to 2.28.1 Ross Burton
2013-05-31 15:05 ` [PATCH 02/11] at-spi2: add -core and -atk, for GTK+ 3.8 Ross Burton
2013-06-03 20:39   ` Saul Wold
2013-06-04 14:26     ` Martin Jansa
2013-06-04 21:38       ` Martin Jansa [this message]
2013-06-04 15:06   ` Martin Jansa
2013-05-31 15:05 ` [PATCH 03/11] gtk+3: update to 3.8.2 Ross Burton
2013-05-31 15:05 ` [PATCH 04/11] gtk+3: explicitly disable introspection Ross Burton
2013-05-31 15:05 ` [PATCH 05/11] gtk+3: respect x11 and wayland DISTRO_FEATURES Ross Burton
2013-05-31 15:05 ` [PATCH 06/11] gtk+3: add dependencies for gtk+3-demo Ross Burton
2013-05-31 15:05 ` [PATCH 07/11] gtk+: remove spurious libgcrypt dependency Ross Burton
2013-05-31 15:05 ` [PATCH 08/11] gtk+3: register GSetting schemas Ross Burton
2013-05-31 15:05 ` [PATCH 09/11] gtk+3: split into .bb/.inc Ross Burton
2013-05-31 15:05 ` [PATCH 10/11] gtk+3: clean up libtool link creation to avoid errors in configure log Ross Burton
2013-05-31 15:05 ` [PATCH 11/11] gtk+3: fix repainting under Weston 1.1 Ross Burton
2013-06-06 16:52 ` [PATCH 00/11] GTK+ 3 updates Saul Wold

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=20130604213835.GC30727@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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