libgcj/2715: Can't compile on Redhat 6.2

[jddahl]

The following reply was made to PR libgcj/2715; it has been noted by GNATS.

From: jddahl <jddahl@micron.com>
To: "'tromey@redhat.com'" <tromey@redhat.com>, jddahl <jddahl@micron.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: RE: libgcj/2715: Can't compile on Redhat 6.2
Date: Thu, 3 May 2001 12:20:36 -0600 

 Thanks for the tip.  I'll use the -o flag.
 
 -Jeff
 
 -----Original Message-----
 From: Tom Tromey [ mailto:tromey@redhat.com ]
 Sent: Thursday, May 03, 2001 11:48 AM
 To: jddahl
 Cc: gcc-gnats@gcc.gnu.org
 Subject: Re: libgcj/2715: Can't compile on Redhat 6.2
 
 
 >>>>> "Jeff" == jddahl  <jddahl@micron.com> writes:
 
 Jeff> That was it!  Thanks.
 
 I'm going to close the PR.
 
 Jeff> When trying to compile with the following command:
 Jeff> gcj -c -d /u/jddahl/java/objects.linux/test/core
 Jeff> /u/jddahl/java/sources/test/core/InitializationException.java
 Jeff> the .o file is place in the current directory, not
 Jeff> /u/jddahl/java/objects.linux/test/core.
 Jeff> Is there a fix?
 
 The -d flag only affects bytecode output.  I know this seems weird
 from a Java point of view but it is how the rest of gcc works.  You
 can use the -o flag to position the .o file:
 
 gcj -c /u/jddahl/java/sources/test/core/InitializationException.java \
     -o /u/jddahl/java/sources/test/core/InitializationException.o
 
 Tom