public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: SourceNav <sourcenav@sourceware.cygnus.com>
Subject: Re: Error in SourceNavigator installation.
Date: Tue, 18 Jul 2000 15:26:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1000718152306.6332P-100000@cse.cygnus.com> (raw)
In-Reply-To: <3974C9C7.23549B7B@switchco.com>

On Tue, 18 Jul 2000, Benjamin Scherrey wrote:

> Sure enough, running as root, the application seems to startup fine.
> Attached are configure.out, make.out, and install.out which are the
> output from each respective step of the build. I'll try the --prefix
> trick for non-root operation in the meantime.
> 
> 	thanx for the help & later,
> 
> 		Ben Scherrey
> 
> PS: Also, it would be very nice if the .tar.gz file expanded everything
> into its own directory (say SNAV-V.v/) instead of blowing up into my
> current directory! Hard to clean up afterwards... :-(
> 
> Syd Polk wrote:
> > 
> > This means that "make install" failed. I need the output from "make
> > install" to see what is going wrong.
> > 
> > In the meantime, use "configure
> > --prefix=<directory_you_have_write_permission_to>"


I just downloaded the tar ball, ran configure with a --prefix,
built and installed it, and ran it. It seems to work just
fine on my Red Hat 6.2 box. I did not build, install, or
run it as root. I am willing to bet that you installed
or built it as root, is that the case?

Mo DeJong
Red Hat Inc

  reply	other threads:[~2000-07-18 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-18 11:50 Henry.Kleynhans
2000-07-18 11:56 ` Syd Polk
2000-07-18 13:53   ` Benjamin Scherrey
2000-07-18 13:56     ` Syd Polk
2000-07-18 14:45       ` Benjamin Scherrey
2000-07-18 15:26         ` Mo DeJong [this message]
2000-07-18 19:07           ` Benjamin Scherrey
2000-07-18 20:57             ` Mo DeJong
2000-07-18 14:48       ` Benjamin Scherrey

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.SOL.3.91.1000718152306.6332P-100000@cse.cygnus.com \
    --to=mdejong@cygnus.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).