public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jddahl@micron.com
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/2730: -d and --output-class-dir= fail to place the .o file in the output dir
Date: Thu, 03 May 2001 10:06:00 -0000 [thread overview]
Message-ID: <20010503170235.2512.qmail@sourceware.cygnus.com> (raw)
>Number: 2730
>Category: libgcj
>Synopsis: -d and --output-class-dir= fail to place the .o file in the output dir
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu May 03 10:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: jddahl@micron.com
>Release: Compile latest CVS yesterday.
>Organization:
>Environment:
Redhat 6.2
>Description:
-d and --output-class-dir= don't put the .o file in specified
directory. The .o is placed in the current directory.
>How-To-Repeat:
Use the -d or --output-class-dir= compiler option.
>Fix:
Move the file yourself. Not very conducive to large projects
with many .o files in different directories.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-05-03 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 10:06 jddahl [this message]
2001-05-03 10:46 Tom Tromey
2001-06-07 15:59 tromey
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=20010503170235.2512.qmail@sourceware.cygnus.com \
--to=jddahl@micron.com \
--cc=gcc-gnats@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).