From: Guy Gastineau <strings.stringsandstrings@gmail.com>
To: 43394@debbugs.gnu.org
Subject: bug#43394: DYNAMIC-LINK is unbound when using r6rs library syntax
Date: Sun, 13 Sep 2020 23:07:26 -0400 [thread overview]
Message-ID: <CAHgGP-+OmbA8W5kvVjqm3URt4k9-Ub3PSFiQfWW3xdzvsdv12A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]
Guile version 3.0.4.38-64c894
I am on 64 bit arch linux, and I built guile3.0 from the AUR package
guile-git on Sep 12 2020
https://aur.archlinux.org/guile-git.git for the PKGBUILD (the config
options were practically non-existent).
I am writing to modules that dynamically link. DYNAMIC-LINK works in the
top level REPL, and when using DEFINE-MODULE.
When using the r6rs library syntax DYNAMIC-LINK is considered unbound and
the compilation fails.
The following is an example of the behavior with a minimally viable source
for reproducing the bug.
(library (fail-link (0 1))
(export link)
(import)
(define link dynamic-link))
What I get:
;;; note: source file /home/guy/guile-fail-link.scm
;;; newer than compiled
/home/guy/.cache/guile/ccache/3.0-LE-8-4.4/home/guy/guile-fail-link.scm.go
;;; compiling /home/guy/guile-fail-link.scm
;;; guile-fail-link.scm:4:2: warning: possibly unbound variable
`dynamic-link'
;;; compiled
/home/guy/.cache/guile/ccache/3.0-LE-8-4.4/home/guy/guile-fail-link.scm.go
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
Unbound variable: dynamic-link
What I expect:
;;; note: source file /home/guy/guile-fail-link.scm
;;; newer than compiled
/home/guy/.cache/guile/ccache/3.0-LE-8-4.4/home/guy/guile-fail-link.scm.go
;;; compiling /home/guy/guile-fail-link.scm
;;; compiled
/home/guy/.cache/guile/ccache/3.0-LE-8-4.4/home/guy/guile-fail-link.scm.go
Additional information:
After I load the failing library I lose a bunch of top level definitions
and syntax. Like IMPORT is no longer recognized and I have to `,q`
in order to get the REPL in a usable state again.
I can just use DEFINE-MODULE, but honestly I like the r6rs syntax. Even
though imports between schemes differ enough (and FFI anyway)
that none of these libraries will end up being portable, I still like r6rs
library syntax.
If I need to find extra information for to help you all figure out what is
happening, please just let me know.
Also, thank you all for your hard work. I am excited to have this snappy
Guile 3 on my system now ;)
- Guy Gastineau
[-- Attachment #2: Type: text/html, Size: 3236 bytes --]
next reply other threads:[~2020-09-14 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 3:07 Guy Gastineau [this message]
2020-09-14 9:29 ` bug#43394: DYNAMIC-LINK is unbound when using r6rs library syntax Linus Björnstam
2021-05-12 21:14 ` Taylan Kammer
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=CAHgGP-+OmbA8W5kvVjqm3URt4k9-Ub3PSFiQfWW3xdzvsdv12A@mail.gmail.com \
--to=strings.stringsandstrings@gmail.com \
--cc=43394@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).