From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-chemistry/gperiodic/
Date: Sun, 20 Mar 2022 18:51:45 +0000 (UTC) [thread overview]
Message-ID: <1647802261.388616e6c095680bbf3480bfd076a2c34ba67dd5.sam@gentoo> (raw)
commit: 388616e6c095680bbf3480bfd076a2c34ba67dd5
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 20 18:49:44 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 20 18:51:01 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=388616e6
sci-chemistry/gperiodic: [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>
sci-chemistry/gperiodic/gperiodic-3.0.3.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sci-chemistry/gperiodic/gperiodic-3.0.3.ebuild b/sci-chemistry/gperiodic/gperiodic-3.0.3.ebuild
index 2ffd7a303310..f4f87a9e8395 100644
--- a/sci-chemistry/gperiodic/gperiodic-3.0.3.ebuild
+++ b/sci-chemistry/gperiodic/gperiodic-3.0.3.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=7
@@ -27,7 +27,7 @@ src_compile() {
emake \
CFLAGS="${CFLAGS}" \
LDFLAGS="${LDFLAGS}" \
- CC=$(tc-getCC) "enable_nls=$(usex nls 1 0)"
+ CC="$(tc-getCC)" "enable_nls=$(usex nls 1 0)"
}
src_install() {
next reply other threads:[~2022-03-20 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 18:51 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-30 6:34 [gentoo-commits] repo/gentoo:master commit in: sci-chemistry/gperiodic/ Agostino Sarubbo
2020-06-22 6:57 Agostino Sarubbo
2020-05-19 17:38 Andreas Sturmlechner
2020-05-19 17:38 Andreas Sturmlechner
2020-05-19 17:38 Andreas Sturmlechner
2018-01-06 20:40 Ulrich Müller
2015-12-20 16:35 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=1647802261.388616e6c095680bbf3480bfd076a2c34ba67dd5.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