emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#59200: closed (ASDF build system/sbcl doesn't build FASLs on some pa


From: GNU bug Tracking System
Subject: bug#59200: closed (ASDF build system/sbcl doesn't build FASLs on some packages)
Date: Wed, 16 Nov 2022 13:09:02 +0000

Your message dated Wed, 16 Nov 2022 13:05:29 +0000
with message-id <87tu2z11ym.fsf@kitej>
and subject line Re: bug#59200: reproducibility
has caused the debbugs.gnu.org bug report #59200,
regarding ASDF build system/sbcl doesn't build FASLs on some packages
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
59200: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59200
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: ASDF build system/sbcl doesn't build FASLs on some packages Date: Fri, 11 Nov 2022 10:20:55 +0100
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).



--- End Message ---
--- Begin Message --- Subject: Re: bug#59200: reproducibility Date: Wed, 16 Nov 2022 13:05:29 +0000
ykonai <mail@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.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]