With sbcl version 2.2.0, support for aarch64 FreeBSD has been added to upstream. Could you look into amending the port so it supports this architecture?
Created attachment 232926 [details] v0 Try this patch (it works here)
Maintainer timeout.
(In reply to Mikael Urankar from comment #1) LGTM. Tested with Poudriere on arm64 FreeBSD 13. The test suite passes. Check perhaps if BOOTVERSION can be raised to 2.2.0 for all architectures.
yes, we have to update bootstrap for all archs, the new version fails because of that
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=15b1da831b7cbebe2762fccebcfb3b0d50b27fc9 commit 15b1da831b7cbebe2762fccebcfb3b0d50b27fc9 Author: Mikael Urankar <mikael@FreeBSD.org> AuthorDate: 2022-04-04 11:00:54 +0000 Commit: Mikael Urankar <mikael@FreeBSD.org> CommitDate: 2022-05-03 05:22:17 +0000 lang/sbcl: Add aarch64 support PR: 261096 Reported by: Robert Clausecker Approved by: krion (maintainer timeout) lang/sbcl/Makefile | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
still an issue
Looks like the patch was reverted. What happened?
Ask krion, I'm not involved with this issue anymore.
Was reverted in the following commit, but it does not say why: commit 322efcae932a4ac7090f990ba07a23b85d40bc92 Author: Kirill Ponomarev <krion@FreeBSD.org> Date: Tue May 3 09:17:04 2022 +0200 lang/sbcl: Revert "lang/sbcl: Add aarch64 support" This reverts commit 15b1da831b7cbebe2762fccebcfb3b0d50b27fc9.
`make test` results on aarch64 12.1-STABLE (AWS Graviton a1.large): Finished running tests. Status: Expected failure: dynamic-extent.pure.lisp / DX-COMPILER-NOTES Expected failure: float.pure.lisp / (SCALE-FLOAT-OVERFLOW BUG-372) Expected failure: float.pure.lisp / (ADDITION-OVERFLOW BUG-372) Expected failure: float.pure.lisp / (ADDITION-OVERFLOW BUG-372 TAKE-2) Expected failure: hash.pure.lisp / SXHASH-ON-DISPLACED-STRING Expected failure: selfbuild-output.pure.lisp / MAKE-LIST-%MAKE-LIST-NOT-CALLED Skipped (broken): debug.impure.lisp / (TRACE ENCAPSULATE NIL) Skipped (broken): debug.impure.lisp / (TRACE ENCAPSULATE NIL RECURSIVE) Expected failure: fopcompiler.impure.lisp / FOPCOMPILER-DEPRECATED-VAR-WARNING Expected failure: full-eval.impure.lisp / INLINE-FUN-CAPTURES-DECL Skipped (broken): gethash-concurrency.impure.lisp / (HASH-TABLE UNSYNCHRONIZED) Expected failure: packages.impure.lisp / USE-PACKAGE-CONFLICT-SET Expected failure: packages.impure.lisp / IMPORT-SINGLE-CONFLICT Expected failure: walk.impure.lisp / (WALK MULTIPLE-VALUE-BIND) Expected failure: walk.impure.lisp / (WALK MULTIPLE-VALUE-BIND SPECIAL) (58 tests skipped for this combination of platform and features) ok //apparent success (reached end of run-tests.sh normally)
(In reply to Ed Maste from comment #9) The reason is the merge was done with some errors which I outlined in mailing list, after that mikael@ removed those parts but apparently no one tested sbcl functionality on arm64 except of poudriere build. See my comments on 2022.4.4, bootstrap for arm64 as well as for amd64 contains some issues which are still under review at upstream. I don't know why the committer put "maintainer timeout" into original commit.
(In reply to Kirill Ponomarev from comment #11) > I don't know why the committer put "maintainer timeout" into original commit. You have not accepted or declined the patch in multiple months. Your only response to this PR was comment #4 after which another month passed without any further response. Maintainer timeout is after two weeks, so this is appropriate.
Any progress on this one?
Giving up on this one due to lack of maintainer interest.