public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libgcj/2715: Can't compile on Redhat 6.2
Date: Thu, 03 May 2001 10:46:00 -0000	[thread overview]
Message-ID: <20010503174601.18889.qmail@sourceware.cygnus.com> (raw)

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

From: Tom Tromey <tromey@redhat.com>
To: jddahl <jddahl@micron.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/2715: Can't compile on Redhat 6.2
Date: 03 May 2001 11:48:11 -0600

 >>>>> "Jeff" == jddahl  <jddahl@micron.com> writes:
 
 Jeff> That was it!  Thanks.
 
 I'm going to close the PR.
 
 Jeff> When trying to compile with the following command:
 Jeff> gcj -c -d /u/jddahl/java/objects.linux/test/core
 Jeff> /u/jddahl/java/sources/test/core/InitializationException.java
 Jeff> the .o file is place in the current directory, not
 Jeff> /u/jddahl/java/objects.linux/test/core.
 Jeff> Is there a fix?
 
 The -d flag only affects bytecode output.  I know this seems weird
 from a Java point of view but it is how the rest of gcc works.  You
 can use the -o flag to position the .o file:
 
 gcj -c /u/jddahl/java/sources/test/core/InitializationException.java \
     -o /u/jddahl/java/sources/test/core/InitializationException.o
 
 Tom


             reply	other threads:[~2001-05-03 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 10:46 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03 11:26 jddahl
2001-05-03  9:36 jddahl
2001-05-02 12:56 Tom Tromey
2001-05-02 10:16 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=20010503174601.18889.qmail@sourceware.cygnus.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).