public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Paul F. Kunz" <Paul_Kunz@slac.stanford.edu>
To: sourcenav@sources.redhat.com
Subject: Bug report
Date: Mon, 24 Jul 2000 19:43:00 -0000	[thread overview]
Message-ID: <200007250242.TAA32077@libra.slac.stanford.edu> (raw)

   I couldn't find on the Web a better address to submit a bug
report.   Please forward to a more proper address.

   This in an installation bug.  I did the following and snavigator
failed to run...

- download source, unzip, untar.

- configure  (no options, system is Red Hat Linux 6.1 on Intel platform)

- make

- su'ed to root and did `make install'.

- quit root session, did `rehash' and typed `snavigator' which failed
  on `sn_tcl_tk_init' (or something like that).


   Grep'ing as myself in /usr/local/share I found...

cd /usr/local/share/
find . -type f -print0 | xargs -0 -e grep -n -e sn_tcl_tk_init
grep: ./sdk/include/db.h: Permission denied
grep: ./sdk/include/cdefs.h: Permission denied
grep: ./gui/tclIndex: Permission denied
./gui/sninit.tcl:772:proc sn_tcl_tk_init {} {

After su'ing to root and fixing these permissions, then snavigator
launched and operated fine under my user account.

P.S.

   I've considered many times buying a 5-10 user license for Source
Navigator.   But I could never quite justify it because someone else
on my site has already bought a 25 user license for SNiFF+ which is
more or less an equivalent product.   Source Navigator is considerablely
easier to use on a new project than SNiFF+, thus with it becoming
GPL'd, the choice is obvious.




             reply	other threads:[~2000-07-24 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24 19:43 Paul F. Kunz [this message]
2000-07-24 20:11 ` Mo DeJong
2000-07-25  7:26   ` Paul F. Kunz
2000-07-25 19:25 Paul F. Kunz
2000-07-25 19:42 bug report Paul F. Kunz
2000-07-25 19:44 ` Albert Wong
2000-07-25 20:12   ` Paul F. Kunz
2000-07-25 19:45 ` Ben Elliston
2000-07-25 20:17   ` Paul F. Kunz
2000-07-25 20:43     ` Mo DeJong
2000-07-25 21:17       ` Ben Elliston

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=200007250242.TAA32077@libra.slac.stanford.edu \
    --to=paul_kunz@slac.stanford.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).