From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/m4/
Date: Tue, 26 Apr 2022 09:47:23 +0000 (UTC) [thread overview]
Message-ID: <1650966283.5dcddbb5214cd29e6217edb4002be36df4d60c66.xen0n@gentoo> (raw)
commit: 5dcddbb5214cd29e6217edb4002be36df4d60c66
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 26 09:40:10 2022 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Tue Apr 26 09:44:43 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5dcddbb5
sys-devel/m4: fix incomplete deactivation of maintainer mode
Commit 4abfea67ec7 ("sys-devel/m4: avoid invoking autoconf") did an
incomplete job of deactivating the refresh of various files after
patching the m4 and configure part of sources; turns out dependency on
makeinfo should be avoided as well.
Tested with sys-apps/texinfo unmerged.
Fixes: 43dd58338de ("sys-devel/m4: fix build on loong")
Closes: https://bugs.gentoo.org/840984
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
sys-devel/m4/m4-1.4.19.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-devel/m4/m4-1.4.19.ebuild b/sys-devel/m4/m4-1.4.19.ebuild
index e3ceb0429850..2830a3894678 100644
--- a/sys-devel/m4/m4-1.4.19.ebuild
+++ b/sys-devel/m4/m4-1.4.19.ebuild
@@ -57,7 +57,7 @@ src_prepare() {
# touch generated files after patching m4, to avoid activating maintainer
# mode
# remove when loong-fix-build.patch is no longer necessary
- touch ./aclocal.m4 ./lib/config.hin ./configure || die
+ touch ./aclocal.m4 ./lib/config.hin ./configure ./doc/stamp-vti || die
find . -name Makefile.in -exec touch {} + || die
}
next reply other threads:[~2022-04-26 9:47 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 9:47 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-19 20:29 [gentoo-commits] repo/gentoo:master commit in: sys-devel/m4/ Sam James
2025-04-14 0:42 Sam James
2024-12-06 13:04 Sam James
2024-11-16 21:48 Sam James
2024-11-11 20:30 Sam James
2023-05-22 16:26 David Seifert
2023-05-22 16:26 David Seifert
2023-03-04 22:30 Jakov Smolić
2023-03-04 13:45 Arthur Zamarin
2023-03-04 9:10 Arthur Zamarin
2023-03-04 8:44 Arthur Zamarin
2023-03-04 7:28 Arthur Zamarin
2023-03-04 7:25 Arthur Zamarin
2023-03-04 7:17 Arthur Zamarin
2023-03-04 6:05 Arthur Zamarin
2022-10-18 2:18 Sam James
2022-04-07 3:57 Sam James
2022-02-10 20:48 Mike Gilbert
2022-02-10 14:46 Sam James
2022-02-07 0:30 Sam James
2021-08-15 19:51 Sam James
2021-08-12 6:41 Agostino Sarubbo
2021-08-11 19:11 Sam James
2021-08-11 6:41 Agostino Sarubbo
2021-08-11 6:40 Agostino Sarubbo
2021-08-11 0:20 Sam James
2021-05-30 11:00 Lars Wendler
2021-05-12 7:28 Lars Wendler
2021-05-10 8:24 Lars Wendler
2021-03-26 17:58 Lars Wendler
2021-03-26 17:58 Lars Wendler
2021-01-06 15:32 Fabian Groffen
2020-12-27 18:18 Fabian Groffen
2020-09-13 22:30 Mike Gilbert
2020-09-13 9:57 Fabian Groffen
2019-05-04 17:28 Mikle Kolyada
2019-03-10 8:36 Mart Raudsepp
2019-03-02 15:46 Mikle Kolyada
2019-03-02 15:46 Mikle Kolyada
2019-03-02 15:46 Mikle Kolyada
2019-03-02 15:46 Mikle Kolyada
2019-03-02 15:46 Mikle Kolyada
2019-03-01 1:14 Thomas Deutschmann
2019-02-28 7:23 Sergei Trofimovich
2019-02-27 8:20 Sergei Trofimovich
2019-02-27 8:20 Sergei Trofimovich
2019-02-27 7:55 Sergei Trofimovich
2019-02-26 4:59 Jack Morgan
2019-02-25 15:19 Mikle Kolyada
2019-02-25 10:55 Mikle Kolyada
2019-02-25 10:55 Mikle Kolyada
2017-02-20 14:11 Michael Haubenwallner
2017-01-29 20:14 Fabian Groffen
2017-01-19 14:14 Mike Frysinger
2017-01-01 1:50 Anthony G. Basile
2016-12-31 23:45 Lars Wendler
2016-06-04 4:54 Markus Meier
2016-05-27 12:46 Lars Wendler
2016-05-26 20:05 Lars Wendler
2016-05-25 9:19 Anthony G. Basile
2016-05-25 6:29 Matt Turner
2016-05-25 5:25 Jeroen Roovers
2016-04-25 22:57 Anthony G. Basile
2016-04-21 6:27 Anthony G. Basile
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=1650966283.5dcddbb5214cd29e6217edb4002be36df4d60c66.xen0n@gentoo \
--to=xen0n@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