From: Arun Isaac <arunisaac@systemreboot.net>
To: 32160@debbugs.gnu.org
Subject: bug#32160: auto compile fails to recompile when included source files change
Date: Sun, 15 Jul 2018 07:49:58 +0530 [thread overview]
Message-ID: <cu7in5hdyup.fsf@systemreboot.net> (raw)
Guile's auto compile fails to recompile when included source files
change.
For example, I have two source files -- foo.scm and bar.scm. foo.scm
includes bar.scm using `include'. When I run foo.scm for the first time,
it is auto compiled and run correctly. But, if I modify bar.scm and run
foo.scm again, foo.scm is not rebuilt and the old version is run.
Here is a concrete example of what I mean.
$ cat foo.scm
(include "bar.scm")
$ cat bar.scm
(display "old")
(newline)
$ guile -s foo.scm
;;; note: source file /tmp/test/foo.scm
;;; newer than compiled /home/arun/.cache/guile/ccache/2.2-LE-8-3.A/tmp/test/foo.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /tmp/test/foo.scm
;;; compiled /home/arun/.cache/guile/ccache/2.2-LE-8-3.A/tmp/test/foo.scm.go
old
$ sed -i 's/old/new/' bar.scm
$ cat bar.scm
(display "new")
(newline)
$ guile -s foo.scm
old
In the last step, guile still printed "old" without recompiling. It
should have recompiled and printed "new".
next reply other threads:[~2018-07-15 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 2:19 Arun Isaac [this message]
2018-08-02 18:01 ` bug#32160: auto compile fails to recompile when included source files change Mark H Weaver
2018-08-02 18:52 ` Mark H Weaver
2018-08-02 21:01 ` Mark H Weaver
[not found] ` <20180802200226.GA12552@tuxteam.de>
2018-08-03 8:34 ` Arun Isaac
2018-08-03 16:34 ` Mark H Weaver
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=cu7in5hdyup.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=32160@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).