From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/ffcall/
Date: Thu, 19 Mar 2020 22:34:35 +0000 (UTC) [thread overview]
Message-ID: <1584657271.b8d5a27733ec5a3841d2635a0aad64d88b2a973a.slyfox@gentoo> (raw)
commit: b8d5a27733ec5a3841d2635a0aad64d88b2a973a
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 19 22:34:22 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Mar 19 22:34:31 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b8d5a277
dev-libs/ffcall: use einfo, not elog in src_prepare()
Noticed the post-merge output from dev-libs/ffcall when
was installing gforth. The output did not look useful:
```
* Messages for package dev-libs/ffcall-2.1:
* Patching 'Makefile.in'
* Patching 'avcall/Makefile.in'
* Patching 'callback/Makefile.in'
* Patching 'gnulib-lib/Makefile.in'
* Patching 'trampoline/Makefile.in'
* Patching 'vacall/Makefile.in'
* Patching 'callback/trampoline_r/Makefile.in'
* Patching 'callback/vacall_r/Makefile.in'
* Patching 'Makefile.in'
```
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-libs/ffcall/ffcall-2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/ffcall/ffcall-2.1.ebuild b/dev-libs/ffcall/ffcall-2.1.ebuild
index 8a690e7e2c0..d627c694ee2 100644
--- a/dev-libs/ffcall/ffcall-2.1.ebuild
+++ b/dev-libs/ffcall/ffcall-2.1.ebuild
@@ -32,7 +32,7 @@ src_prepare() {
for mfi in {,*/,*/*/,}Makefile.in
do
- elog "Patching '${mfi}'"
+ einfo "Patching '${mfi}'"
# usually uses only assembler here, but -march=
# and -Wa, are a must to pass here.
sed -e 's/$(CC) /&$(CFLAGS) /g' \
next reply other threads:[~2020-03-19 22:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 22:34 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 6:06 [gentoo-commits] repo/gentoo:master commit in: dev-libs/ffcall/ Arthur Zamarin
2025-04-26 4:12 Sam James
2025-04-10 10:38 Sam James
2024-11-21 13:47 Jakov Smolić
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18 11:11 Sam James
2024-11-18 9:36 Sam James
2024-05-02 4:32 Sam James
2022-08-29 18:39 Andreas Sturmlechner
2022-06-23 19:50 Arthur Zamarin
2022-05-14 21:52 Jakov Smolić
2022-04-28 15:05 Jakov Smolić
2022-03-10 10:10 Jakov Smolić
2022-03-10 9:13 Agostino Sarubbo
2022-03-10 9:13 Agostino Sarubbo
2022-03-10 9:12 Agostino Sarubbo
2022-03-10 9:03 Jakov Smolić
2022-02-17 11:00 Jakov Smolić
2021-11-19 8:34 Sam James
2018-05-28 9:13 José María Alonso
2018-05-26 9:28 Mikle Kolyada
2018-05-14 21:19 Tobias Klausmann
2018-05-14 0:16 Aaron Bauman
2018-05-13 22:06 Thomas Deutschmann
2018-05-11 19:21 Sergei Trofimovich
2018-05-10 22:43 Sergei Trofimovich
2018-04-10 16:40 José María Alonso
2017-12-16 16:36 José María Alonso
2017-12-16 16:32 José María Alonso
2017-12-16 16:25 José María Alonso
2017-12-16 10:31 Tobias Klausmann
2017-10-26 20:30 Thomas Deutschmann
2017-10-22 21:42 Tobias Klausmann
2017-10-19 20:55 Sergei Trofimovich
2017-10-18 21:28 Sergei Trofimovich
2017-10-18 21:21 Sergei Trofimovich
2017-09-14 15:41 José María Alonso
2017-07-14 7:45 Sergei Trofimovich
2017-07-02 17:05 Alexis Ballier
2017-06-30 7:32 José María Alonso
2017-06-27 10:03 José María Alonso
2017-06-12 8:58 Michael Palimaka
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=1584657271.b8d5a27733ec5a3841d2635a0aad64d88b2a973a.slyfox@gentoo \
--to=slyfox@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