From owner-freebsd-hackers  Mon Dec 22 03:41:18 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA18010
          for hackers-outgoing; Mon, 22 Dec 1997 03:41:18 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA18002
          for <FreeBSD-Hackers@freebsd.org>; Mon, 22 Dec 1997 03:41:13 -0800 (PST)
          (envelope-from toor@dyson.iquest.net)
Received: (from root@localhost)
	by dyson.iquest.net (8.8.8/8.8.8) id GAA01265;
	Mon, 22 Dec 1997 06:40:45 -0500 (EST)
	(envelope-from toor)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199712221140.GAA01265@dyson.iquest.net>
Subject: Re: gcc error
In-Reply-To: <19971222164749.21879@lemis.com> from Greg Lehey at "Dec 22, 97 04:47:49 pm"
To: grog@lemis.com (Greg Lehey)
Date: Mon, 22 Dec 1997 06:40:45 -0500 (EST)
Cc: chuckr@glue.umd.edu, FreeBSD-Hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Greg Lehey said:
> On Mon, Dec 22, 1997 at 12:58:23AM -0500, Chuck Robey wrote:
> > I was trying to compile ddd version 2.2 for a project, and I got an error:
> >
> > ==> Making all in ./ddd...
> > Building ddd-2.2-i386-unknown-freebsd3.0...
> > c++  -DHAVE_CONFIG_H -DNDEBUG -O2 -g -Wall -fexternal-templates
> > -felide-constructors -fconserve-space -c -I. -I. -I./..
> > -I/usr/X11R6/include -o ddd.o ddd.C
> > ddd.C: In function `int main(int, char **)':
> > ddd.C:2490: virtual memory exhausted
> > *** Error code 1
> >
> > This can't possibly refer to FreeBSD's memory, seeing as this is a big
> > machine, with 192M of swap, and it wasn't even fractionally full.  I think
> > it's some gcc/g++ (note it's a C++ file being compiled) problem, but I
> > don't know how to increase g++'s idea of memory.
> >
> > Does anyone else know how?
> 
> Yes, this is a per-process limit.  Check with ulimit or friends:
> 
Note that GCC (the C++ part) can get really really big.

-- 
John                  | Never try to teach a pig to sing,
dyson@freebsd.org     | it just makes you look stupid,
jdyson@nc.com         | and it irritates the pig.