Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] webkitgtk, gcr, libsecret: force ARM mode
Date: Sun, 11 Oct 2015 10:51:08 +0100	[thread overview]
Message-ID: <1444557068.2003.0.camel@pbcl.net> (raw)
In-Reply-To: <1444403489-29494-1-git-send-email-Martin.Jansa@gmail.com>

On Fri, 2015-10-09 at 17:11 +0200, Martin Jansa wrote:
> * gcr, libsecret are new since switch to gcc 5.2

The problem with libsecret seems to be caused by its valgrind support
code (which contains asm statements that only work in ARM state).  I
wonder if you can just turn WITH_VALGRIND off rather than forcing
ARM-state for the whole library.

p.




  parent reply	other threads:[~2015-10-11  9:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 12:30 [PATCH] guile, mailx, gcc, opensp, gstreamer1.0-libav, libunwind: disable thumb where it fails for qemuarm Martin Jansa
2015-05-14 10:48 ` Richard Purdie
2015-05-14 11:40   ` Martin Jansa
2015-10-09 15:11     ` [PATCH] webkitgtk, gcr, libsecret: force ARM mode Martin Jansa
2015-10-10 12:13       ` Carlos Alberto Lopez Perez
2015-10-10 15:32         ` Martin Jansa
2015-10-10 21:45           ` Carlos Alberto Lopez Perez
2015-10-10 21:59             ` Khem Raj
2015-10-12  8:03             ` Martin Jansa
2015-10-12 11:17             ` Alexander Kanavin
2015-10-12 22:26               ` Carlos Alberto Lopez Perez
2015-10-10 19:15         ` Khem Raj
2015-10-11  9:51       ` Phil Blundell [this message]
2015-10-12 16:21         ` Burton, Ross
2015-10-14 11:22 ` [PATCH] guile, mailx, gcc, opensp, gstreamer1.0-libav, libunwind: disable thumb where it fails for qemuarm 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=1444557068.2003.0.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@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