This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Failure to build gcc-3.4 20030909 Java sourcefiles: @libgcj.sourcelist: gcj: Internal error: Killed (program jc1)
- From: Andrew Haley <aph at redhat dot com>
- To: Mohan Embar <gnustuff at thisiscool dot com>
- Cc: Jeff Sturm <jsturm at one-point dot com>, tromey at redhat dot com, tcallawa at redhat dot com, c dot christian dot joensson at comhem dot se, "'java'" <java at gcc dot gnu dot org>
- Date: Tue, 16 Sep 2003 16:59:56 +0100
- Subject: Re: Failure to build gcc-3.4 20030909 Java sourcefiles: @libgcj.sourcelist: gcj: Internal error: Killed (program jc1)
- References: <16231.12427.54650.422833@cuddles.cambridge.redhat.com><ZW06B9D0YW42PL4FCA0SR2YNMJF1XHG.3f6732b1@p733>
Mohan Embar writes:
> Hi Andrew,
>
> > > > I'm not sure that we can require huge memory to build libgcj.
> > >
> > > What if libgcj looks for --enable-intermodule, as gcc itself now does?
> > > I'd take that to mean "I have lots of memory, so build in a way that gives
> > > better optimizations and may build faster". Not unlike the current libgcj
> > > situation.
> >
> >Sounds good. Trouble is, we are using this "compile everything at
> >once" to get around a libtool (and/or shell) bug, aren't we?
>
> No. This was purely a cool optimization which I thought would speed
> build time and be harmless. (Ha!) The old way worked just fine, albeit
> slower on systems which had enough memory.
Please either back out this patch or make it conditional on
--enable-intermodule.
Thanks,
Andrew.