Openembedded Devel Discussions
 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: Wed, 15 Feb 2017 08:28:38 +0100	[thread overview]
Message-ID: <1487143718.13854.368.camel@intel.com> (raw)
In-Reply-To: <CA+chaQfovfgVG6oiWcc=SV5ssZ-6qDY5z_AWg2pGoHZqNaum7Q@mail.gmail.com>

On Tue, 2017-02-14 at 21:06 +0100, Martin Jansa wrote:
> Or you can try to force arm mode for multipath-tools build (by setting
> ARM_INSTRUCTION_SET in the recipe).

That's probably the easiest solution - I'll do that. Thanks for the
hint.

-- 
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-15  7:28 UTC|newest]

Thread overview: 11+ 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-13 12:36 ` Burton, Ross
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 17:28   ` Patrick Ohly
2017-02-14 18:08     ` Martin Jansa
2017-02-14 19:46       ` Patrick Ohly
2017-02-14 20:06         ` Martin Jansa
2017-02-15  7:28           ` Patrick Ohly [this message]

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=1487143718.13854.368.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox