From: Pierre Neidhardt <mail@ambrevar.xyz>
To: 46424@debbugs.gnu.org
Subject: bug#46424: ASDF build system sometimes fails to load .asd files properly
Date: Wed, 10 Feb 2021 17:36:49 +0100 [thread overview]
Message-ID: <87blcrubfi.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Yesterday I pushed 3aba721da73fbdc3382cc098c41596d5cfbb29eb
"gnu: sbcl-quri: Update to 20200209", which fixes the tests for sbcl-quri.
I noted:
--8<---------------cut here---------------start------------->8---
;; Test system must be loaded before, otherwise tests fail with:
;; Component QURI-ASD::QURI-TEST not found, required by #<SYSTEM
;; "quri">.
'(#:asd-systems '("quri-test" "quri")))
--8<---------------cut here---------------end--------------->8---
Our build system should be able to do better, we should not even have to
specify the asd-systems here. After all, ASDF is smart enough.
Note that:
- If we don't specify the systems, the tests are still run and
succeed(!), it's only the phase that fails with the aforementioned
error.
- If we specify the systems in the reverse order, it still fails!
We've got this issue for many SBCL packages.
Any clue? Guillaume?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next reply other threads:[~2021-02-10 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:36 Pierre Neidhardt [this message]
2021-02-12 10:25 ` bug#46424: ASDF build system sometimes fails to load .asd files properly Guillaume Le Vaillant
2021-05-05 20:55 ` bug#46424: Use load-systems or load-systems* Sharlatan Hellseher
2021-05-08 9:37 ` Guillaume Le Vaillant
2021-05-08 10:00 ` Pierre Neidhardt
2022-09-05 9:10 ` bug#46424: ASDF build system sometimes fails to load .asd files properly Guillaume Le Vaillant
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=87blcrubfi.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=46424@debbugs.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.
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).