Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] rpm5
Date: Thu, 11 Oct 2012 20:51:59 -0300	[thread overview]
Message-ID: <50775B9F.8030101@zacarias.com.ar> (raw)
In-Reply-To: <50774BED.9040400@mind.be>

On 10/11/12 19:45, Arnout Vandecappelle wrote:

>  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...

The internal toolchain has support/an option for OpenMP
(BR2_ENABLE_GCC_OPENMP).
So it should probably be handled in the beecrypt package.
Regards.

      reply	other threads:[~2012-10-11 23:51 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
2012-10-11 23:51           ` Gustavo Zacarias [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=50775B9F.8030101@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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