public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pycparser/
Date: Sun, 24 May 2020 19:40:25 +0000 (UTC)	[thread overview]
Message-ID: <1590349221.ebbffbddc263b9dc81fc8081165f2c26dac945f8.floppym@gentoo> (raw)

commit:     ebbffbddc263b9dc81fc8081165f2c26dac945f8
Author:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sun May 24 19:39:37 2020 +0000
Commit:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sun May 24 19:40:21 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ebbffbdd

dev-python/pycparser: skip tests if cpp is not in PATH

Bug: https://bugs.gentoo.org/719934
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>

 dev-python/pycparser/pycparser-2.20.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-python/pycparser/pycparser-2.20.ebuild b/dev-python/pycparser/pycparser-2.20.ebuild
index 4b222c379ee..12172c1c82e 100644
--- a/dev-python/pycparser/pycparser-2.20.ebuild
+++ b/dev-python/pycparser/pycparser-2.20.ebuild
@@ -41,6 +41,8 @@ python_compile() {
 }
 
 python_test() {
+	# Skip tests if cpp is not in PATH
+	type -P cpp >/dev/null || return 0
 	# change workdir to avoid '.' import
 	cd tests || die
 	"${EPYTHON}" -m unittest discover -v || die "Tests fail with ${EPYTHON}"


             reply	other threads:[~2020-05-24 19:40 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 19:40 Mike Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-10 18:38 [gentoo-commits] repo/gentoo:master commit in: dev-python/pycparser/ Michał Górny
2024-04-20  9:45 Michał Górny
2024-03-31  3:10 Michał Górny
2023-05-24  7:48 Sam James
2023-03-26  2:27 Michał Górny
2023-03-26  0:51 Sam James
2023-02-23 15:14 Michał Górny
2023-02-23 15:14 Michał Górny
2023-02-23 15:14 Michał Górny
2023-02-06  5:27 Sam James
2022-06-12 14:25 Michał Górny
2022-06-12 12:46 Sam James
2022-06-12  5:51 Michał Górny
2022-05-10 21:52 Michał Górny
2022-05-10 21:52 Michał Górny
2021-12-28 20:54 Michał Górny
2021-12-28 20:52 Arthur Zamarin
2021-12-28 20:41 Sam James
2021-12-28 19:51 Arthur Zamarin
2021-12-27 19:18 Jakov Smolić
2021-12-27 19:18 Jakov Smolić
2021-12-27 19:08 Arthur Zamarin
2021-12-27 18:48 Arthur Zamarin
2021-12-27 18:48 Arthur Zamarin
2021-11-26  8:57 Sam James
2021-11-26  8:20 Sam James
2021-08-13  6:58 Michał Górny
2021-05-05 19:14 Michał Górny
2020-09-25 20:04 Michał Górny
2020-05-25 19:27 Michał Górny
2020-05-19 19:47 Mike Gilbert
2020-05-11 17:48 Michał Górny
2020-05-08 20:58 Mart Raudsepp
2020-05-08  9:36 Sergei Trofimovich
2020-05-04 16:51 Agostino Sarubbo
2020-05-03 15:13 Agostino Sarubbo
2020-05-03 13:00 Agostino Sarubbo
2020-05-03 12:58 Agostino Sarubbo
2020-05-03 12:31 Agostino Sarubbo
2020-05-03 12:28 Agostino Sarubbo
2020-05-02 21:28 Mike Gilbert
2020-03-05  5:50 Michał Górny
2019-12-04  6:48 Aaron Bauman
2019-11-18 16:18 Mike Gilbert
2019-11-17 22:59 Mike Gilbert
2019-11-16 23:00 Michał Górny
2019-11-16 23:00 Michał Górny
2018-11-25  9:09 Michał Górny
2018-11-25  9:09 Michał Górny
2018-11-19 21:15 Fabian Groffen
2018-02-21 20:18 Michał Górny
2017-08-27 18:16 Michał Górny
2017-08-27 18:14 Michał Górny
2017-08-27 18:07 Michał Górny
2017-08-20  3:34 Tim Harder
2017-05-03 11:02 Michał Górny
2017-01-29 17:15 Fabian Groffen
2016-11-03  9:15 Lars Wendler
2016-10-25 14:19 Mike Gilbert
2016-10-24 16:00 Mike Gilbert
2016-10-24 15:57 Mike Gilbert
2016-10-24 12:43 Lars Wendler
2016-09-14  5:19 Tim Harder
2016-06-21  2:47 Mike Frysinger
2015-10-18 16:48 Mikle Kolyada
2015-09-24 11:50 Justin Lecher
2015-09-24 10:36 Agostino Sarubbo
2015-09-20  9:30 Agostino Sarubbo
2015-08-25  5:38 Jeroen Roovers
2015-08-21 16:47 Markus Meier
2015-08-16 18:01 Mikle Kolyada

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=1590349221.ebbffbddc263b9dc81fc8081165f2c26dac945f8.floppym@gentoo \
    --to=floppym@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