From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/lpe/
Date: Fri, 2 Apr 2021 13:59:37 +0000 (UTC) [thread overview]
Message-ID: <1617371967.5ea6be86d6e62ea1e0e0fd25ab1afe8f2bb3646f.sam@gentoo> (raw)
commit: 5ea6be86d6e62ea1e0e0fd25ab1afe8f2bb3646f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 2 13:51:40 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 2 13:59:27 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5ea6be86
app-editors/lpe: fix ncurses discovery
I originally tested on a macOS Prefix which
apparently has non-split tinfo.
Closes: https://bugs.gentoo.org/779778
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-editors/lpe/lpe-1.2.8_p20210401.ebuild | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/app-editors/lpe/lpe-1.2.8_p20210401.ebuild b/app-editors/lpe/lpe-1.2.8_p20210401.ebuild
index 549d8c087e3..4cf5b201a5b 100644
--- a/app-editors/lpe/lpe-1.2.8_p20210401.ebuild
+++ b/app-editors/lpe/lpe-1.2.8_p20210401.ebuild
@@ -37,7 +37,13 @@ src_prepare() {
# That is, if you need eautoreconf
sed -i \
-e "s:-lncurses:$($(tc-getPKG_CONFIG) --libs-only-l ncurses):" \
- src/Makefile.in || die
+ configure.ac || die
+
+ # Actually use what configure discovers (above)
+ # bug #779778
+ sed -i \
+ -e 's:-lncurses:@NCURSES_LIB@:' \
+ src/Makefile.am || die
# Refresh outdated libtool (elibtoolize insufficient)
# Fixes undefined references on macOS/Darwin
next reply other threads:[~2021-04-02 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 13:59 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-29 13:31 [gentoo-commits] repo/gentoo:master commit in: app-editors/lpe/ Yixun Lan
2021-05-06 7:22 Sergei Trofimovich
2021-05-04 21:27 Sam James
2021-05-04 21:26 Sam James
2021-04-02 13:59 Sam James
2021-04-01 22:08 Sam James
2017-12-10 14:16 David Seifert
2017-06-12 11:06 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=1617371967.5ea6be86d6e62ea1e0e0fd25ab1afe8f2bb3646f.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