public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/pari/
Date: Sun, 14 Jan 2018 13:49:43 +0000 (UTC)	[thread overview]
Message-ID: <1515937772.d6b594521223c317128fe54f652461fe2e0717ba.asturm@gentoo> (raw)

commit:     d6b594521223c317128fe54f652461fe2e0717ba
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 14 13:49:10 2018 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sun Jan 14 13:49:32 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d6b59452

sci-mathematics/pari: Fix typo

Thanks-to: Felix Janda <felix.janda <AT> posteo.de>
Bug: https://bugs.gentoo.org/641942
Package-Manager: Portage-2.3.19, Repoman-2.3.6

 sci-mathematics/pari/pari-2.9.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sci-mathematics/pari/pari-2.9.4.ebuild b/sci-mathematics/pari/pari-2.9.4.ebuild
index 6e3bf66bb96..37593bb6748 100644
--- a/sci-mathematics/pari/pari-2.9.4.ebuild
+++ b/sci-mathematics/pari/pari-2.9.4.ebuild
@@ -77,7 +77,7 @@ src_configure() {
 		--with-ncurses-lib="${EPREFIX}"/usr/$(get_libdir) \
 		$(use_with fltk) \
 		$(use_with gmp) \
-		--without-qt4 \
+		--without-qt \
 		|| die "./Configure failed"
 }
 


             reply	other threads:[~2018-01-14 13:49 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 13:49 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-01 11:35 [gentoo-commits] repo/gentoo:master commit in: sci-mathematics/pari/ Arthur Zamarin
2025-02-01 11:35 Arthur Zamarin
2025-01-12  1:47 Michael Orlitzky
2024-08-19 12:47 Michael Orlitzky
2024-07-14 20:17 Jakov Smolić
2024-07-14 18:57 Arthur Zamarin
2024-03-12 18:40 Michael Orlitzky
2023-11-22 22:06 Michael Orlitzky
2023-10-31  6:05 Sam James
2023-10-31  2:35 Sam James
2023-08-02 10:46 Michael Orlitzky
2023-07-27  3:37 Michael Orlitzky
2023-06-05  5:15 Sam James
2023-06-05  5:02 Sam James
2023-06-05  3:51 Sam James
2023-06-03 11:15 Arthur Zamarin
2023-01-22  1:17 Michael Orlitzky
2023-01-22  1:17 Michael Orlitzky
2022-11-24  1:04 Michael Orlitzky
2022-09-21  1:00 Michael Orlitzky
2022-09-20 22:55 Michael Orlitzky
2022-09-20 22:55 Michael Orlitzky
2022-08-10  8:04 Arthur Zamarin
2022-08-10  8:04 Arthur Zamarin
2022-08-09  6:19 Joonas Niilola
2022-08-08 13:11 Michael Orlitzky
2022-08-08 12:34 Agostino Sarubbo
2022-06-07 14:43 Michael Orlitzky
2022-06-03 10:59 Michael Orlitzky
2022-06-02  0:36 Sam James
2022-06-02  0:36 Sam James
2022-06-02  0:36 Sam James
2022-06-02  0:36 Sam James
2022-04-07  2:27 Michael Orlitzky
2022-01-20 14:19 Michael Orlitzky
2022-01-19 22:43 Sam James
2022-01-19 22:43 Sam James
2022-01-18 21:50 Jakov Smolić
2022-01-18 21:50 Jakov Smolić
2021-11-11  0:46 Michael Orlitzky
2021-11-10 23:53 Michael Orlitzky
2021-11-10  4:15 Sam James
2021-11-05 17:38 Sam James
2021-11-03 20:28 Sam James
2021-11-03 20:28 Sam James
2021-09-22 15:02 Michael Orlitzky
2021-09-22 15:02 Michael Orlitzky
2021-04-29 14:45 Andrey Grozin
2020-10-20 20:48 Michael Orlitzky
2020-07-23  7:03 Kent Fredric
2020-06-29  1:26 Michael Orlitzky
2020-06-28 20:44 Agostino Sarubbo
2020-06-28 20:37 Agostino Sarubbo
2020-06-28 20:33 Agostino Sarubbo
2020-06-28 20:27 Agostino Sarubbo
2020-06-28 11:46 Michael Orlitzky
2020-06-26 20:21 Thomas Deutschmann
2020-04-28 12:44 Michael Orlitzky
2020-04-26 10:38 Joonas Niilola
2020-04-26  8:40 Joonas Niilola
2020-04-26  8:40 Joonas Niilola
2020-02-24 12:50 Agostino Sarubbo
2020-02-24 11:43 Agostino Sarubbo
2020-02-21 15:57 Agostino Sarubbo
2018-04-20  8:02 David Seifert
2018-01-14  9:43 Andreas Sturmlechner
2018-01-14  9:43 Andreas Sturmlechner
2016-05-14 23:32 David Seifert
2016-03-10 17:53 Markus Meier

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=1515937772.d6b594521223c317128fe54f652461fe2e0717ba.asturm@gentoo \
    --to=asturm@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