From: Brad Cox <bcox@virtualschool.edu>
To: Mo DeJong <mdejong@redhat.com>, sourcenav@sources.redhat.com
Subject: Using SourceNav for Java
Date: Tue, 27 Feb 2001 13:50:00 -0000 [thread overview]
Message-ID: <p05010403b6c1d185b903@[192.168.1.2]> (raw)
In-Reply-To: <Pine.SOL.3.91.1010227133947.20315G-100000@cse.cygnus.com>
I've subscribed to this list after trying everything else I could
think of to get Java compiling via SN and GCJ. Can't seem to make it
find the core java libraries (java.io.*). I've tried including the
.jars as files, as directories, by expanding the jars into
directories and including the files as files and as directories).
Nothing works.
How does SN regard jars anyway? As includes? As directories? As
files? As linker command line options?
Thanks! I'd really appreciate the help.
At 1:41 PM -0800 02/27/2001, Mo DeJong wrote:
>On Tue, 27 Feb 2001, Christian Fleury wrote:
>
>> Any project to port sorce nav on MacOS 9.1
>
>That is not going to happen. MacOS has
>no exec, so it would be really really
>hard to do properly.
>
> > and/or MacOS X?
>
>That might happen, but there are no plans.
>
>Mo DeJong
>Red Hat Inc
--
---
Dr. Brad Cox; bcox@superdistributed.com
Phone: 703 361 4751 Fax: 703 995 0422 Cellular: 703 919-9623
http://superdistributed.com: A new paradigm for a new millinneum
PGP Signature: E194 C6E5 92D8 B8FB 20E8 8667 929A 95A0 FCB6 7C62
next prev parent reply other threads:[~2001-02-27 13:50 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 ` Brad Cox [this message]
2001-03-01 11:31 ` Using SourceNav for Java D-Man
2001-03-01 14:14 ` Brad Cox
2001-03-01 16:09 ` D-Man
2001-03-01 16:51 ` Tom Tromey
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='p05010403b6c1d185b903@[192.168.1.2]' \
--to=bcox@virtualschool.edu \
--cc=mdejong@redhat.com \
--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).