[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
If you're desperate to run clisp...
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: If you're desperate to run clisp...
- From: Andrew Sveikauskas <asveikau_(_at_)_mail_(_dot_)_rochester_(_dot_)_edu>
- Date: Mon, 14 Nov 2005 22:31:24 -0500
I was looking at the archives for people discussing how to get clisp to
work, and how difficult it would be to work around etc., adding relocation
to the heap files that clisp expects to map. Looking at how clisp works
it seems like no small task.
It was surprising to me that no one had posted the easiest hack of all,
which is... don't hate me for saying this... Linking clisp to a brk-based
malloc. clisp even has one in its source tree.
I'm not suggesting that ports should do this. I'm just posting to mention
the possibility, and so that anyone else who is "desperate to run clisp"
can see that there's a fairly trivial way to do it, without modifying the
behavior of mmap as some have suggested...
I was able to get clisp working like this:
ar cq /usr/local/lib/libgmalloc.a
[ Add -lgmalloc to LIBS in w-clisp-2.33.2p0/build-i386/Makefile ]
Visit your host, monkey.org