zzkt/osc
1
0
Fork 0
Code Issues7 Pull requests Projects Releases Activity Actions

Some systems failed to build for Quicklisp dist #13

New issue
Closed
opened 2022-09-28 23:53:38 +00:00 by quicklisp · 2 comments
quicklisp commented 2022-09-28 23:53:38 +00:00 (Migrated from github.com)

Building with SBCL 2.2.7.28-02bc916fd / ASDF 3.3.5 for quicklisp dist creation.

Trying to build commit id e46e9b1942

osc fails to build with the following error:

Unhandled PACKAGE-DOES-NOT-EXIST in thread #<SB-THREAD:THREAD "main thread" RUNNING {10016C8003}>: The name "SB-BSD-SOCKETS" does not designate any package.

Full log here

Building with SBCL 2.2.7.28-02bc916fd / ASDF 3.3.5 for quicklisp dist creation. Trying to build commit id e46e9b1942c3bd5a439dceafa576c062a68c6cbd *osc* fails to build with the following error: ``` Unhandled PACKAGE-DOES-NOT-EXIST in thread #<SB-THREAD:THREAD "main thread" RUNNING {10016C8003}>: The name "SB-BSD-SOCKETS" does not designate any package. ``` [Full log here](http://report.quicklisp.org/2022-09-28/failure-report/osc.html)
zzkt commented 2022-09-29 21:28:33 +00:00 (Migrated from github.com)

Thanks for picking this up @quicklisp I haven't looked closely at it for a while but made a few small changes which should improve things. What's the best way to test quicklisp builds currently?

Thanks for picking this up @quicklisp I haven't looked closely at it for a while but made a few small changes which should improve things. What's the best way to test quicklisp builds currently?
quicklisp commented 2022-10-11 09:26:42 +00:00 (Migrated from github.com)

It looks good now, thanks.

Best way would be to try to load it in bare sbcl (not in sly/slime or with
an extensive init file) with ASDF warnings visible. If using quickload, use
:verbose t as well.

On Thu, Sep 29, 2022 at 5:28 PM nik gaffney @.***>
wrote:

Thanks for picking this up @quicklisp https://github.com/quicklisp I
haven't looked closely at it for a while but made a few small changes which
should improve things. What's the best way to test quicklisp builds
currently?

—
Reply to this email directly, view it on GitHub
https://github.com/zzkt/osc/issues/13#issuecomment-1262836842, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACPNLOCNOFSUYP2F5CLATTWAYCY3ANCNFSM6AAAAAAQYIEFCA
.
You are receiving this because you were mentioned.Message ID:
@.***>

It looks good now, thanks. Best way would be to try to load it in bare sbcl (not in sly/slime or with an extensive init file) with ASDF warnings visible. If using quickload, use :verbose t as well. On Thu, Sep 29, 2022 at 5:28 PM nik gaffney ***@***.***> wrote: > Thanks for picking this up @quicklisp <https://github.com/quicklisp> I > haven't looked closely at it for a while but made a few small changes which > should improve things. What's the best way to test quicklisp builds > currently? > > — > Reply to this email directly, view it on GitHub > <https://github.com/zzkt/osc/issues/13#issuecomment-1262836842>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACPNLOCNOFSUYP2F5CLATTWAYCY3ANCNFSM6AAAAAAQYIEFCA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: zzkt/osc#13
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?