From owner-freebsd-ports@FreeBSD.ORG  Sun Sep 14 09:22:08 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 37CD516A4BF
	for <ports@freebsd.org>; Sun, 14 Sep 2003 09:22:08 -0700 (PDT)
Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EE57043FBF
	for <ports@freebsd.org>; Sun, 14 Sep 2003 09:22:06 -0700 (PDT)
	(envelope-from bakul@bitblocks.com)
Received: from bitblocks.com (localhost [127.0.0.1])
	by gate.bitblocks.com (8.12.9/8.12.9) with ESMTP id h8EGM4AX022811;
	Sun, 14 Sep 2003 09:22:06 -0700 (PDT)
	(envelope-from bakul@bitblocks.com)
Message-Id: <200309141622.h8EGM4AX022811@gate.bitblocks.com>
To: Mark Murray <mark@grondar.org>
In-reply-to: Your message of "Sun, 14 Sep 2003 16:02:57 BST."
             <200309141503.h8EF2xqi015839@grimreaper.grondar.org> 
Date: Sun, 14 Sep 2003 09:22:04 -0700
From: Bakul Shah <bakul@bitblocks.com>
cc: ports@freebsd.org
cc: sf@slappy.org
Subject: Re: FreeBSD Maxima port 
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Sep 2003 16:22:08 -0000

> I have fixed the FreeBSD GCL port, and I'm using it locally for your
> maxima port. I have also done some other Maxima fixups to the INFO
> files (portlint -a -b -c was whining). I opted for GCL because I
> couldn't fix cmucl, and cmucl could not compile Maxima - it core
> dumped.

If I remember correctly, cmucl preallocates all the memory
space it will ever use by mmaping.  If the os make some of
these unavailable (due to increase kernel memory use or
whatever) cmucl gets confused.  My experience with is if you
use any of the MAXDSIZ, MAXSSIZ or DFLDSIZ options in your
kernel config file because you want more than 512MB of
datasize, cmucl will coredump.  If these default to the
values in 4.8-stable cmucl works fine.  I haven't kept track
recently but the default in -current used to be the same.  Of
course, the bug you encountered may be different....

maxima works fine with clisp as well.  Would be nice if the
freebsd port of maxima can be made to work will all three.
cmucl is the fastest, clisp is the friendliest and gcl is
what maxima "grew up" on.

Glad to see you have fixed up gcl!