Re: more question about porting/gcc

[Bernd Ebert <ebertbd@tick.informatik.uni-stuttgart.de>]

On Fri, 20 Mar 1998, Mario Becroft wrote:

> I imagine that all these problems could be avoided by setting the maximum
> memory per process variable in mint.cnf. If you have enough memory, this
> variable can be set to a value that is less than half the size of the RAM,
> and then you should find that the memory will not keep being broken up
> into smaller and smaller blocks past this size (or at least not so badly).
> It will also stop gcc from eating up all your memory. But if you have less
> than 30 or 40MB RAM it might be difficult to find a suitable value that
> doesn't limit the available memory too much for memory-hungry
> applications.

I do own a hades with 64mb EDO-Ram, but this is still no real possibility,
I do own that much Ram (relative, for Atari) because of scanning and
working with images, it is definitely no solution for me to have 2 times
the ram I really need.
Besides that: with the third big program the problem would come back....

cu,
	Bernd