From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-biology/bowtie/
Date: Wed, 14 Oct 2015 12:48:05 +0000 (UTC) [thread overview]
Message-ID: <1444826878.1f3b594dde68ff07ecf429b10b2501660adc0f1d.jlec@gentoo> (raw)
commit: 1f3b594dde68ff07ecf429b10b2501660adc0f1d
Author: Ted Tanberry <ted.tanberry <AT> gmail <DOT> com>
AuthorDate: Sat Oct 10 20:18:12 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Wed Oct 14 12:47:58 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f3b594d
sci-biology/bowtie: remove REQUIRED_USE
When SSE2 support is not explicitly enabled, the user is
informed by erroring out instead of portage recommending
enabling cpu flags.
sci-biology/bowtie/bowtie-2.2.6.ebuild | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/sci-biology/bowtie/bowtie-2.2.6.ebuild b/sci-biology/bowtie/bowtie-2.2.6.ebuild
index 50aca7e..c15de56 100644
--- a/sci-biology/bowtie/bowtie-2.2.6.ebuild
+++ b/sci-biology/bowtie/bowtie-2.2.6.ebuild
@@ -15,7 +15,6 @@ SLOT="2"
KEYWORDS="~amd64 ~x86"
IUSE="examples cpu_flags_x86_sse2 tbb"
-REQUIRED_USE="cpu_flags_x86_sse2"
RDEPEND="dev-lang/perl"
DEPEND="${RDEPEND}
@@ -27,6 +26,13 @@ S="${WORKDIR}/${PN}2-${PV}"
DOCS=( AUTHORS NEWS TUTORIAL )
HTML_DOCS=( doc/{manual.html,style.css} )
+pkg_pretend() {
+ if ! use cpu_flags_x86_sse2 ; then
+ eerror "This package requires a CPU supporting the SSE2 instruction set."
+ die "SSE2 support missing"
+ fi
+}
+
src_compile() {
emake \
CC="$(tc-getCC)" \
next reply other threads:[~2015-10-14 12:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 12:48 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-30 21:13 [gentoo-commits] repo/gentoo:master commit in: sci-biology/bowtie/ Pacho Ramos
2023-02-24 7:30 Andrew Ammerlaan
2021-08-01 17:02 David Seifert
2021-08-01 16:41 David Seifert
2017-12-25 16:09 David Seifert
2016-06-04 21:17 David Seifert
2016-04-10 9:48 David Seifert
2015-12-26 18:05 Justin Lecher
2015-12-25 16:20 Agostino Sarubbo
2015-12-25 15:42 Agostino Sarubbo
2015-12-25 15:42 Agostino Sarubbo
2015-10-14 12:48 Justin Lecher
2015-10-14 12:48 Justin Lecher
2015-10-14 12:48 Justin Lecher
2015-10-14 12:48 Justin Lecher
2015-10-14 12:48 Justin Lecher
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=1444826878.1f3b594dde68ff07ecf429b10b2501660adc0f1d.jlec@gentoo \
--to=jlec@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