All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: multipath-tools on arm (was: Re: [OE-core] State of bitbake world, Failed tasks 2017-02-08)
Date: Tue, 14 Feb 2017 20:46:48 +0100	[thread overview]
Message-ID: <1487101608.13854.367.camel@intel.com> (raw)
In-Reply-To: <CA+chaQc+pT3pj-MJFHY=AJBdqgdrhqNmqM+k1KDm8-Nfir02Sw@mail.gmail.com>

On Tue, 2017-02-14 at 19:08 +0100, Martin Jansa wrote:
> Have you tried to reproduce it in qemuarm build after enabling thumb
> in poky?
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9213

No, I haven't. I'm not familiar with the exact configuration of these
tests, and from http://errors.yoctoproject.org/Errors/Details/130529/
it's not obvious that one needs anything besides MACHINE=qemuarm to
replicate the problem.

Bug #9213 doesn't say how thumb can be enabled, and the bug #7717 that
it links to isn't very clear about it either. Ross suggested on IRC:

PREFERRED_ARM_INSTRUCTION_SET ?= "thumb"
ARM_INSTRUCTION_SET = "${PREFERRED_ARM_INSTRUCTION_SET}"

Is that right? Yes, seems to be - using it I can reproduce the problem.

It seems to be a known problem. valgrind is marked as incompatible with
older ARM, so the solution has to be to disable the use of these
valgrind macros. Should I do that unconditionally?

Doing it conditionally would imply copying the logic from valgrind.bb:

# valgrind supports armv7 and above
COMPATIBLE_HOST_armv4 = 'null'
COMPATIBLE_HOST_armv5 = 'null'
COMPATIBLE_HOST_armv6 = 'null'

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-02-14 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10  8:28 State of bitbake world, Failed tasks 2017-02-08 Martin Jansa
2017-02-10 16:26 ` Martin Jansa
2017-02-10 20:20   ` [OE-core] " Andreas Müller
2017-02-10 20:20     ` Andreas Müller
2017-02-13 12:36 ` [OE-core] " Burton, Ross
2017-02-13 12:36   ` Burton, Ross
2017-02-13 14:02   ` [OE-core] " Martin Jansa
2017-02-13 14:02     ` Martin Jansa
2017-02-14 15:35 ` multipath-tools on arm (was: Re: [OE-core] State of bitbake world, Failed tasks 2017-02-08) Patrick Ohly
2017-02-14 15:35   ` multipath-tools on arm (was: " Patrick Ohly
2017-02-14 17:28   ` multipath-tools on arm (was: Re: [OE-core] " Patrick Ohly
2017-02-14 18:08     ` Martin Jansa
2017-02-14 19:46       ` Patrick Ohly [this message]
2017-02-14 20:06         ` Martin Jansa
2017-02-15  7:28           ` Patrick Ohly
2017-02-14 17:28   ` multipath-tools on arm (was: " Phil Blundell

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=1487101608.13854.367.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=martin.jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.