From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 57121@debbugs.gnu.org
Subject: bug#57121: clojure-build-system fails to compile -- backtrace from language/tree-il/peval.scm
Date: Fri, 19 Aug 2022 22:58:48 +0200 [thread overview]
Message-ID: <e43d48d5-1223-8149-e354-c30107d02c49@telenet.be> (raw)
In-Reply-To: <87ilmohswc.fsf@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1763 bytes --]
On 19-08-2022 22:37, Maxim Cournoyer wrote:
> Hi Maxime.
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> Can't reproduce after touching java-utils.scm.
> I got this issue a couple times too. I attributed it (without analysis)
> to Guile's failure to keep track of changes to macro expanded code.
It might be inlining. I don't see how macro expansion matters here. I
think it's dependency tracking in general.
> More like something to track on the side of Guile, I would think.
I had a patch for build-aux/compile-all.scm that adds a form of
dependency tracking: <https://issues.guix.gnu.org/50384>. If we teach it
about (define-module (foo) #:use-module (bar)) --> (bar) is a dependency
of (foo) (using parts of source-module-closure?) (and drop the
search-patch things), then it seems solved to me.
As there is a known path to a solution, I wouldn't close this.
These patches are for Guix' build system. I don't see anything that
could be done on the Guile side, except for eventually migrating some
dependency tracking stuff over to Guile -- "gcc" has an -M option to use
in combination with "make", maybe Guile could have something similar.
Actually acting on the dependency information (which is part of the
patches) isn't something Guile can do, that seems more something for
"make" (when using Autotools and not like how Guix uses Autotools),
guile-build-system or build-aux/compile-all.scm to me.
> I'd suggest to close it here, since it's not reproducible.
Just wait a few months or something, it keeps popping up -- I have
encountered this one some time in the past.
Also, non-determinism failures (which is a cause of irreproducibility)
are bugs in Guix.
Greetings,
Maxime
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-19 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:59 bug#57121: clojure-build-system fails to compile -- backtrace from language/tree-il/peval.scm Maxime Devos
2022-08-10 17:42 ` Maxime Devos
2022-08-19 20:37 ` Maxim Cournoyer
2022-08-19 20:58 ` Maxime Devos [this message]
2022-08-22 15:32 ` Maxim Cournoyer
2022-08-22 18:10 ` Maxime Devos
2022-08-23 4:06 ` Maxim Cournoyer
2022-08-23 9:07 ` Maxime Devos
2022-08-27 15:53 ` Maxim Cournoyer
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=e43d48d5-1223-8149-e354-c30107d02c49@telenet.be \
--to=maximedevos@telenet.be \
--cc=57121@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).