Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Carlos Alberto Lopez Perez <clopez@igalia.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] webkitgtk, gcr, libsecret: force ARM mode
Date: Mon, 12 Oct 2015 10:03:05 +0200	[thread overview]
Message-ID: <20151012080305.GA2392@jama> (raw)
In-Reply-To: <56198707.8@igalia.com>

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

On Sat, Oct 10, 2015 at 11:45:43PM +0200, Carlos Alberto Lopez Perez wrote:
> On 10/10/15 17:32, Martin Jansa wrote:
> > Did you enable thumb in that build? It's not enabled by default.
> > 
> > ARM_INSTRUCTION_SET is for recipes to use arm when distro selects thumb by
> > default.
> 
> I assumed it was enabled by default if it was listed on the list printed
> on TUNE_FEATURES when starting bitbake. Seems not.
> 
> I manually enabled it on the recipe of webkitgtk+ by setting
> 'ARM_INSTRUCTION_SET = "thumb"' and I was able to reproduce the build
> failure.
> 
> However, later I tried doing the same for a standard armv7a machine and
> it built fine.
> 
> qemuarm is arvm6 with thumb1, and any armv7 or newer machine will prefer
> thumb2 instead. The compiler would automatically use thumb2 when
> enabling -mthumb on a armv7 or newer march.
> 
> So, it built fine with -march=armv7-a -mthumb
> 
> Given that most people building webkitgtk+ will use armv7 or newer, I
> don't think disabling the possibility of building webkitgtk+ with thumb
> (thumb2) unconditionally is a good idea.
> 
> I also tested to build gcr and libsecret. Both build also fine with
> -mthumb on armv7.
> 
> 
> So, could we set ARM_INSTRUCTION_SET=arm only for armv6 or older
> machines in this 3 recipes?

Yes, that would be better, I'm still waiting for answer about other
layers, see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7717#c6

In the meantime I'm using this to keep my world builds going.

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

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

  parent reply	other threads:[~2015-10-12  8:02 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 [this message]
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
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=20151012080305.GA2392@jama \
    --to=martin.jansa@gmail.com \
    --cc=clopez@igalia.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