From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/mpc/
Date: Tue, 26 Dec 2017 17:24:55 +0000 (UTC) [thread overview]
Message-ID: <1514309091.0c689de38bcc3b4279aa9e3b09c836e48a237e3d.slyfox@gentoo> (raw)
commit: 0c689de38bcc3b4279aa9e3b09c836e48a237e3d
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 26 17:24:28 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Dec 26 17:24:51 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0c689de3
dev-libs/mpc: explicitly regenerate ./configure, noticed by Anarchy
Package-Manager: Portage-2.3.19, Repoman-2.3.6
dev-libs/mpc/mpc-1.0.3.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dev-libs/mpc/mpc-1.0.3.ebuild b/dev-libs/mpc/mpc-1.0.3.ebuild
index ac5e3396ddd..66845b9d3d0 100644
--- a/dev-libs/mpc/mpc-1.0.3.ebuild
+++ b/dev-libs/mpc/mpc-1.0.3.ebuild
@@ -3,7 +3,7 @@
EAPI="4"
-inherit eutils libtool multilib-minimal
+inherit autotools eutils libtool multilib-minimal
DESCRIPTION="A library for multiprecision complex arithmetic with exact rounding"
HOMEPAGE="http://mpc.multiprecision.org/"
@@ -20,6 +20,7 @@ RDEPEND="${DEPEND}"
src_prepare() {
epatch "${FILESDIR}"/${P}-mpfr-4.0.0.patch
+ eautoreconf
elibtoolize #347317
}
next reply other threads:[~2017-12-26 17:25 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 17:24 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 8:27 [gentoo-commits] repo/gentoo:master commit in: dev-libs/mpc/ Sam James
2023-08-01 7:09 Sam James
2023-08-01 7:09 Sam James
2023-01-28 19:07 Arthur Zamarin
2023-01-27 6:28 Sam James
2023-01-27 6:27 Sam James
2023-01-27 6:27 Sam James
2023-01-27 6:27 Sam James
2023-01-27 6:23 Sam James
2023-01-27 6:23 Sam James
2023-01-27 6:21 Sam James
2022-12-16 22:39 Sam James
2022-12-15 19:55 Sam James
2022-12-13 23:00 Sam James
2022-12-12 17:54 Sam James
2022-12-10 2:58 Sam James
2022-12-09 21:27 Sam James
2022-12-03 8:10 Sam James
2022-04-09 2:35 Sam James
2021-01-06 19:34 Fabian Groffen
2020-12-27 14:21 Fabian Groffen
2020-12-04 19:34 Sergei Trofimovich
2020-12-02 22:39 Sam James
2020-11-27 16:10 Agostino Sarubbo
2020-11-27 16:08 Agostino Sarubbo
2020-11-27 16:04 Agostino Sarubbo
2020-11-27 8:42 Agostino Sarubbo
2020-11-27 7:55 Agostino Sarubbo
2020-11-26 16:38 Thomas Deutschmann
2020-11-26 11:31 Sam James
2020-11-26 11:31 Sam James
2020-10-25 9:28 Sergei Trofimovich
2020-09-24 22:50 Sergei Trofimovich
2020-09-23 10:31 Agostino Sarubbo
2020-09-23 10:29 Agostino Sarubbo
2020-09-23 10:24 Agostino Sarubbo
2020-09-21 18:53 Sergei Trofimovich
2020-09-20 16:44 Thomas Deutschmann
2020-09-19 21:11 Sam James
2020-09-19 20:23 Sam James
2020-09-19 20:13 Mikle Kolyada
2020-08-19 18:14 Sergei Trofimovich
2020-02-25 12:46 Mikle Kolyada
2020-02-25 12:46 Mikle Kolyada
2019-11-13 16:09 Agostino Sarubbo
2019-11-12 19:42 Matt Turner
2019-11-12 18:07 Agostino Sarubbo
2019-11-12 10:38 Agostino Sarubbo
2019-11-11 0:26 Matt Turner
2019-11-10 21:56 Sergei Trofimovich
2019-11-09 15:54 Aaron Bauman
2019-11-08 8:35 Mikle Kolyada
2019-11-03 14:49 Agostino Sarubbo
2019-11-03 13:39 Mikle Kolyada
2019-11-03 13:03 Agostino Sarubbo
2019-05-04 18:38 Andreas K. Hüttel
2019-03-15 7:58 Sergei Trofimovich
2018-06-24 12:10 Matthias Maier
2018-06-24 12:10 Matthias Maier
2018-06-24 12:10 Matthias Maier
2018-01-14 21:27 Sergei Trofimovich
2018-01-12 15:13 Anthony G. Basile
2018-01-12 4:10 Mike Frysinger
2018-01-10 4:31 Mike Frysinger
2018-01-02 22:54 Sergei Trofimovich
2017-12-26 20:59 Sergei Trofimovich
2017-11-27 7:27 Sergei Trofimovich
2017-11-27 0:20 Thomas Deutschmann
2017-11-26 19:06 Sergei Trofimovich
2017-11-26 1:30 Matt Turner
2017-11-25 20:02 Matt Turner
2017-11-25 12:10 Sergei Trofimovich
2017-01-29 16:19 Fabian Groffen
2016-02-29 8:46 Stephen Klimaszewski
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=1514309091.0c689de38bcc3b4279aa9e3b09c836e48a237e3d.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