From: Bruce Stephens <bruce.stephens@messagingdirect.com>
To: Bill Munday <bmunday@3glab.com>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Installing sourcenav
Date: Mon, 05 Feb 2001 09:03:00 -0000 [thread overview]
Message-ID: <vbsnltf4fz.fsf@erwin.isode.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102051633570.1417-100000@bmunday>
Bill Munday <bmunday@3glab.com> writes:
[...]
> 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.
The instructions in the README should be sufficient, I think. In
summary,
% ./configure --prefix=/usr/local/snav
% make
% make install
should be sufficient. You may need to be root to install in
/usr/local/snav (you can install wherever you like; you probably want
to choose a new directory, not reuse something like /usr/local).
You should find there's an executable script called snavigator in
/usr/local/snav/bin which is what you should run.
You must do the "make install", and there are some flags which, if
passed to configure, will mysteriously cause things to fail. For
example, people familiar with Tcl might try --disable-static, but if I
remember correctly, that doesn't work.
Alternatively, if you're using some common distribution of Linux (such
as Red Hat) then you can probably find ready built packages. For
Debian unstable, for example, "apt-get install sourcenav" will do the
necessary installation.
--
Bruce Stephens Bruce.Stephens@MessagingDirect.com
ACI Worldwide/MessagingDirect <URL: http://www.MessagingDirect.com/ >
next prev parent reply other threads:[~2001-02-05 9:03 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 [this message]
2001-02-06 2:23 ` Bill Munday
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=vbsnltf4fz.fsf@erwin.isode.com \
--to=bruce.stephens@messagingdirect.com \
--cc=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).