From: Greg Troxel <gdt@lexort.com>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: guile-user@gnu.org
Subject: Re: guile 2.0 and slib build procedure: cache bug?
Date: Fri, 11 Mar 2022 15:05:47 -0500 [thread overview]
Message-ID: <rmilexggspw.fsf@s1.lexort.com> (raw)
In-Reply-To: <CAA2Xvw+Sg9pzHmTAnkT98x39XEeFgmAjzcb29oT12=o7oVAxNg@mail.gmail.com> (Mikael Djurfeldt's message of "Fri, 11 Mar 2022 19:50:34 +0100")
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Mikael Djurfeldt <mikael@djurfeldt.com> writes:
> Hi Greg!
>
> The procedure module-export-all! was introduced in 2.0.1.
>
> It appears that the guile.init (which is distributed with slib, not guile)
> which you are using requires guile 2.0.1.
Thanks for replying.
Sorry, I wasn't precise and meant the 2.0 branch, and in fact I am using
2.0.14. It has module-export-all!, and when thre is no compiled file
everything works as it should. BUt with the compiled file, something
goes wrong.
I guess this is just "2.0.14's complier has a bug, or slib's code
invokes unefined bahavior", and since it doesn't happen with the latest
2.2.x there's nothing much that can be (or should be) done.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
prev parent reply other threads:[~2022-03-11 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 1:49 guile 2.0 and slib build procedure: cache bug? Greg Troxel
2022-03-11 18:50 ` Mikael Djurfeldt
2022-03-11 20:05 ` Greg Troxel [this message]
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=rmilexggspw.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=guile-user@gnu.org \
--cc=mikael@djurfeldt.com \
/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).