search

digikar99 / numericals

SIMD powered simple-math numerical operations on arrays for Common Lisp through CFFI [still experimental]
https://digikar99.github.io/numericals/
MIT License
48 stars 3 forks source link

Some systems failed to build for Quicklisp dist #6

Open quicklisp opened 1 year ago

quicklisp commented 1 year ago

Building with SBCL 2.3.3.83-562a1a329 / ASDF 3.3.5 for quicklisp dist creation.

Trying to build commit id c8dd3ab44557f1d7f37125cac2edfc8c5c62ce44

dense-numericals fails to build with the following error:

Unhandled ASDF/FIND-COMPONENT:MISSING-DEPENDENCY in thread #<SB-THREAD:THREAD tid=542952 "main thread" RUNNING {1001738003}>: Component "dense-arrays+static-vectors" not found, required by #<SYSTEM "dense-numericals">

dense-numericals/magicl fails to build with the following error:

Unhandled ASDF/FIND-COMPONENT:MISSING-DEPENDENCY in thread #<SB-THREAD:THREAD tid=542948 "main thread" RUNNING {1001738003}>: Component "dense-arrays+static-vectors" not found, required by #<SYSTEM "dense-numericals">

numericals/benchmarks fails to build with the following error:

; caught ERROR:
;   READ error during COMPILE-FILE: Package TRIVIAL-COERCE does not exist. Line: 21, Column: -1, File-Position: 465 Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/quicklisp/quicklisp-controller/dist/build-cache/numericals/372c3a674706749c1f5a7b55b8171c33037c6142/numericals-2023.05.0/benchmarks/benchmark.lisp" {1015455A03}>
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=542956 "main thread" RUNNING {1001730113}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "numericals/benchmarks" "benchmark">

Full log here

digikar99 commented 1 year ago

This should be fixed with the latest commit 31e2e701cc66bc4a64825257c7bd42556a534907 and tag.

quicklisp commented 1 year ago

Unhandled SB-KERNEL:SIMPLE-PACKAGE-ERROR in thread #<SB-THREAD:THREAD tid=1318087 "main thread" RUNNING {1001738003}>: The loader tried loading the symbol named MEM-REF into the package named CFFI, but the package did not get defined, and does not exist.

digikar99 commented 1 year ago

I have addressed this in 31f298d14dca13f7401d15c2a1b6875b40de580c and have updated the latest tag to point to the same.

digikar99 commented 1 year ago

Is the commit information this build is using visible anywhere? I'm unable to reproduce it locally using the latest commit/tag; plus the CI also passes.

quicklisp commented 1 year ago

This is when building 31f298d14dca13f7401d15c2a1b6875b40de580c

On Wed, Jun 21, 2023 at 3:10 AM Shubhamkar Ayare @.***> wrote:

Is the commit information this build http://report.quicklisp.org/2023-06-20/failure-report/numericals.html#numericals.common is using visible anywhere? I'm unable to reproduce it locally using the latest commit/tag; plus the CI also passes.

— Reply to this email directly, view it on GitHub https://github.com/digikar99/numericals/issues/6#issuecomment-1600299192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACPNLK45YVDNMCMTPH6ZRDXMKM4RANCNFSM6AAAAAAZHXASYA . You are receiving this because you authored the thread.Message ID: @.***>

digikar99 commented 1 year ago

And, please confirm, we need to ensure that the system is loadable with asdf:load-system, right?

I can confirm that the issue exists prior to https://github.com/digikar99/numericals/commit/31f298d14dca13f7401d15c2a1b6875b40de580c - it exists for 31e2e701cc66bc4a64825257c7bd42556a534907 - but is resolved for 31f298d itself. I had also force pushed the tag to make it point to 31f298d instead of 31e2e70 earlier, in case that becomes an issue.