unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: 59200@debbugs.gnu.org
Subject: bug#59200: ASDF build system/sbcl doesn't build FASLs on some packages
Date: Tue, 15 Nov 2022 10:32:37 +0000	[thread overview]
Message-ID: <878rkczedz.fsf@kitej> (raw)
In-Reply-To: <CAO+9K5o4o2STpud0GNOGkk+-pZvKa+SpGj8QHy7+rb2eB_1+BA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

Hi,

I can't reproduce this issue.

I tried
--8<---------------cut here---------------start------------->8---
guix shell sbcl sbcl-uuid --pure -- sbcl --eval '(require :asdf)' --eval '(asdf:load-system :uuid)'
guix shell sbcl sbcl-cl-containers --pure -- sbcl --eval '(require :asdf)' --eval '(asdf:load-system :cl-containers)'
--8<---------------cut here---------------end--------------->8---
and both commands worked without any error.

With each of the following commands, do you see the "uuid.fasl" file at
the end or not?
--8<---------------cut here---------------start------------->8---
ls -l $(guix build sbcl-uuid)/lib/common-lisp/sbcl/uuid/
ls -l $(guix build --check --no-grafts sbcl-uuid)/lib/common-lisp/sbcl/uuid/
--8<---------------cut here---------------end--------------->8---

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-11-15 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  9:20 bug#59200: ASDF build system/sbcl doesn't build FASLs on some packages ykonai via Bug reports for GNU Guix
2022-11-12  9:16 ` bug#59200: Sharlatan Hellseher
2022-11-15 10:32   ` Guillaume Le Vaillant [this message]
2022-11-15 23:09 ` bug#59200: reproducibility ykonai via Bug reports for GNU Guix
2022-11-16 10:20   ` Guillaume Le Vaillant
2022-11-16 12:46     ` ykonai via Bug reports for GNU Guix
2022-11-16 13:05       ` 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=878rkczedz.fsf@kitej \
    --to=glv@posteo.net \
    --cc=59200@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).