From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Guix Help <help-guix@gnu.org>
Subject: Advice about guile-spec package definition
Date: Wed, 31 Mar 2021 23:13:55 +0200 [thread overview]
Message-ID: <5b3fcfc965a4b8fe9cc87a362aad6e5ab63d3420.camel@korwin-zmijowski.fr> (raw)
Dear Guixters,
Hope you are doing well !
I am working on the package definition for
https://framagit.org/Jeko/guile-spec (file: guix.scm). It is a set of
macro based on SRFI-64.
The definition's inputs field is filled with guile-3.0 (or the guix
build reports an error with a stack trace I can't understand haha).
For Guix users willing to try guile-spec before installing it, I know
guix environment can help.
But…
When I use guild (with highest warning level) to compile t.scm[1] in an
environment based on this definition, it raises unknown warnings :
$ guix environment -l guix.scm -- guild compile -W3 /tmp/t.scm
warning: unknown warning type `#{3}#'
wrote `/home/jeko/.cache/guile/ccache/3.0-LE-8-4.2/tmp/t.scm.go'
When I call it outside of the environment, the warning is fine :
$ guild compile -W3 /tmp/t.scm
/tmp/t.scm:3:0: warning: unused variable `name'
wrote `/home/jeko/.cache/guile/ccache/3.0-LE-8-4.4/tmp/t.scm.go'
When I remove Guile from the definition's inputs fiels, the warning is
fine :
$ guix environment -l guix.scm -- guild compile -W3 /tmp/t.scm
/tmp/t.scm:3:0: warning: unused variable `name'
wrote `/home/jeko/.cache/guile/ccache/3.0-LE-8-4.4/tmp/t.scm.go'
[1] t.scm doesn't use guile-spec macro to narrow the context
$ cat /tmp/t.scm
(use-modules (srfi srfi-64))
(test-begin "group")
(test-assert "test" #t)
(test-end)
How can I make it to work ? Maybe I misuse something here… Let me know
!
Cheers,
Jérémy
next reply other threads:[~2021-03-31 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 21:13 Jérémy Korwin-Zmijowski [this message]
2021-04-01 7:22 ` Advice about guile-spec package definition Efraim Flashner
2021-04-01 9:39 ` Jérémy Korwin-Zmijowski
2021-04-01 10:16 ` Efraim Flashner
2021-04-01 11:21 ` Jérémy Korwin-Zmijowski
2021-04-01 12:17 ` Efraim Flashner
2021-04-01 13:09 ` Jérémy Korwin-Zmijowski
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=5b3fcfc965a4b8fe9cc87a362aad6e5ab63d3420.camel@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=help-guix@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).