From: Patrick Ohly <patrick.ohly@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] libjpeg-turbo: don't depend on NASM for non-x86 targets
Date: Tue, 04 Apr 2017 10:08:38 +0200 [thread overview]
Message-ID: <1491293318.10884.19.camel@intel.com> (raw)
In-Reply-To: <CAJTo0LZW1_=jroQsTQ5E+hz0LpCz3tOaWvVH-pB6X9Bj4gzPyg@mail.gmail.com>
On Mon, 2017-04-03 at 18:25 +0100, Burton, Ross wrote:
>
> On 3 April 2017 at 18:03, Andre McCurdy <armccurdy@gmail.com> wrote:
> > +EXTRA_OECONF_append_class-native = "--without-simd"
>
>
> Missing space?
>
>
> Argh. V3 incoming.
I'm so glad that this can happen even to the best of us and not just
me ;-}
--
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.
prev parent reply other threads:[~2017-04-04 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 12:04 [PATCH V2] libjpeg-turbo: don't depend on NASM for non-x86 targets Ross Burton
2017-04-03 17:03 ` Andre McCurdy
2017-04-03 17:25 ` Burton, Ross
2017-04-04 8:08 ` 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=1491293318.10884.19.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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