From xemacs-m  Mon Mar 24 08:53:59 1997
Received: from amber.vis-av.com (amber.vis-av.com [206.119.44.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id IAA11768
	for <xemacs-beta@xemacs.org>; Mon, 24 Mar 1997 08:53:58 -0600 (CST)
Received: (from derrell@localhost)
          by amber.vis-av.com (8.8.5/8.8.4)
	  id JAA18525; Mon, 24 Mar 1997 09:53:50 -0500 (EST)
Date: Mon, 24 Mar 1997 09:53:50 -0500 (EST)
Message-Id: <199703241453.JAA18525@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: "Karl M. Hegbloom" <karlheg@inetarena.com>
Cc: <xemacs-beta@xemacs.org>
Subject: Re: [19.15b104] Gnus bug solved
In-Reply-To: <199703241238.EAA30319@bittersweet.inetarena.com>
References: <199703241238.EAA30319@bittersweet.inetarena.com>
X-Mailer: VM 6.21 under 19.15 XEmacs Lucid (beta103)
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII

>>>>> "  Karl" == Karl M Hegbloom <karlheg@inetarena.com> writes:

  Karl> The 'memory-exhausted' bug
  Karl> happened again when I recompiled beta 104 from the complete
  Karl> distribution a little while ago.  When I configured, I
  Karl> selected --use-system-malloc as one of the options.

  Karl>  Recompiling with the Gnu-malloc included with XEmacs fixes
  Karl> it, and now Gnus works agian.

This seems to point to an issue that we should possibly handle in
documentation.  With a "configure" script which determines exactly
what it needs to do automagically, people really shouldn't use ANY
options to "configure" unless there is some REALLY GOOD reason to do
so.

Some REALLY GOOD reasons that I can think of:

	1. Modify the automagic enabling/disabling of a feature
	2. Get around an OS bug
		In this case, I'd prefer to see "configure" fixed

	3. er... I can't think of other REALLY GOOD reasons.

Just assume that xemacs and its configurator know what they're doing
and everything should turn out ok.

Derrell

