public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20010607225925.22918.qmail@sourceware.cygnus.com> (raw)

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


             reply	other threads:[~2001-06-07 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 15:59 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03 10:46 Tom Tromey
2001-05-03 10:06 jddahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010607225925.22918.qmail@sourceware.cygnus.com \
    --to=tromey@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    --cc=jddahl@micron.com \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).