public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: D-Man <dsh8290@rit.edu>
Cc: sourcenav@sources.redhat.com
Subject: Re: Using SourceNav for Java
Date: Thu, 01 Mar 2001 16:51:00 -0000	[thread overview]
Message-ID: <878zmpq8vs.fsf@creche.redhat.com> (raw)
In-Reply-To: <20010301190906.A26591@harmony.cs.rit.edu>

>> | >  If you are using gcj to compile to native, I don't know how
>> | >it handles jar files.  As for the standard libary stuff, it is
>> | >included in libgcj.so (a shared library file).

>> | I still don't see why it can't find stuff like java.io.* then.

gcj uses libgcj.so for linking, but when compiling your Java code it
needs to read libgcj.jar (or libgcj.zip for somewhat older versions of
gcj) too.  Think of the .jar file as the Java equivalent of C header
files...

>> Maybe you need to add -lgcj to the gcj command line?  This is what I
>> would do if ld failed to find some C/C++ symbols (in a C/C++ project).

This should be done automatically by gcj.  If this is the failure then
the odds are the libgcj.so isn't installed at all, or is installed
incorrectly.


The original report doesn't mention what version of gcj is in use, or
the system, or anything, so I can't help too much.  gcj-related
questions really belong on the `java@gcc.gnu.org' mailing list anyway.

Tom

  reply	other threads:[~2001-03-01 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 13:39 source nnavigator on macintosh Christian Fleury
2001-02-27 13:41 ` Mo DeJong
2001-02-27 13:50   ` Using SourceNav for Java Brad Cox
2001-03-01 11:31     ` D-Man
2001-03-01 14:14       ` Brad Cox
2001-03-01 16:09         ` D-Man
2001-03-01 16:51           ` Tom Tromey [this message]
2001-03-02 10:36             ` Brad Cox
2001-03-02 11:35               ` Mo DeJong
2001-02-27 13:58 ` source nnavigator on macintosh Syd Polk
2001-02-28 14:32 Using SourceNav for Java Ian Roxborough

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=878zmpq8vs.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dsh8290@rit.edu \
    --cc=sourcenav@sources.redhat.com \
    /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).