From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/mingw64-toolchain/
Date: Fri, 13 May 2022 06:53:21 +0000 (UTC) [thread overview]
Message-ID: <1652424774.2a3c0f5024be20d4604d7a686039cbee6cd36a30.ionen@gentoo> (raw)
commit: 2a3c0f5024be20d4604d7a686039cbee6cd36a30
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Fri May 13 06:46:43 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Fri May 13 06:52:54 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a3c0f50
dev-util/mingw64-toolchain: disable gcov
Doesn't make sense for this package and if going to cause issues...
Closes: https://bugs.gentoo.org/843989
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-util/mingw64-toolchain/mingw64-toolchain-10.0.0.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-util/mingw64-toolchain/mingw64-toolchain-10.0.0.ebuild b/dev-util/mingw64-toolchain/mingw64-toolchain-10.0.0.ebuild
index 1ae7b097c037..4df5573bc1e4 100644
--- a/dev-util/mingw64-toolchain/mingw64-toolchain-10.0.0.ebuild
+++ b/dev-util/mingw64-toolchain/mingw64-toolchain-10.0.0.ebuild
@@ -111,6 +111,7 @@ src_compile() {
--host=${CHOST}
--disable-bootstrap
--disable-cet
+ --disable-gcov #843989
--disable-gomp
--disable-libquadmath
--disable-libsanitizer
next reply other threads:[~2022-05-13 6:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 6:53 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 6:53 [gentoo-commits] repo/gentoo:master commit in: dev-util/mingw64-toolchain/ Jakov Smolić
2022-05-17 6:53 Jakov Smolić
2022-05-28 19:26 Ionen Wolkens
2022-06-28 5:56 Ionen Wolkens
2022-07-16 17:03 Ionen Wolkens
2022-08-20 13:45 Ionen Wolkens
2022-08-20 13:45 Ionen Wolkens
2022-08-20 13:58 Ionen Wolkens
2022-08-29 6:55 Ionen Wolkens
2022-08-29 6:55 Ionen Wolkens
2022-09-14 19:39 Ionen Wolkens
2022-09-14 21:12 Ionen Wolkens
2022-09-14 23:11 Ionen Wolkens
2022-09-16 7:47 Ionen Wolkens
2022-09-16 7:54 Ionen Wolkens
2022-09-16 16:17 Ionen Wolkens
2022-10-23 7:20 Ionen Wolkens
2022-10-31 0:54 Ionen Wolkens
2022-11-12 11:33 Ionen Wolkens
2023-01-15 7:00 Ionen Wolkens
2023-02-01 21:04 Ionen Wolkens
2023-04-26 8:37 Ionen Wolkens
2023-04-26 8:37 Ionen Wolkens
2023-04-29 9:43 Ionen Wolkens
2023-05-11 17:01 Ionen Wolkens
2023-05-19 1:41 Ionen Wolkens
2023-05-29 15:06 Sam James
2023-05-29 17:49 Arthur Zamarin
2023-06-26 10:12 Ionen Wolkens
2023-07-03 20:55 Ionen Wolkens
2023-07-28 5:16 Ionen Wolkens
2023-07-30 16:52 Ionen Wolkens
2023-08-04 3:25 Ionen Wolkens
2023-08-04 3:25 Ionen Wolkens
2023-08-27 1:28 Sam James
2023-08-27 17:18 Sam James
2023-12-22 17:38 Ionen Wolkens
2024-01-16 17:52 Ionen Wolkens
2024-02-22 14:27 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-05-07 14:28 Ionen Wolkens
2024-05-07 14:28 Ionen Wolkens
2024-05-07 17:49 Ionen Wolkens
2024-05-10 3:03 Ionen Wolkens
2024-05-10 10:12 Ionen Wolkens
2024-05-21 3:01 Ionen Wolkens
2024-05-22 3:32 Ionen Wolkens
2024-05-30 6:39 Ionen Wolkens
2024-06-02 3:54 Ionen Wolkens
2024-06-06 13:20 Ionen Wolkens
2024-07-02 21:09 Jakov Smolić
2024-07-02 21:09 Jakov Smolić
2024-09-03 12:31 Ionen Wolkens
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=1652424774.2a3c0f5024be20d4604d7a686039cbee6cd36a30.ionen@gentoo \
--to=ionen@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