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: Mon, 22 Aug 2022 20:10:00 +0200 [thread overview]
Message-ID: <d35f4d4d-830d-991a-1d55-33689182ed67@telenet.be> (raw)
In-Reply-To: <878rngi99p.fsf@gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 811 bytes --]
On 22-08-2022 17:32, Maxim Cournoyer wrote:
>> 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
> If a module imports a different module, and that module changes, even if
> it's macro, Guile should not blindly reuse the stale .go like it
> currently does. It should complain and evaluate from source instead.
>
> That would cover the base and avoid breakage. After, if it known how to
> do that, yes, it seems it'd be useful to have something similar to 'gcc
> -M' to provide the needed intelligence to the build system.
>
> Does that make sense?
Sounds reasonable, though we could go for something less general in Guix
first.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 1296 bytes --]
[-- 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-22 19:22 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
2022-08-22 15:32 ` Maxim Cournoyer
2022-08-22 18:10 ` Maxime Devos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d35f4d4d-830d-991a-1d55-33689182ed67@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.