public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/bc/
Date: Fri,  2 Dec 2022 22:34:19 +0000 (UTC)	[thread overview]
Message-ID: <1670020447.5d625775a8d03535e7eea28b56eff54f7a63ebb5.sam@gentoo> (raw)

commit:     5d625775a8d03535e7eea28b56eff54f7a63ebb5
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Dec  2 22:33:12 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Dec  2 22:34:07 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5d625775

sys-devel/bc: explicitly set LEX=flex

We already BDEPEND on flex.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-devel/bc/bc-1.07.1-r6.ebuild | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sys-devel/bc/bc-1.07.1-r6.ebuild b/sys-devel/bc/bc-1.07.1-r6.ebuild
index 83e40a7d2488..175d05638d79 100644
--- a/sys-devel/bc/bc-1.07.1-r6.ebuild
+++ b/sys-devel/bc/bc-1.07.1-r6.ebuild
@@ -57,6 +57,10 @@ src_configure() {
 	# who knows when they'll make another release.
 	append-lfs-flags
 
+	# configure dies with other lexes:
+	# "configure: error: readline works only with flex."
+	export LEX=flex
+
 	econf "${myconf[@]}"
 
 	# Do not regen docs -- configure produces a small fragment that includes


             reply	other threads:[~2022-12-02 22:34 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 22:34 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27  2:42 [gentoo-commits] repo/gentoo:master commit in: sys-devel/bc/ Sam James
2025-02-23 14:21 Arthur Zamarin
2025-02-23 12:22 Jakov Smolić
2025-02-23 12:22 Jakov Smolić
2025-02-23  5:42 Sam James
2025-02-23  5:21 Sam James
2025-02-23  5:16 Sam James
2025-02-23  5:16 Sam James
2025-01-06  4:16 Sam James
2025-01-03  1:11 Sam James
2023-05-30 13:55 Fabian Groffen
2022-12-28  0:33 Sam James
2022-12-27 19:53 Sam James
2022-12-27 19:45 Sam James
2022-12-27 13:40 Sam James
2022-12-27 11:31 Sam James
2022-12-02 21:30 Sam James
2022-11-04  8:16 Agostino Sarubbo
2022-11-03 19:13 Sam James
2022-11-03 19:11 Arthur Zamarin
2022-09-09  8:23 Mike Frysinger
2022-09-09  8:23 Mike Frysinger
2022-07-28  6:40 Sam James
2022-06-19 18:50 David Seifert
2022-06-19 18:50 David Seifert
2021-04-21 19:02 Sam James
2021-02-26 16:11 Sam James
2021-01-06 15:32 Fabian Groffen
2020-12-27 18:18 Fabian Groffen
2020-08-23  8:10 Sergei Trofimovich
2020-08-19  8:31 Sergei Trofimovich
2020-08-17 12:03 Agostino Sarubbo
2020-08-17 10:01 Agostino Sarubbo
2020-08-17  9:59 Agostino Sarubbo
2020-08-17  9:58 Agostino Sarubbo
2020-08-17  9:57 Agostino Sarubbo
2020-01-17 16:02 Mike Gilbert
2019-05-05 11:04 Mikle Kolyada
2018-01-18 21:23 Mikle Kolyada
2018-01-18 21:20 Mikle Kolyada
2018-01-10  6:19 Markus Meier
2018-01-08 20:12 Sergei Trofimovich
2018-01-06 22:30 Sergei Trofimovich
2018-01-06 21:49 Sergei Trofimovich
2018-01-04 22:11 Sergei Trofimovich
2018-01-04 20:10 Lars Wendler
2018-01-04 13:00 Lars Wendler
2017-12-01 18:25 Fabian Groffen
2017-10-28 13:10 Thomas Deutschmann
2017-10-28 13:10 Thomas Deutschmann
2017-04-10  9:06 Lars Wendler
2017-04-10  7:58 Lars Wendler
2017-04-10  7:58 Lars Wendler
2017-04-10  7:58 Lars Wendler
2017-04-10  7:55 Lars Wendler
2017-03-21 15:46 Michael Haubenwallner
2015-12-31 17:07 Mike Frysinger

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=1670020447.5d625775a8d03535e7eea28b56eff54f7a63ebb5.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