unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Guile User <guile-user@gnu.org>
Subject: Guile 3.0.7 compile cache messages
Date: Mon, 31 May 2021 19:46:51 +0000	[thread overview]
Message-ID: <bd42d701-da77-b08d-d8b6-48efe896ddb2@posteo.de> (raw)

Hello Guile Users!

It seems my Guile (version 3.0.7, installed via GNU Guile, updated today) is
doing something weird, or perhaps something correct but unexpected with regard
to informing about it finding compile caches. When I run a program with `guile
-L . main.scm`, it displays the following:

~~~~
$ guile -L . main.scm 
;;; note: source file ./logging.scm
;;;       newer than compiled /home/user/.guix-profile/lib/guile/3.0/site-ccache/logging.go
;;; found fresh local cache at /home/user/.cache/guile/ccache/3.0-LE-8-4.5/home/user/dev/guile/lf2-data-files/logging.scm.go
;;; note: source file ./file-reader.scm
;;;       newer than compiled /home/user/.guix-profile/lib/guile/3.0/site-ccache/file-reader.go
;;; found fresh local cache at /home/user/.cache/guile/ccache/3.0-LE-8-4.5/home/user/dev/guile/lf2-data-files/file-reader.scm.go
160
~~~~

This is displayed every single time I run the same program, without making any
changes to the program.

Is this intentional?

I think it used to not display this info all the time. It could become quite
annoying with a bigger program consisting of hundreds of files / modules and
then Guile displaying a note for every single file.

Even with `--no-auto-compile` as in `guile -L . --no-auto-compile main.scm` it
keeps displaying that message.

Is there something I can do, to only make it display a note about caches, when
it finds, that a file needs recompiling, because the cache is not up to date any
longer?

Here is some more detailed information about my versions:

~~~~
$ guix --version
guix (GNU Guix) 4092813037f9fadb2c1da805dc9117277efc7910
Copyright (C) 2021 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ guile --version
guile (GNU Guile) 3.0.7
Copyright (C) 2021 Free Software Foundation, Inc.

License LGPLv3+: GNU LGPL 3 or later <http://gnu.org/licenses/lgpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
~~~~

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




             reply	other threads:[~2021-05-31 19:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 19:46 Zelphir Kaltstahl [this message]
2021-06-01 12:14 ` Guile 3.0.7 compile cache messages Olivier Dion via General Guile related discussions
2021-06-02  6:00   ` Adriano Peluso
2021-06-02  8:52     ` Zelphir Kaltstahl
2021-06-02 10:30       ` Chris Vine
2021-06-02 12:20         ` Zelphir Kaltstahl
2021-06-02 12:38           ` Matt Wette
2021-06-02 16:53           ` Chris Vine
2021-06-02 21:52             ` Zelphir Kaltstahl
2021-06-02 23:09               ` Chris Vine
2021-06-02 20:51           ` Adriano Peluso
2021-06-02 21:45             ` Zelphir Kaltstahl
2021-06-02 22:15               ` Zelphir Kaltstahl

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=bd42d701-da77-b08d-d8b6-48efe896ddb2@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@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).