From: Mike Looijmans <mike.looijmans@topic.nl>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Building with OpenMP support in OE fails on #include <omp.h>
Date: Mon, 2 Mar 2015 15:54:04 +0100 [thread overview]
Message-ID: <54F4798C.8070402@topic.nl> (raw)
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
Maybe something missing in the OE compiler options for the compiler?
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
next reply other threads:[~2015-03-02 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 14:54 Mike Looijmans [this message]
2015-03-02 15:45 ` Building with OpenMP support in OE fails on #include <omp.h> Paul Eggleton
2015-03-02 17:31 ` Mike Looijmans
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=54F4798C.8070402@topic.nl \
--to=mike.looijmans@topic.nl \
--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