From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/lockrun/
Date: Sun, 20 Mar 2022 00:38:37 +0000 (UTC) [thread overview]
Message-ID: <1647736639.fb8de3f06e8b503c958b5a0f14b88c19d3195359.sam@gentoo> (raw)
commit: fb8de3f06e8b503c958b5a0f14b88c19d3195359
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 20 00:37:19 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 20 00:37:19 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fb8de3f0
dev-util/lockrun: [QA] fix tc-get* quoting
This can cause build problems for e.g. 32-bit (gcc -m32 ...)
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/lockrun/lockrun-20120508-r1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-util/lockrun/lockrun-20120508-r1.ebuild b/dev-util/lockrun/lockrun-20120508-r1.ebuild
index 33e668a9dea2..0500a760ea84 100644
--- a/dev-util/lockrun/lockrun-20120508-r1.ebuild
+++ b/dev-util/lockrun/lockrun-20120508-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -20,7 +20,7 @@ src_unpack() {
}
src_compile() {
- emake CC=$(tc-getCC) ${PN}
+ emake CC="$(tc-getCC)" ${PN}
sed -i README -e '60q;s|^ \*||g' || die
}
next reply other threads:[~2022-03-20 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 0:38 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 9:27 [gentoo-commits] repo/gentoo:master commit in: dev-util/lockrun/ Sam James
2024-07-24 9:27 Sam James
2024-04-17 11:17 Michael Orlitzky
2023-08-26 14:11 Andreas Sturmlechner
2023-08-26 14:08 Sam James
2023-08-26 14:08 Sam James
2023-07-05 20:49 Conrad Kostecki
2018-05-27 12:01 Pacho Ramos
2018-02-25 18:21 Thomas Deutschmann
2018-02-24 8:07 Jason Zaman
2017-06-22 21:58 Patrice Clement
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=1647736639.fb8de3f06e8b503c958b5a0f14b88c19d3195359.sam@gentoo \
--to=sam@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