From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Getting rid of "source file [...] newer than compiled" messages
Date: Wed, 10 Apr 2019 09:31:03 -0500 [thread overview]
Message-ID: <87wok2ortk.fsf@gmail.com> (raw)
In-Reply-To: <87h8b9f14s.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 08 Apr 2019 08:43:15 +0200")
Ricardo Wurmus <rekado@elephly.net> writes:
> You said that there are no .go files, yet Guile keeps saying that the
> source file
> /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/hash.scm
> is newer than the compiled
> /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go
>
> Does the second file really not exist while the first one does?
Correct:
#+BEGIN_EXAMPLE
ls -a /gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt
. .. base16.scm base64.scm common.scm hash.scm hmac.scm package-config.scm pk-crypto.scm random.scm utils.scm
#+END_EXAMPLE
--
Katherine
next prev parent reply other threads:[~2019-04-10 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:55 Getting rid of "source file [...] newer than compiled" messages Katherine Cox-Buday
2019-03-28 21:40 ` Ricardo Wurmus
2019-03-29 1:45 ` Katherine Cox-Buday
2019-03-29 2:46 ` Ricardo Wurmus
2019-03-29 15:21 ` Katherine Cox-Buday
2019-04-06 19:39 ` Katherine Cox-Buday
2019-04-06 20:39 ` Ricardo Wurmus
2019-04-06 21:15 ` Katherine Cox-Buday
2019-04-06 21:24 ` Gábor Boskovits
2019-04-07 3:11 ` Ricardo Wurmus
2019-04-07 17:31 ` Katherine Cox-Buday
2019-04-08 6:43 ` Ricardo Wurmus
2019-04-10 14:31 ` Katherine Cox-Buday [this message]
2019-04-10 16:04 ` Andreas Enge
2019-04-10 16:24 ` Katherine Cox-Buday
2019-04-10 16:49 ` Ricardo Wurmus
2019-04-10 18:04 ` Katherine Cox-Buday
2019-04-10 18:22 ` Ricardo Wurmus
2019-04-10 20:20 ` Katherine Cox-Buday
2019-04-11 12:47 ` Giovanni Biscuolo
2019-04-11 14:34 ` Katherine Cox-Buday
2019-04-11 17:16 ` Giovanni Biscuolo
2019-04-17 21:01 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wok2ortk.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).