[Gcl-devel] Re: OpenBSD and GCL

[Magnus Henoch]

"Mike Thomas" <address@hidden> writes:

> Hi Camm.
>
> Just a note to let you know that last night I was possessed of the need to
> procrastinate by installing OpenBSD 3.4 and hand tweaking ppp, chat and KDE
> all from some CD's I found on a magazine cover, grab CVS head GCL and
> compile it.
>
> In short GCL doesn't compile out of the box on OpenBSD and OpenBSD seems to
> be quite a nice lightweight Unix install, although you don't get the
> installation automation that Linux and Windows users have come to expect.

I started to port GCL to OpenBSD, but have no complete success yet due
to lack of time and skills.

The attached patch against CVS head is what I have so far.  I haven't
really sorted out the clean way of doing what I've done, so parts of
it are OpenBSD-specific.  I'm also not sure whether all of it is
needed.  The patch to configure.in, though, is probably cross-platform
correct, though it should be cleaned up.

With these patches, and compiling with --enable-machine=FreeBSD and
either --enable-custreloc or --enable-dlopen, the compile proceeds
unto creation of raw_pre_gcl.  Running raw_pre_gcl gives a "Memory
fault", due to infinite recursion eating stack space.

The problem starts in o/alloc.c, line 149, where memory allocation
fails and an error is reported.  For some reason, reporting that error
starts memory allocation, which fails... etc.

Line 149 is:
        IF_ALLOCATE_ERR error("Can't allocate.  Good-bye!");

The IF_ALLOCATE_ERR macro is defined in h/bsd.h, and calls
FIX_RANDOM_SBRK in the same file.  It seems to me that sbrk() on
OpenBSD doesn't behave as this code expects it to behave.

That's where I'm stuck.  I don't know how to proceed from that.

Regards,
Magnus

txtUByx97c6dO.txt
Description: Text document