From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/beep/
Date: Mon, 18 Sep 2023 09:01:51 +0000 (UTC) [thread overview]
Message-ID: <1695027560.bec0e5ce38d99d789194d7b14aadf9d0e074caca.sam@gentoo> (raw)
commit: bec0e5ce38d99d789194d7b14aadf9d0e074caca
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 18 08:59:10 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Sep 18 08:59:20 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bec0e5ce
app-misc/beep: respect CC/*FLAGS
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-misc/beep/beep-1.4.12.ebuild | 33 +++++++++++----------------------
1 file changed, 11 insertions(+), 22 deletions(-)
diff --git a/app-misc/beep/beep-1.4.12.ebuild b/app-misc/beep/beep-1.4.12.ebuild
index 921d9410df5d..b05797a15faf 100644
--- a/app-misc/beep/beep-1.4.12.ebuild
+++ b/app-misc/beep/beep-1.4.12.ebuild
@@ -19,28 +19,17 @@ RESTRICT="test"
src_prepare() {
default
- sed -i -e "s#-D_FORTIFY_SOURCE=2##g;" GNUmakefile || die
-}
-
-src_compile() {
- emake \
- COMPILERS=gcc \
- COMPILER_gcc="$(tc-getCC)" \
- LINKER_gcc="$(tc-getCC)" \
- CFLAGS_gcc="${CFLAGS}" \
- LDFLAGS="${LDFLAGS}" \
- CPPFLAGS_gcc="" \
- all
-}
-
-src_test() {
- emake \
- COMPILERS=gcc \
- COMPILER_gcc="$(tc-getCC)" \
- LINKER_gcc="$(tc-getCC)" \
- CFLAGS_gcc="${CFLAGS}" \
- LDFLAGS="${LDFLAGS}" \
- check
+ cat <<-EOF > local.mk || die
+ CC=$(tc-getCC)
+ CFLAGS=${CFLAGS}
+ CPPFLAGS=${CPPFLAGS}
+ LDFLAGS=${LDFLAGS}
+ EOF
+
+ sed -i \
+ -e "s#-D_FORTIFY_SOURCE=2##g;" \
+ -e '/\-Werror)/d' \
+ GNUmakefile || die
}
src_install() {
next reply other threads:[~2023-09-18 9:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 9:01 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 16:17 [gentoo-commits] repo/gentoo:master commit in: app-misc/beep/ Arthur Zamarin
2023-10-20 20:18 Arthur Zamarin
2023-10-19 15:41 Sam James
2023-10-19 15:41 Sam James
2023-10-19 15:41 Sam James
2023-10-19 15:03 Sam James
2023-09-18 9:01 Sam James
2022-12-23 1:34 Sam James
2022-12-23 1:34 Sam James
2021-12-06 15:23 Sam James
2021-12-06 11:31 Agostino Sarubbo
2021-12-05 20:36 Arthur Zamarin
2021-12-05 18:39 Sam James
2021-12-05 5:18 Sam James
2021-09-23 8:20 Michał Górny
2020-06-23 7:28 Patrice Clement
2020-06-22 18:23 Sergei Trofimovich
2020-03-30 13:36 Agostino Sarubbo
2020-03-26 12:04 Agostino Sarubbo
2020-03-26 12:03 Agostino Sarubbo
2020-03-26 10:20 Agostino Sarubbo
2020-03-26 10:17 Agostino Sarubbo
2020-03-25 17:31 Thomas Deutschmann
2019-04-29 21:06 Aaron Bauman
2019-04-27 23:03 Aaron Bauman
2018-05-30 14:10 Aaron Bauman
2018-05-25 4:18 Matt Turner
2018-05-25 4:18 Matt Turner
2018-04-14 11:40 Markus Meier
2018-04-05 21:07 Sergei Trofimovich
2018-04-05 16:10 Tobias Klausmann
2018-04-05 13:43 Thomas Deutschmann
2018-04-05 3:29 Aaron Bauman
2017-08-03 22:41 Patrice Clement
2017-08-03 22:41 Patrice Clement
2016-05-20 20:31 Patrice Clement
2016-04-18 21:23 Patrice Clement
2016-02-01 9:36 Tobias Klausmann
2015-11-26 19:14 Markus Meier
2015-09-25 14:29 Agostino Sarubbo
2015-09-24 22:56 Patrice Clement
2015-08-28 21:37 Patrice Clement
2015-08-28 21:37 Patrice Clement
2015-08-28 21:37 Patrice Clement
2015-08-28 13:08 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=1695027560.bec0e5ce38d99d789194d7b14aadf9d0e074caca.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