GNU bug report logs -
#59200
ASDF build system/sbcl doesn't build FASLs on some packages
Previous Next
Reported by: ykonai <mail <at> ykonai.net>
Date: Fri, 11 Nov 2022 19:26:02 UTC
Severity: normal
Done: Guillaume Le Vaillant <glv <at> posteo.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 59200 in the body.
You can then email your comments to 59200 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Fri, 11 Nov 2022 19:26:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
ykonai <mail <at> ykonai.net>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 11 Nov 2022 19:26:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
guix shell sbcl sbcl-uuid --pure -- sbcl --eval '(require :asdf)' --eval '(asdf:load-system :uuid)'
#<THREAD "main thread" RUNNING {100B1E8123}>:
Error opening #P"/gnu/store/in6ndcrnqg9pp2glkbvl1s072zp7r34y-sbcl-uuid-2012.12.26-1.e7d6680/lib/common-lisp/sbcl/uuid/uuid-tmpGHU3ALSV.fasl":
Read-only file system
The issue seems to be that the sbcl-uuid package has an empty
lib/common-lisp/sbcl/uuid directory: the FASL files don't get built.
The build log shows everything is fine
https://ci.guix.gnu.org/build/1670426/log/raw so I believe this has to
be an issue with the asdf-build-system/sbcl itself. It also seems to
affect a number of packages, including from what I've seen: sbcl-numcl,
sbcl-lack, and sbcl-mito. It doesn't seem to be a missing #:asd-systems
argument either (the .asd file is loaded fine per the build log).
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Sat, 12 Nov 2022 09:17:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 59200 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
I've got the same issue while packing cl-graph which has cl-containers as
one of the inputs. It's fails exactly the same where it can't assess
cl-containers FASL file.
Regards,
Oleg
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Tue, 15 Nov 2022 10:45:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 59200 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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---
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Wed, 16 Nov 2022 00:15:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 59200 <at> debbugs.gnu.org (full text, mbox):
Hi,
I can definitely consistently reproduce this issue. Maybe something in
your filesystem could interfere with this? Try:
guix shell sbcl sbcl-uuid --container -- sbcl --eval '(require :asdf)'
--eval '(asdf:load-system :uuid)'
This is on guix commit 8f9588185d74f1f251b041b84d43302c337588ff, which
is from a fresh guix pull.
I was wrong wrt. .fasl files missing: ls -l $(guix build
sbcl-uuid)/lib/common-lisp/sbcl/uuid/ does show that the FASL is there,
it is simply that SBCL arbitrarily decides it needs to be recompiled,
which looks like the problem here. It could be some ASDF upstream bug.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Wed, 16 Nov 2022 10:33:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 59200 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
ykonai via Bug reports for GNU Guix <bug-guix <at> gnu.org> skribis:
> I can definitely consistently reproduce this issue. Maybe something in
> your filesystem could interfere with this? Try:
> guix shell sbcl sbcl-uuid --container -- sbcl --eval '(require :asdf)'
> --eval '(asdf:load-system :uuid)'
>
> This is on guix commit 8f9588185d74f1f251b041b84d43302c337588ff, which
> is from a fresh guix pull.
>
> I was wrong wrt. .fasl files missing: ls -l $(guix build
> sbcl-uuid)/lib/common-lisp/sbcl/uuid/ does show that the FASL is there,
> it is simply that SBCL arbitrarily decides it needs to be recompiled,
> which looks like the problem here. It could be some ASDF upstream bug.
I tried:
--8<---------------cut here---------------start------------->8---
guix time-machine --commit=8f9588185d74f1f251b041b84d43302c337588ff -- \
shell sbcl sbcl-uuid --container -- \
sbcl --no-userinit --eval '(require :asdf)' --eval '(asdf:load-system :uuid)'
--8<---------------cut here---------------end--------------->8---
and it worked without error.
Maybe there is something in your local CL configuration (.sbclrc) that
ASDF doesn't like...
Could you check if you still have an error when ignoring the local
configuration with:
--8<---------------cut here---------------start------------->8---
guix shell sbcl sbcl-uuid --container -- \
sbcl --no-userinit --eval '(require :asdf)' --eval '(asdf:load-system :uuid)'
--8<---------------cut here---------------end--------------->8---
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#59200
; Package
guix
.
(Wed, 16 Nov 2022 12:47:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 59200 <at> debbugs.gnu.org (full text, mbox):
Hi,
It turns out this was due to the fact that I had ironclad git cloned on
my computer, which was accidentally visible via :tree in the ASDF
configuration. ASDF detected that a different ironclad was used and
tried to compile-file to the gnu/store. I thought it was guix-related
since it did occur with both --pure and --container, but I was running
it with the default cwd share on.
Using --container --no-cwd is the solution to this problem.
Reply sent
to
Guillaume Le Vaillant <glv <at> posteo.net>
:
You have taken responsibility.
(Wed, 16 Nov 2022 13:09:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
ykonai <mail <at> ykonai.net>
:
bug acknowledged by developer.
(Wed, 16 Nov 2022 13:09:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 59200-close <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
ykonai <mail <at> ykonai.net> skribis:
> Hi,
>
> It turns out this was due to the fact that I had ironclad git cloned on
> my computer, which was accidentally visible via :tree in the ASDF
> configuration. ASDF detected that a different ironclad was used and
> tried to compile-file to the gnu/store. I thought it was guix-related
> since it did occur with both --pure and --container, but I was running
> it with the default cwd share on.
>
> Using --container --no-cwd is the solution to this problem.
Ok. Closing.
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 15 Dec 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 105 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.