Re: [MinGW] Failure Building libjava

[Mike Stump <mrs at apple dot com>]

On Mar 30, 2007, at 2:10 PM, Null Heart wrote:
> ... No file failed.

You've not read the output correctly.  The file named by make failed,  
that file named is gnu/javax/swing/text/html/parser/HTML_401F.lo.

> GCJ did not give an error.

That then is a bug is gcj, a failed compile should produce output. I  
would first have to ask, are you sure your not outwitting yourself with:

make bootstrap 1>Make.out.log.txt 2>Make.error.log.txt

?  Hint, don't do that..  Do make >log 2>&1 instead.

> The only error was the generic make error. I know, I repeated the  
> process and varieties for
> hours trying to track down an error on my part. I get "make[3]: ***
> [gnu/javax/swing/text/html/parser/HTML_401F.lo] Error 1" and no other
> error.

That is consistent with misunderstanding what is in Make.out.log.txt  
and Make.error.log.txt.

> > > Running the included libtool command manually without the "-O2"
> > > worked perfectly.
> >
> > Run the command with the -O2 option, does it fail?  If so, does it
> > always fail if you run it 5 times?  If so, that bug is probably a run
> > of the mill compiler bug.  Feel free to file a bug report.  Do make
> > sure you have enough memory and paging file space on the system  
> > though.
>
> The "-O2" is there, apparently, by default. It took removing it to
> finish the compile.

I notice that you didn't answer my question if it fails if you run it  
with -O2 by hand.  If you had, I suspect it would have given you  
output that would have made it clear.

> The bug may be in the compiler, but I don't have enough specific  
> information to file a bug report

The compiler (name of snapshot/svn revision number) fails to build on  
a mingw32 system, it dies with make[3]: *** [gnu/javax/swing/text/ 
html/parser/HTML_401F.lo] Error 1.  That should be enough to get the  
ball rolling.

> or I already would have.

> http://gcc.gnu.org/ml/java-patches/2007-q1/msg00321.html

Ah, yes, probably the same problem.  If you run it by hand, and it  
runs out of memory, you can be fairly certain that is the same problem.

Anyway, that problem can be discussed on the java list directly, I'd  
expect they might say more about it there, if you're interested.