From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] rpm5
Date: Fri, 12 Oct 2012 00:45:01 +0200 [thread overview]
Message-ID: <50774BED.9040400@mind.be> (raw)
In-Reply-To: <CABtOAfwz7TLgP5qf6HKhFnK-isC92GRxgjTjLM9VsW_B5xYrxA@mail.gmail.com>
On 12/10/12 00:27, Alexander Khryukin wrote:
> I wrote a simple patch that enables support of -lgomp instead of $LIB_GOMP macro
LIB_GOMP should have been set to -lgomp if openmp is enabled, so that patch
wouldn't do much AFAICS.
Oh, but now I see the real issue: in beecrypt's acinclude.m4, they check for
$OPENMP_CFLAGS to decide if OPENMP_LIBS should be set. But you don't need to
pass any option to enable openmp, so $OPENMP_CFLAGS is empty... Instead it
should check for $ac_cv_prog_c_openmp.
Since AFAIK we have no toolchain that supports OpenMP in buildroot, I'm not
sure if it makes sense to patch it in buildroot...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-10-11 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 11:28 [Buildroot] rpm5 Alexander Khryukin
2012-10-09 20:46 ` Arnout Vandecappelle
2012-10-10 14:40 ` Alexander Khryukin
2012-10-10 17:21 ` Alexander Khryukin
2012-10-11 10:04 ` Alexander Khryukin
2012-10-11 14:14 ` Stefan Fröberg
2012-10-11 14:30 ` Stefan Fröberg
2012-10-11 15:38 ` Alexander Khryukin
2012-10-11 16:39 ` Alexander Khryukin
2012-10-11 22:14 ` Arnout Vandecappelle
2012-10-11 22:27 ` Alexander Khryukin
2012-10-11 22:45 ` Arnout Vandecappelle [this message]
2012-10-11 23:51 ` Gustavo Zacarias
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=50774BED.9040400@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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