This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/16253] bootstrapping java does not work when using GNU binutils
- From: "rsandifo at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Jul 2004 09:20:30 -0000
- Subject: [Bug bootstrap/16253] bootstrapping java does not work when using GNU binutils
- References: <20040628212020.16253.geos@epost.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rsandifo at redhat dot com 2004-07-19 09:20 -------
Subject: Re: bootstrapping java does not work when
using GNU binutils
Georg Schwarz <geos@epost.de> writes:
>> What does "systune ncargs" say?
>
> I hope this helps:
>
> lorenz 1# systune ncargs
> [snip]
> group: limits (dynamically changeable)
> vnode_free_ratio = 2 (0x2)
> maxup = 150 (0x96)
> reserve_ncallout = 5 (0x5)
> maxsymlinks = 30 (0x1e)
> nprofile = 100 (0x64)
> maxwatchpoints = 100 (0x64)
> shlbmax = 8 (0x8)
Hmm, so ncargs must just be an IRIX 6 thing. Is there some other way
of controlling the command-line limit?
As you'll probably have guessed, I don't have access to an IRIX 5 box
myself, so can you try to debug it a bit more at your end? E.g., does
it fail if you cut-&-paste the failing command line into a shell?
FWIW, there are successful build reports with binutils:
http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00761.html
Given that the failure is in a long, but otherwise innocuous, shell command,
and that that command would be shorter when not using binutils, it really
does look like a limits issue to me. One possible workaround would be to
move the gcc sources so that the full pathname to them is shorter.
Richard
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16253