From: FX <fxcoudert@gmail.com>
To: 44505@debbugs.gnu.org
Subject: bug#44505: Guile 3.0.4 build fails on macOS Big Sur / ARM
Date: Sat, 7 Nov 2020 17:27:04 +0100 [thread overview]
Message-ID: <1DEC0AB9-23F4-4DD7-90D8-A74DF3B57170@gmail.com> (raw)
Compilation of Guile 3.0.4 on arm64-apple-darwin20 (macOS Big Sur with ARM hardware) fails with:
GEN guile-procedures.texi
allocating JIT code buffer failed: Permission denied
jit.c:5687: fatal: assertion failed
/bin/sh: line 1: 65000 Broken pipe: 13 cat alist.doc array-handle.doc array-map.doc arrays.doc async.doc atomic.doc backtrace.doc boolean.doc bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc exceptions.doc expand.doc extensions.doc fdes-finalizers.doc feature.doc filesys.doc fluids.doc foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc generalized-arrays.doc generalized-vectors.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc list.doc load.doc macros.doc mallocs.doc memoize.doc modules.doc numbers.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc promises.doc r6rs-ports.doc random.doc rdelim.doc read.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc srfi-60.doc stackchk.doc stacks.doc stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc syntax.doc threads.doc throw.doc trees.doc unicode.doc uniform.doc values.doc variable.doc vectors.doc version.doc vports.doc weak-set.doc weak-table.doc weak-vector.doc dynl.doc posix.doc net_db.doc socket.doc regex-posix.doc
65001 Abort trap: 6 | GUILE_AUTO_COMPILE=0 ../meta/build-env guild snarf-check-and-output-texi > guile-procedures.texi
The backtrace for this issue is:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00000001932bfcec __pthread_kill + 8
1 libsystem_pthread.dylib 0x00000001932f0c24 pthread_kill + 292
2 libsystem_c.dylib 0x0000000193238864 abort + 104
3 libguile-3.0.1.dylib 0x00000001009092f8 die + 48
4 libguile-3.0.1.dylib 0x000000010090922c initialize_jit + 244
5 libsystem_pthread.dylib 0x00000001932ecdc8 __pthread_once_handler + 80
6 libsystem_platform.dylib 0x000000019333608c _os_once_callout + 32
7 libsystem_pthread.dylib 0x00000001932ecd5c pthread_once + 100
8 libguile-3.0.1.dylib 0x0000000100908dd0 scm_jit_compute_mcode + 732
9 libguile-3.0.1.dylib 0x0000000100962e88 vm_regular_engine + 364
10 libguile-3.0.1.dylib 0x0000000100960c6c scm_call_n + 356
11 libguile-3.0.1.dylib 0x0000000100912f10 scm_primitive_load_path + 820
12 libguile-3.0.1.dylib 0x0000000100963730 vm_regular_engine + 2580
13 libguile-3.0.1.dylib 0x0000000100960c6c scm_call_n + 356
14 libguile-3.0.1.dylib 0x0000000100912f10 scm_primitive_load_path + 820
15 libguile-3.0.1.dylib 0x0000000100903ad4 scm_load_startup_files + 56
16 libguile-3.0.1.dylib 0x0000000100903e64 scm_i_init_guile + 704
17 libguile-3.0.1.dylib 0x000000010095c374 scm_i_init_thread_for_guile + 156
18 libguile-3.0.1.dylib 0x000000010095e1b0 with_guile + 32
19 libgc.1.dylib 0x0000000100a10f78 GC_call_with_stack_base + 36
20 libguile-3.0.1.dylib 0x000000010095c3c0 scm_with_guile + 44
21 libguile-3.0.1.dylib 0x0000000100903b4c scm_boot_guile + 80
22 guile 0x00000001008b3e6c main + 208
23 libdyld.dylib 0x000000019330cf54 start + 4
The latest macOS version implements some new restrictions: the MMU does not allow a physical page to be both writeable and executable. In particular, there is no possibility for executable stack.
FX Coudert
next reply other threads:[~2020-11-07 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 16:27 FX [this message]
2022-12-21 7:20 ` bug#44505: Guile 3.0.4 build fails on macOS Big Sur / ARM lloda
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=1DEC0AB9-23F4-4DD7-90D8-A74DF3B57170@gmail.com \
--to=fxcoudert@gmail.com \
--cc=44505@debbugs.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).