[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make: *** virtual memory exhausted. Stop.

From: Paul D. Smith
Subject: Re: make: *** virtual memory exhausted. Stop.
Date: Mon, 23 Jun 2003 09:55:33 -0400

%% Fabio Alemagna <address@hidden> writes:

  fa> Ok. Do you know if it still compiles on AmigaOS with ixemul (the
  fa> posix layer)? Well, I guess I can just try and see...

No one has reported that it doesn't, but I'm not sure if anyone has
tried in a while.  I don't have an Amiga system so I can't try it

  >> Barring bugs, though, I don't see any reason why $(eval ...) should
  >> be any more memory or performance intensive than include.  It's all
  >> the same code.

  fa> Ok, then the question translates into this one: how big can a BIG
  fa> make file be? I mean, I'm going to use one big makefile for a
  fa> large project (AROS, http://www.aros.org/), switching from the
  fa> current build system which uses a lot of different tools and about
  fa> 600 makefiles whose average size is of 212 lines: now, do you have
  fa> any rough idea on whether make will consume a lot of memory and on
  fa> whether it will be slow?

Not really.  I don't believe it will (again, barring bugs--and I'm
not aware of any right now), but I've not done any real measurements.

All the major internal structures of GNU make use open hash tables, so
adding lots of targets, etc. should not result in a significant
slowdown.  As far as I'm aware, for example, there are no lookups
or anything that are O(n) or worse.

 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

reply via email to

[Prev in Thread] Current Thread [Next in Thread]