From: Benjamin Scherrey <scherrey@switchco.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: SourceNav <sourcenav@sourceware.cygnus.com>
Subject: Re: Error in SourceNavigator installation.
Date: Tue, 18 Jul 2000 19:07:00 -0000 [thread overview]
Message-ID: <39750C98.AFD583F8@switchco.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1000718152306.6332P-100000@cse.cygnus.com>
Yep - its long been my habit (and common practice amoungst automake/conf
configured apps) to switch to root before performing the final install.
I guess SourceNav does some strange things that prohibit this from
working. So.. my status is that I can install SourceNav on a per-user
basis using the --prefix option in configuration but cannot just
globally install the product for all users. I suppose I could make a
globally writable directory for all to use but that's not the greatest
idea as far as security and just plain stability of the system is
concerned. I hope these are just first light hiccups and not intended
consequences.
thanx & later,
Ben Scherrey
Mo DeJong wrote:
> 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
next prev parent reply other threads:[~2000-07-18 19:07 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
2000-07-18 19:07 ` Benjamin Scherrey [this message]
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=39750C98.AFD583F8@switchco.com \
--to=scherrey@switchco.com \
--cc=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).