This is the mail archive of the
mailing list for the GCC project.
Re: Does cpp still open many files.
- To: eliz at is dot elta dot co dot il
- Subject: Re: Does cpp still open many files.
- From: Zack Weinberg <zack at wolery dot cumb dot org>
- Date: Thu, 3 Aug 2000 01:16:08 -0700
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <20000727183822.A4501@lucon.org> <20000731121401.J26185@wolery.cumb.org> <200008011521.e71FLi527277@wolery.cumb.org>
On Tue, Aug 01, 2000 at 06:20:17PM +0200, email@example.com wrote:
> > Date: Mon, 31 Jul 2000 12:14:01 -0700
> > From: Zack Weinberg <firstname.lastname@example.org>
> > Setting rlimits such that
> > (number of per-process files allowed) * (number of parallel gcc
> > instances) < (total number of open files supported) should fix that
> > problem.
> I probably don't know enough about the context, but if the call to
> setrlimit is going to be relevant not only to GNU/Linux systems,
> please note that some systems might not have setrlimit in their
> library, or their setrlimit might not support RLIMIT_NOFILE.
I'm suggesting setting rlimits by hand as a temporary workaround, not
a permanent solution wired into the compiler. (How would we decide
the proper value?)