libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir

[Tom Tromey]

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

From: Tom Tromey <tromey@redhat.com>
To: jddahl@micron.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir
Date: 03 May 2001 11:50:48 -0600

 >>>>> "Jeff" == jddahl  <jddahl@micron.com> writes:
 
 Jeff> -d and --output-class-dir= don't put the .o file in specified
 Jeff> directory.  The .o is placed in the current directory.
 
 These options only affect .class file output.
 That is, they only do something when you use the `-C' option.
 
 Jeff> Move the file yourself.  Not very conducive to large projects
 Jeff> with many .o files in different directories.
 
 You can use the `-o' option to place the output file.
 
 I personally don't think we need to change this.
 However you might consider raising the issue on the java@gcc.gnu.org
 mailing list to see what others think.
 
 Tom