From: Mike Looijmans <mike.looijmans@topic.nl>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Building with OpenMP support in OE fails on #include <omp.h>
Date: Mon, 02 Mar 2015 18:31:08 +0100 [thread overview]
Message-ID: <54F49E5C.7020408@topic.nl> (raw)
In-Reply-To: <5774096.IiVkEzFHVb@peggleto-mobl5.ger.corp.intel.com>
On 02-03-15 16:45, Paul Eggleton wrote:
> Hi Mike,
>
> On Monday 02 March 2015 15:54:04 Mike Looijmans wrote:
>> Here's the problem, running in a devshell:
>>
>> # echo '#include <omp.h>' > /tmp/compileme.c
>> # $CC -c -fopenmp /tmp/compileme.c
>> /tmp/compileme.c:1:17: fatal error: omp.h: No such file or directory
>> #include <omp.h>
>> ^
>> compilation terminated.
>>
>>
>> The #pragma's and linking of OpenMP work just fine, it's just the inclusion
>> of omp.h that appears to fail.
>>
>> What I was actually trying to do is to activate OpenMP in OpenCV to get
>> decent performance on a multicore ARM system. But this is holding me back
>> now.
>>
>> Looking in the sysroots reveals that the include file is actually there:
>>
>> $ find tmp-glibc/sysroots/topic-miami-florida-med-xc7z030 -name omp.h
>> tmp-glibc/sysroots/topic-miami-florida-med-xc7z030/usr/lib/gcc/arm-oe-linux-
>> gnueabi/4.9.1/include/omp.h
>
> Funnily enough this is an issue I fixed a few weeks ago - here's the bug which
> contains a link to the fix:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7141
Ah okay, I'll upgrade to current master and retest.
If it works, I'll post the patch to make opencv build with openmp.
--
Mike Looijmans
next prev parent reply other threads:[~2015-03-02 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 14:54 Building with OpenMP support in OE fails on #include <omp.h> Mike Looijmans
2015-03-02 15:45 ` Paul Eggleton
2015-03-02 17:31 ` Mike Looijmans [this message]
2015-03-05 10:32 ` Mike Looijmans
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=54F49E5C.7020408@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 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.