Quoting Janne Johansson <icepic...@gmail.com>:


>
> 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.

Well, OpenBSD is involved as a target system and as the cross
compilation works to different arm64 OS targets it seems to me it is
maybe an issue with OpenBSD ?


But this is a freebsd program running which crashes if you tell it "do
something that outputs openbsd stuff". It's not like the OpenBSD OS can
change in any way so that this fbsd program stops crashing.  It is an issue
with SBCL when told the output should look a certain way.

Now, this bug report might still have some value, in case some decent SBCL
people or OpenBSD have an idea on what could be wrong, but it's weird to
see you trying to circle back on solenes reply to try making it an OpenBSD
problem if it isn't running on OpenBSD.

If you have a fbsd box and run
$ echo 'Linux'
Linux
$ echo 'OpenBSD'
SEGMENTATION FAULT, process 234345 killed, memory access violation
something something

..would you report this as an OpenBSD bug also? Or is "echo" special
compared to sbcl here?

--
May the most significant bit of your life be positive.

Sorry, the FreeBSD involvement seems to be too confusing. I cut it out of the equation by using

- an OpenBSD box (amd64) as a host machine and

ws-3# uname -a
OpenBSD ws-3.my.domain 7.3 GENERIC#1072 amd64

- an OpenBSD box (arm64) as a target machine

ws-4# uname -a
OpenBSD ws-4.my.domain 7.3 GENERIC.MP#2164 arm64

On the host machine I have SBCL installed as OpenBSD package.

ws-3# sbcl
This is SBCL 2.2.5.openbsd

I start the compilation on my host (but something on the target machine is built, too):

./cross-make.sh sync root@target-ip /usr/local/sbcl SBCL_ARCH=arm64

with sbcl git sources cloned on host and target at /usr/locale/sbcl

following https://fiveop.de/blog/sbcl-on-fedora-on-riscv-qemu-on-arch-linux-x86_64.html

The website describes it for riscv arch but I changed it simply to arm64

--------
To build SBCL, I need a copy of the SBCL source on the host and on the target machine. On the target machine it has to be the cloned git repository of the SBCL sources.

After I downloaded the sources to /root/sbcl/ on the target machine and to some arbitrary location on the host machine, I couldstart the build with

$ ./cross-make.sh -p 10000 sync root@localhost /root/sbcl SBCL_ARCH=riscv

on the host machine and then

$ ./make-target-contrib.sh

in the target machine's source directory, to build all the contribs. The default build only builds sb-posix and sb-bsd-sockets.
--------

So in my opinion it can only be something in SBCL or OpenBSD that fails, but I don't know where to look.

Maybe in SBCL, don't know :-/

src/runtime/bsd-os.c
src/runtime/arm64-bsd-os.c

Many thanks.




Reply via email to