Subject: Re: -current, mmaps, and clisp
To: Arnaud Degroote <firstname.lastname@example.org>
From: David Howland <email@example.com>
Date: 11/24/2007 20:40:59
Arnaud Degroote wrote:
> On Sat, Nov 24, 2007 at 07:26:42PM -0500, David Howland wrote:
>> clisp, which I use for pkgmanager, refuses to run with the new kernel.
>> I have tried 4.99.36 and 4.99.37.
>> It has some kind of problems mapping memory, so it seems.
> I have experimented the same issue but it is not kernel related. It is
> due to the use of jemalloc in current instead of the old malloc
> implementation. Clisp seems to do some evil assumption about what malloc
> There is two workaround possible. Rebuild libc using USE_JEMALLOC=NO or
> use the good configure flag for clisp ( --with-gmalloc ). The clisp
> package has been updated to use this flag so I think that if you rebuild
> clisp, everything will be fine.
Oh man, sorry guys. I'll check that right away. I figured that with
the recent talk of mmap and file holes, something had changed.
Thanks for the help!