From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/slibtool/
Date: Sun, 7 May 2023 06:10:24 +0000 (UTC) [thread overview]
Message-ID: <1683439813.4ac26fb671f24d49b20930f9acfb875933b0fa14.sam@gentoo> (raw)
commit: 4ac26fb671f24d49b20930f9acfb875933b0fa14
Author: orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Sun May 7 06:04:23 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 7 06:10:13 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4ac26fb6
sys-devel/slibtool: remove shell workaround
slibtool now uses CONFIG_SHELL like autoconf instead of accepting the
SHELL variable which may not be a bourne compatible shell.
Bug: https://bugs.gentoo.org/905721
Upstream-Commit: https://git.foss21.org/slibtool/commit/?id=667d348ca9d54b31857fd20c08b97c642ae9f815
Signed-off-by: orbea <orbea <AT> riseup.net>
Closes: https://github.com/gentoo/gentoo/pull/30908
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/slibtool/slibtool-9999.ebuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/sys-devel/slibtool/slibtool-9999.ebuild b/sys-devel/slibtool/slibtool-9999.ebuild
index 5295be737954..74b39d4339b5 100644
--- a/sys-devel/slibtool/slibtool-9999.ebuild
+++ b/sys-devel/slibtool/slibtool-9999.ebuild
@@ -33,6 +33,5 @@ src_configure() {
--host=${CHOST} \
--prefix="${EPREFIX}"/usr \
--libdir="${EPREFIX}/usr/$(get_libdir)" \
- --shell="${EPREFIX}"/bin/sh \
|| die
}
next reply other threads:[~2023-05-07 6:10 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 6:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-03 2:20 [gentoo-commits] repo/gentoo:master commit in: sys-devel/slibtool/ Ionen Wolkens
2023-12-22 7:16 Joonas Niilola
2023-12-22 7:16 Joonas Niilola
2023-12-22 5:07 Sam James
2023-12-21 16:01 Arthur Zamarin
2023-12-21 15:15 Sam James
2023-12-21 12:56 Sam James
2023-12-21 11:55 Sam James
2023-12-21 11:12 Arthur Zamarin
2023-11-17 12:32 Sam James
2023-11-17 12:32 Sam James
2023-06-17 17:15 Arthur Zamarin
2023-06-17 13:17 Joonas Niilola
2023-06-17 10:42 Arthur Zamarin
2023-06-17 8:29 Arthur Zamarin
2023-06-17 8:29 Arthur Zamarin
2023-06-17 5:42 Sam James
2023-05-05 4:44 Sam James
2022-05-07 18:24 Sam James
2022-03-20 0:26 Sam James
2022-01-01 9:38 Sam James
2021-09-21 12:40 James Le Cuirot
2021-09-07 15:36 Lars Wendler
2021-09-06 18:01 Sam James
2021-07-31 22:49 Joshua Kinard
2021-07-31 13:40 Michał Górny
2021-07-25 3:36 Matt Turner
2021-06-25 17:24 Marek Szuba
2021-05-12 7:01 Lars Wendler
2021-05-12 6:21 Lars Wendler
2021-04-26 15:37 Sam James
2021-04-25 5:19 Sam James
2021-04-05 20:49 Sam James
2021-04-05 20:49 Sam James
2021-04-05 20:49 Sam James
2021-04-01 12:19 Thomas Deutschmann
2021-03-28 15:41 Sam James
2021-03-27 19:17 Sergei Trofimovich
2021-03-27 19:17 Sergei Trofimovich
2021-03-27 19:17 Sergei Trofimovich
2021-03-25 19:08 Sam James
2021-03-22 17:53 Lars Wendler
2021-03-22 15:19 Lars Wendler
2021-03-22 15:19 Lars Wendler
2021-03-22 9:23 Sam James
2021-03-22 9:23 Sam James
2021-03-22 9:23 Sam James
2021-03-21 15:35 Sergei Trofimovich
2021-03-21 9:45 Sergei Trofimovich
2021-01-17 1:28 Lars Wendler
2020-12-01 7:56 Joonas Niilola
2019-01-17 22:55 Patrice Clement
2019-01-17 22:55 Patrice Clement
2018-08-01 21:40 Patrice Clement
2018-05-26 17:07 Aaron Bauman
2018-05-20 0:16 Aaron Bauman
2017-09-06 12:06 Michał Górny
2017-09-06 12:06 Michał Górny
2017-07-30 14:13 David Seifert
2017-07-30 14:13 David Seifert
2016-12-04 22:32 Patrice Clement
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=1683439813.4ac26fb671f24d49b20930f9acfb875933b0fa14.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