This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
Re: libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, java-prs at gcc dot gnu dot org, jddahl at micron dot com, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org
- Subject: Re: libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir
- From: tromey at gcc dot gnu dot org
- Date: 7 Jun 2001 22:59:25 -0000
Synopsis: -d and --output-class-dir= fail to place the .o file in the output dir
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Thu Jun 7 15:59:24 2001
Responsible-Changed-Why:
I'm handling it.
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Thu Jun 7 15:59:24 2001
State-Changed-Why:
I don't think this is really a bug.
I agree it is a bit confusing, but it is what we
decided to do.
`-d' (aka --output-class-dir) only affects the placement
of .class files. It only has any effect when you are
using gcj to generate .class files. In this mode gcj
tries to follow the lead of `javac' (our goal -- which
at present we aren't very close to, is to have `gcj -C'
work like `javac').
When compiling to object code, gcj works more like other
gcc front ends. So for instance the .o file is placed
where the `-o' option says -- and in the absence of `-o'
it is named after the source file and put into `.'.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2730&database=gcc