From: "Benda XU" <heroxbd@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/openblas/
Date: Mon, 28 Aug 2017 07:37:22 +0000 (UTC) [thread overview]
Message-ID: <1503905823.0e143007295f7fe3fe1b5f9506817216d5eb80e2.heroxbd@gentoo> (raw)
commit: 0e143007295f7fe3fe1b5f9506817216d5eb80e2
Author: Benda Xu <heroxbd <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 28 07:37:03 2017 +0000
Commit: Benda XU <heroxbd <AT> gentoo <DOT> org>
CommitDate: Mon Aug 28 07:37:03 2017 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=0e143007
sci-libs/openblas: USE flags of single-threaded version.
When neither openmp nor threads USE flag is set, OpenBLAS
should build a single-threaded version with make option
USE_THREAD=0.
Package-Manager: Portage-2.3.3, Repoman-2.3.1
sci-libs/openblas/openblas-0.2.20.ebuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sci-libs/openblas/openblas-0.2.20.ebuild b/sci-libs/openblas/openblas-0.2.20.ebuild
index c15c6eb73..838c334d6 100644
--- a/sci-libs/openblas/openblas-0.2.20.ebuild
+++ b/sci-libs/openblas/openblas-0.2.20.ebuild
@@ -40,6 +40,8 @@ get_openblas_flags() {
openblas_flags+=( USE_THREAD=1 USE_OPENMP=0 )
elif use openmp; then
openblas_flags+=( USE_OPENMP=1 )
+ else
+ openblas_flags+=( USE_THREAD=0 ) # single-threaded
fi
local profname=$(numeric-int64_get_module_name)
local libname="${profname//-/_}"
next reply other threads:[~2017-08-28 7:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 7:37 Benda XU [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-25 6:28 [gentoo-commits] proj/sci:master commit in: sci-libs/openblas/ Benda XU
2017-06-06 4:12 Benda XU
2017-04-30 10:25 Justin Lecher
2017-04-02 4:21 Benda XU
2016-02-21 15:16 Justin Lecher
2015-11-30 10:58 Justin Lecher
2015-11-30 10:58 Justin Lecher
2015-06-06 10:23 Justin Lecher
2015-06-06 10:23 Justin Lecher
2015-04-02 10:15 Justin Lecher
2015-04-02 10:15 Justin Lecher
2015-03-27 20:25 Denis Dupeyron
2014-10-20 18:01 Justin Lecher
2014-10-20 12:32 Mark Wright
2014-10-19 10:21 Mark Wright
2014-10-19 5:55 Mark Wright
2014-10-06 5:56 Justin Lecher
2014-10-06 5:56 Justin Lecher
2014-10-06 5:56 Justin Lecher
2014-10-06 5:56 Justin Lecher
2014-10-06 5:56 Justin Lecher
2014-10-06 5:56 Justin Lecher
2014-01-06 18:33 Justin Lecher
2013-08-06 15:49 Sebastien Fabbro
2013-07-24 23:09 Sebastien Fabbro
2013-03-03 18:39 Sebastien Fabbro
2013-03-03 18:39 Sebastien Fabbro
2012-12-12 19:28 Sebastien Fabbro
2012-10-15 20:15 Andrea Arteaga
2012-10-08 17:35 Andrea Arteaga
2012-08-20 9:21 Andrea Arteaga
2012-06-26 22:27 Sebastien Fabbro
2012-05-07 14:57 Andrea Arteaga
2012-05-07 14:50 Andrea Arteaga
2012-03-23 20:45 Andrea Arteaga
2012-03-16 21:41 Sebastien Fabbro
2012-03-15 22:08 Francois Bissey
2012-03-15 22:01 Francois Bissey
2012-03-15 2:34 Francois Bissey
2011-08-17 17:21 Alexey Shvetsov
2011-08-17 15:45 Sebastien Fabbro
2011-08-16 23:51 Francois Bissey
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=1503905823.0e143007295f7fe3fe1b5f9506817216d5eb80e2.heroxbd@gentoo \
--to=heroxbd@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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