From: Geert Janssens <info@kobaltwit.be>
To: 18835@debbugs.gnu.org
Subject: bug#18835: load-from-path is inconsistent when looking for a compiled version of the source file
Date: Sat, 25 Oct 2014 19:09:09 +0200 [thread overview]
Message-ID: <2787802.8pnN87I00l@legolas.kobaltwit.lan> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1903 bytes --]
$ guile --version
guile (GNU Guile) 2.0.11
$ config.guess
x86_64-unknown-linux-gnu
$ rpm -qa | grep guile
compat-guile18-1.8.8-7.fc20.x86_64
guile-debuginfo-2.0.11-1.fc20.x86_64
guile-2.0.11-1.fc20.x86_64
guile-devel-2.0.11-1.fc20.x86_64
These steps illustrate the issue:
1. Download the attached file and save it as $HOME/guile/test.scm
Note: this is just an example file printing one line to indicate is has
successfully been called. Any other scm file will do to illustrate this bug.
2. Run these commands:
$ mkdir -p $HOME/guile/ccache
$ cd $HOME/guile/ccache
$ guild compile -o test.go ../test.scm
$ guild compile -o test.scm.go ../test.scm
This will generate two compiled versions of the test file, each with a different extension.
Now run these commands and observe what happens:
$ cd $HOME/guile
$ GUILE_LOAD_PATH=$HOME/guile \
GUILE_LOAD_COMPILED_PATH=$HOME/guile/ccache \
guile -c '(load-from-path "test")'
=> This command will use the file $HOME/guile/ccache/test.go. That is, no auto-compilation
is triggered.
$ GUILE_LOAD_PATH=$HOME/guile \
GUILE_LOAD_COMPILED_PATH=$HOME/guile/ccache \
guile -c '(load-from-path "test.scm")'
=> This command will *not* use either of $HOME/guile/ccache/test.go or
$HOME/guile/ccache/test.scm.go. Instead it will autocompile test.scm into <default-cache-
dir>/test.scm.go and use that one.
So there is no way to have the second command use your self-compiled files.
From Andy Wingo's comments on irc, it is expected that the second case would have used the
self-compiled $HOME/guile/ccache/test.scm.go. I'm fine with that although using
$HOME/guile/ccache/test.go would have made more sense from an outsider's point of view. At
least it should be possible to make load-from-path use a self-compiled .go file regardless of
whether the argument ends in .scm or not.
If more information is needed, feel free to ask.
Regards,
Geert
[-- Attachment #1.2: Type: text/html, Size: 9369 bytes --]
[-- Attachment #2: test.scm --]
[-- Type: text/x-scheme, Size: 38 bytes --]
(display "Testfile is read")(newline)
next reply other threads:[~2014-10-25 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:09 Geert Janssens [this message]
2016-06-22 8:28 ` bug#18835: load-from-path is inconsistent when looking for a compiled version of the source file Andy Wingo
2021-05-17 20:25 ` 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=2787802.8pnN87I00l@legolas.kobaltwit.lan \
--to=info@kobaltwit.be \
--cc=18835@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).