public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Bill Munday <bmunday@3glab.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: Installing sourcenav
Date: Tue, 06 Feb 2001 02:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0102061010250.1417-100000@bmunday> (raw)
In-Reply-To: <Pine.LNX.4.21.0102051633570.1417-100000@bmunday>

Hi All SNers,

Thanks for helping me out, I suppose the thing I done wrong was not
clicking on the Downloads link as I thought one had to click on:

	"Download 4.5.2 here!"

There was a comment I read somewhere that Source Nav doesn't support
for more than 500,000 lines of code is this true?

And finally has anyone used it for eCos?

Thanks in advance again.
Bill Munday 

On Mon, 5 Feb 2001, Bill Munday wrote:

> Hi Source Nav users,
> 
> I am very new to the linux world so please excuse my ignornace.
> 
> I thought it would be a good idea to use Source Navigator to understand
> eCos.
> 
> So I downloaded it from http://sources.redhat.com/sourcenav/
> 
> I unzipped the the file.
> 
> Then the problems started, I followed a README that built me lots of GNU
> tools - thanks. But no source navigator.
> 
> I wonder if you could tell me where the instructions are, or if you have
> done it can you tell me how.
> 
> I am using Linux as my desktop and I am working on eCos.
> 
> I also browsed through the emails and as a result decided to send you an
> email.
> 
> Thanks in advance
> Bill Munday
> 
> 
> 

  parent reply	other threads:[~2001-02-06  2:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <981386286.22393.ezmlm@sources.redhat.com>
2001-02-05  8:47 ` Bill Munday
2001-02-05  9:01   ` Ian Roxborough
2001-02-05  9:03   ` Bruce Stephens
2001-02-06  2:23   ` Bill Munday [this message]
2001-02-06  4:22     ` Bruce Stephens
2001-02-08  8:54     ` Bill Munday
2001-02-08  9:54       ` Window Names Bill Munday

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=Pine.LNX.4.21.0102061010250.1417-100000@bmunday \
    --to=bmunday@3glab.com \
    --cc=sourcenav@sourceware.cygnus.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).