From: Greg Troxel <gdt@lexort.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: <guile-devel@gnu.org>
Subject: Re: GNU Guile 3.0.9rc1 available for testing!
Date: Sun, 22 Jan 2023 12:41:09 -0500 [thread overview]
Message-ID: <rmih6wicvre.fsf@s1.lexort.com> (raw)
In-Reply-To: rmiy1pv48rj.fsf@s1.lexort.com
My second approach is using the rc tarball in pkgsrc. I had to patch
out the verify call. pkgsrc already works around PaX issues mostly, via
paxctl on things that do jit, after build and before use, and by
--- libguile/loader.c.orig 2018-01-08 16:21:04.790894906 +0000
+++ libguile/loader.c
@@ -484,7 +484,7 @@ map_file_contents (int fd, size_t len, i
char *data;
#ifdef HAVE_SYS_MMAN_H
- data = mmap (NULL, len, PROT_READ, MAP_PRIVATE, fd, 0);
+ data = mmap (NULL, len, PROT_READ | PROT_WRITE, MAP_PRIVATE, fd, 0);
if (data == MAP_FAILED)
SCM_SYSERROR;
*is_read_only = 1;
because (something like, am fuzzy) mprotect (at least ours) can only
reduce not add permissions. I still don't understand why this isn't a
more widespread issue.
With the rc tarball, the build almost works, and now stops at:
Making all in guile-readline
gmake[2]: Entering directory '/tmp/work/lang/guile30/work/guile-3.0.9rc1/guile-readline'
/usr/pkg/bin/gmake all-am
gmake[3]: Entering directory '/tmp/work/lang/guile30/work/guile-3.0.9rc1/guile-readline'
gmake[3]: *** No rule to make target 'ice-9/readline.scm', needed by 'ice-9/readline.go'. Stop.
gmake[3]: Leaving directory '/tmp/work/lang/guile30/work/guile-3.0.9rc1/guile-readline'
gmake[2]: *** [Makefile:1984: all] Error 2
gmake[2]: Leaving directory '/tmp/work/lang/guile30/work/guile-3.0.9rc1/guile-readline'
gmake[1]: *** [Makefile:2152: all-recursive] Error 1
gmake[1]: Leaving directory '/tmp/work/lang/guile30/work/guile-3.0.9rc1'
gmake: *** [Makefile:2038: all] Error 2
*** Error code 2
with or without -j2. I see ice-9/readline.scm in git but not in the
rc tarball.
next prev parent reply other threads:[~2023-01-22 17:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:58 GNU Guile 3.0.9rc1 available for testing! Ludovic Courtès
2023-01-20 16:18 ` Thompson, David
2023-01-21 14:58 ` Jan Nieuwenhuizen
2023-01-23 10:42 ` Ludovic Courtès
2023-01-23 13:23 ` Janneke Nieuwenhuizen
2023-01-20 17:50 ` Aleix Conchillo Flaqué
2023-01-23 10:45 ` Ludovic Courtès
2023-01-23 17:01 ` Aleix Conchillo Flaqué
2023-01-22 2:12 ` Greg Troxel
2023-01-22 14:30 ` lloda
2023-01-22 14:39 ` Greg Troxel
2023-01-23 10:48 ` Ludovic Courtès
2023-01-23 18:04 ` lloda
2023-01-23 21:59 ` bug#60971: build failure of v3.0.9rc1 on mac os 12.6 Ludovic Courtès
2023-01-23 18:47 ` GNU Guile 3.0.9rc1 available for testing! Aleix Conchillo Flaqué
2023-01-25 1:44 ` Greg Troxel
2023-01-25 10:32 ` Ludovic Courtès
2023-01-22 17:41 ` Greg Troxel [this message]
2023-01-22 23:10 ` Greg Troxel
2023-01-23 11:02 ` Ludovic Courtès
2023-01-23 11:19 ` Ludovic Courtès
2023-01-24 15:43 ` Greg Troxel
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmih6wicvre.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).