From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/
Date: Sat, 26 Mar 2022 00:09:06 +0000 (UTC) [thread overview]
Message-ID: <1648253277.7421ae946ca9d19a417d2fcf3e48b4de8f80202b.sam@gentoo> (raw)
commit: 7421ae946ca9d19a417d2fcf3e48b4de8f80202b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 26 00:07:46 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 26 00:07:57 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7421ae94
dev-libs/libaio: fix tc-getCPP
Fixes: b7d492ff93212de55b9844dc6aabcef5493c69d5
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/libaio/libaio-0.3.112.ebuild | 2 +-
dev-libs/libaio/libaio-9999.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-libs/libaio/libaio-0.3.112.ebuild b/dev-libs/libaio/libaio-0.3.112.ebuild
index 8c82444565a2..dd90b717f5d9 100644
--- a/dev-libs/libaio/libaio-0.3.112.ebuild
+++ b/dev-libs/libaio/libaio-0.3.112.ebuild
@@ -46,7 +46,7 @@ multilib_src_configure() {
if use arm ; then
# When building for thumb, we can't allow frame pointers.
# http://crbug.com/464517
- if "$(tc-getCPP)" ${CFLAGS} ${CPPFLAGS} - <<<$'#ifndef __thumb__\n#error\n#endif' >&/dev/null ; then
+ if $(tc-getCPP) ${CFLAGS} ${CPPFLAGS} - <<<$'#ifndef __thumb__\n#error\n#endif' >&/dev/null ; then
append-flags -fomit-frame-pointer
fi
fi
diff --git a/dev-libs/libaio/libaio-9999.ebuild b/dev-libs/libaio/libaio-9999.ebuild
index 87ca662c92c6..cd86a0c918f6 100644
--- a/dev-libs/libaio/libaio-9999.ebuild
+++ b/dev-libs/libaio/libaio-9999.ebuild
@@ -46,7 +46,7 @@ multilib_src_configure() {
if use arm ; then
# When building for thumb, we can't allow frame pointers.
# http://crbug.com/464517
- if "$(tc-getCPP)" ${CFLAGS} ${CPPFLAGS} - <<<$'#ifndef __thumb__\n#error\n#endif' >&/dev/null ; then
+ if $(tc-getCPP) ${CFLAGS} ${CPPFLAGS} - <<<$'#ifndef __thumb__\n#error\n#endif' >&/dev/null ; then
append-flags -fomit-frame-pointer
fi
fi
next reply other threads:[~2022-03-26 0:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 0:09 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-13 21:30 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/ Sam James
2024-04-12 6:26 Arthur Zamarin
2024-04-12 6:26 Arthur Zamarin
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-02-20 5:14 Sam James
2022-10-15 3:11 Sam James
2022-09-27 7:10 Agostino Sarubbo
2022-09-26 6:37 Arthur Zamarin
2022-09-26 6:24 Arthur Zamarin
2022-09-26 6:24 Arthur Zamarin
2022-09-25 7:28 Arthur Zamarin
2022-09-25 6:19 Agostino Sarubbo
2022-09-25 4:43 Sam James
2022-09-25 4:37 Sam James
2022-08-24 7:04 Sam James
2022-05-06 2:44 WANG Xuerui
2022-05-02 2:09 Sam James
2022-04-21 20:25 Sam James
2022-03-26 0:01 Sam James
2020-09-07 0:53 Sam James
2020-08-29 14:48 Thomas Deutschmann
2020-08-28 22:21 Sergei Trofimovich
2020-08-24 17:33 Sergei Trofimovich
2020-08-23 6:51 Sam James
2020-08-22 5:43 Agostino Sarubbo
2020-08-21 18:20 Agostino Sarubbo
2019-06-04 0:07 Thomas Deutschmann
2019-05-05 20:09 Mikle Kolyada
2019-04-24 22:54 Thomas Deutschmann
2019-04-24 22:39 Göktürk Yüksek
2017-02-23 2:30 Göktürk Yüksek
2016-05-22 17:09 Göktürk Yüksek
2016-04-23 18:13 Patrice Clement
2016-04-23 7:59 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=1648253277.7421ae946ca9d19a417d2fcf3e48b4de8f80202b.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