All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] beecrypt: enable OpenMP if Buildroot GCC supports it
Date: Sat, 13 Oct 2012 15:29:21 +0200	[thread overview]
Message-ID: <50796CB1.8040106@mind.be> (raw)
In-Reply-To: <50796BDA.3040008@petroprogram.com>

On 13/10/12 15:25, Stefan Fr?berg wrote:
> And the automatic detection didn't work for Alexander and he was even
> using the internal toolchain

  The automatic detection did work (and it's part of autoconf, BTW).  However,
beecrypt uses the OPENMP_CFLAGS given by autoconf to determine if OpenMP is
available or not - but OPENMP_CFLAGS may be empty if OpenMP is already enabled
without any CFLAGS.  So it should instead check on ac_cv_prog_c_openmp.

  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

  reply	other threads:[~2012-10-13 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 19:54 [Buildroot] [PATCH] beecrypt: enable OpenMP if Buildroot GCC supports it Stefan Fröberg
2012-10-13  9:29 ` Arnout Vandecappelle
2012-10-13 13:25   ` Stefan Fröberg
2012-10-13 13:29     ` Arnout Vandecappelle [this message]
2012-10-13 14:07       ` Stefan Fröberg
2012-10-13 14:54         ` Alexander Khryukin
2012-10-13 15:07           ` Stefan Fröberg
2012-10-13 20:56           ` Arnout Vandecappelle

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=50796CB1.8040106@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 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.