public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/binutils-apple/
Date: Wed, 20 Apr 2022 06:15:44 +0000 (UTC)	[thread overview]
Message-ID: <1650435341.4e2f7063a89cd6ad368706c9a433ce7833aa5b21.grobian@gentoo> (raw)

commit:     4e2f7063a89cd6ad368706c9a433ce7833aa5b21
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 20 06:13:50 2022 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Wed Apr 20 06:15:41 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e2f7063

sys-devel/binutils-apple-8.2.1-r1: fix clang check #839156

shellcheck pointed out that checking a non-empty string constant to be
non-empty always evaluates to true

Closes: https://bugs.gentoo.org/839156
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 sys-devel/binutils-apple/binutils-apple-8.2.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-devel/binutils-apple/binutils-apple-8.2.1-r1.ebuild b/sys-devel/binutils-apple/binutils-apple-8.2.1-r1.ebuild
index 06e3523c934f..b38e12eebe33 100644
--- a/sys-devel/binutils-apple/binutils-apple-8.2.1-r1.ebuild
+++ b/sys-devel/binutils-apple/binutils-apple-8.2.1-r1.ebuild
@@ -335,7 +335,7 @@ install_cctools() {
 }
 
 src_test() {
-	if ! [ "${EPREFIX}"/usr/bin/clang ] ; then
+	if ! [[ -x "${EPREFIX}"/usr/bin/clang ]] ; then
 		einfo "Test suite only works properly with clang - please install"
 		return
 	fi


             reply	other threads:[~2022-04-20  6:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  6:15 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-27 14:44 [gentoo-commits] repo/gentoo:master commit in: sys-devel/binutils-apple/ Fabian Groffen
2024-01-16 12:05 Fabian Groffen
2023-07-09 12:20 Fabian Groffen
2023-07-09 11:50 Fabian Groffen
2023-05-29 11:58 Fabian Groffen
2022-12-12 20:13 Fabian Groffen
2022-03-29 11:31 Fabian Groffen
2021-01-10 10:05 Fabian Groffen
2021-01-06 15:32 Fabian Groffen
2020-12-31 12:17 Fabian Groffen
2020-12-22 20:25 Fabian Groffen
2020-12-21 17:57 Fabian Groffen
2020-12-21  8:32 Fabian Groffen
2020-12-20 18:47 Fabian Groffen
2020-12-20 16:06 Fabian Groffen
2020-12-19 19:51 Fabian Groffen
2020-12-19 19:07 Fabian Groffen
2020-11-27 15:33 Fabian Groffen
2019-03-16 14:59 Fabian Groffen
2019-01-28 10:37 Fabian Groffen
2018-12-22 11:02 Fabian Groffen
2018-12-13 10:47 Fabian Groffen
2018-12-13  8:35 Fabian Groffen
2018-12-13  7:28 Fabian Groffen
2018-12-10 14:20 Fabian Groffen
2018-01-04 16:46 Fabian Groffen
2018-01-03 20:52 Fabian Groffen
2018-01-03 20:52 Fabian Groffen
2017-12-29 13:50 Fabian Groffen
2017-09-06 21:00 Michał Górny
2017-02-26 19:06 Fabian Groffen
2017-01-01 13:17 Fabian Groffen
2016-12-22  7:44 Fabian Groffen
2016-12-15 15:01 Fabian Groffen
2016-09-10 14:40 Fabian Groffen
2016-09-10 14:08 Fabian Groffen
2016-07-10 21:59 Patrick Lauer
2016-07-10 17:32 Fabian Groffen
2016-05-20 16:15 Fabian Groffen
2016-05-16 19:11 Fabian Groffen
2016-05-16 15:44 Fabian Groffen

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=1650435341.4e2f7063a89cd6ad368706c9a433ce7833aa5b21.grobian@gentoo \
    --to=grobian@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