https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837

--- Comment #14 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #13)
> (In reply to Jakub Jelinek from comment #12)
> > Preapproved with proper ChangeLog entry.
> 
> Unfortunately, there seems to be a problem with the machine in the compile
> farm that I use for gcc development, and I'm not able to finish a
> bootstrap&regression test. I always get:
> 
> couldn't create output pipe for command: too many open files
> 
> even for a pristine copy of GCC. This didn't happen a few days ago. I didn't
> have time yet to investigate what is wrong. If someone can bootstrap&regtest
> the patch for me, I will commit it with proper changelog and send it to
> gcc-patches.
> 
> (Of course, hints on how to fix the above problem are more than welcome.
> This issue prevents me from doing any GCC development right now).

You could display the hard limits first:
 ulimit -H -a
and then increase the soft limits as needed:
 ulimit -a

Reply via email to