From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-scheme/guile/, dev-scheme/guile/files/
Date: Fri, 1 Jan 2021 05:52:36 +0000 (UTC) [thread overview]
Message-ID: <1609480349.fb97c7de4b112b77e5205b7926bfaf1d38cc733d.sam@gentoo> (raw)
commit: fb97c7de4b112b77e5205b7926bfaf1d38cc733d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 1 05:52:29 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jan 1 05:52:29 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fb97c7de
dev-scheme/guile: fix build where stack grows upwards
Closes: https://bugs.gentoo.org/747049
Package-Manager: Portage-3.0.9, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-scheme/guile/files/guile-2.2.7-stack-up.patch | 17 +++++++++++++++++
dev-scheme/guile/guile-2.2.7.ebuild | 8 ++++++--
2 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/dev-scheme/guile/files/guile-2.2.7-stack-up.patch b/dev-scheme/guile/files/guile-2.2.7-stack-up.patch
new file mode 100644
index 00000000000..de291421c0b
--- /dev/null
+++ b/dev-scheme/guile/files/guile-2.2.7-stack-up.patch
@@ -0,0 +1,17 @@
+This patch (dropping an obsolete extra parameter to grow_stack) landed post
+2.2.7 and we're not likely to ever see a 2.2.8, as development has moved
+on to 3.x now.
+
+https://bugs.gentoo.org/747049
+https://www.mail-archive.com/guile-devel@gnu.org/msg15502.html
+--- a/libguile/continuations.c
++++ b/libguile/continuations.c
+@@ -302,7 +302,7 @@
+
+ #if SCM_STACK_GROWS_UP
+ if (dst + continuation->num_stack_items >= &stack_top_element)
+- grow_stack (cont, mra);
++ grow_stack (cont);
+ #else
+ dst -= continuation->num_stack_items;
+ if (dst <= &stack_top_element)
diff --git a/dev-scheme/guile/guile-2.2.7.ebuild b/dev-scheme/guile/guile-2.2.7.ebuild
index 61026da9a02..6020cc99568 100644
--- a/dev-scheme/guile/guile-2.2.7.ebuild
+++ b/dev-scheme/guile/guile-2.2.7.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -29,7 +29,11 @@ BDEPEND="
sys-devel/libtool
sys-devel/gettext"
-PATCHES=( "${FILESDIR}/${PN}-2.2.3-gentoo-sandbox.patch" )
+PATCHES=(
+ "${FILESDIR}/${PN}-2.2.3-gentoo-sandbox.patch"
+ "${FILESDIR}/${PN}-2.2.7-stack-up.patch"
+)
+
DOCS=( GUILE-VERSION HACKING README )
src_configure() {
next reply other threads:[~2021-01-01 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 5:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 2:56 [gentoo-commits] repo/gentoo:master commit in: dev-scheme/guile/, dev-scheme/guile/files/ Sam James
2024-06-08 8:55 Sam James
2023-07-03 17:51 Ulrich Müller
2023-01-04 4:32 Sam James
2022-03-15 19:25 Maciej Barć
2017-12-04 12:44 Amy Liffey
2017-11-27 12:47 Amy Liffey
2017-06-21 12:33 Fabian Groffen
2017-04-22 14:40 Amy Liffey
2016-09-21 18:11 Amy Winston
2016-08-12 19:11 Amy Winston
2016-08-07 19:10 Amy Winston
2016-06-27 16:09 Austin English
2015-10-12 23:24 Ryan Hill
2015-10-12 23:24 Ryan Hill
2015-10-12 23:24 Ryan Hill
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=1609480349.fb97c7de4b112b77e5205b7926bfaf1d38cc733d.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