From mboxrd@z Thu Jan  1 00:00:00 1970
From: tromey@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, jddahl@micron.com, nobody@gcc.gnu.org, tromey@gcc.gnu.org
Subject: Re: libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir
Date: Thu, 07 Jun 2001 15:59:00 -0000
Message-id: <20010607225925.22918.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-06/msg00263.html
List-Id: <gcc-prs.sourceware.org>

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