This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libgcj/2715: Can't compile on Redhat 6.2
- To: tromey at gcc dot gnu dot org
- Subject: Re: libgcj/2715: Can't compile on Redhat 6.2
- From: Tom Tromey <tromey at redhat dot com>
- Date: 3 May 2001 17:46:01 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Tom Tromey <tromey at redhat dot com>
The following reply was made to PR libgcj/2715; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: jddahl <jddahl@micron.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/2715: Can't compile on Redhat 6.2
Date: 03 May 2001 11:48:11 -0600
>>>>> "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