On Tue, 2023-06-20 at 13:34 +0200, develo...@robert-palm.de wrote: > > Hi, > > I am trying to cross compile sbcl (a common lisp compiler) from > amd64 > (FreeBSD) to arm64 (OpenBSD) and receive this error during the > compilation: > > ---------------- > //entering make-target-2.sh > //doing warm init - compilation phase > This is SBCL 2.3.5.117-850a8f314-WIP, an implementation of ANSI > Common Lisp. > More information about SBCL is available at <http://www.sbcl.org/>. > > SBCL is free software, provided as is, with absolutely no warranty. > It is mostly in the public domain; some portions are provided under > BSD-style licenses. See the CREDITS and COPYING files in the > distribution for more information. > Initial page table: > Immobile Object Counts > Gen layout fdefn symbol code Boxed Cons Raw Code SmMix Mixed LgRaw > LgCode LgMix Waste% Alloc Trig Dirty GCs Mem-age > 6 0 0 0 0 0 71 0 207 0 293 0 0 0 0.5 37228304 2000000 207 0 0.0000 > Tot 0 0 0 0 0 71 0 207 0 293 0 0 0 0.5 37228304 [3.5% of 1073741824 > max] > Welcome to LDB, a low-level debugger for the Lisp runtime > environment. > ldb> CORRUPTION WARNING in SBCL pid 87552 pthread 0x4c101c290: > Memory fault at 0x257448 (pc=0x25731c) > The integrity of this image is possibly compromised. > Exiting. > ---------------- > > A backtrace shows this: > > ---------------- > ldb> backtrace > Backtrace: > Bad frame pointer 0x10 [valid range=0x409ea0000..0x40a0a0000] > ---------------- > > I already asked sbcl folks, but it seems it is something in OpenBSD > casuing this issue ? > > https://bugs.launchpad.net/sbcl/+bug/2024003 > > Indeed, I can cross compile from my box to an arm64 linux (debian > 11) > without having this issue. > > Please, any ideas why this occurs or suggestions how to make it work > ? > > Many thanks. >
if I understand well, you are on FreeBSD trying to build sbcl for OpenBSD? This is either an SBCL bug or FreeBSD problem, you are not using OpenBSD anywhere in the loop so it's unrelated to OpenBSD. That said, sbcl building has always been fragile on OpenBSD, updating it always require new workarounds. You can take a look at the sbcl OpenBSD packaging to see for patches and command line arguments used for building: https://github.com/openbsd/ports/tree/master/lang/sbcl
