public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mel Hatzis <hatzis@juniper.net>
To: Chris Jensen <chris-gnats@drspirograph.com>
Cc: help-gnats@gnu.org
Subject: Re: Am I using the wrong docs/package?
Date: Mon, 07 Apr 2003 19:23:00 -0000	[thread overview]
Message-ID: <3E91C24F.7040905@juniper.net> (raw)
In-Reply-To: <200304062351.03896.chris-gnats@drspirograph.com>

On 04/06/2003 06:51 AM, Chris Jensen wrote:
> Hi,
> I'm having  a fair bit of trouble installing gnats on a gentoo system. 
> Theproblems seem to be so fundamental that I think I must have the wrong 
> package or install docs.
> I've tried 
> http://ftp.gnu.org/pub/gnu/gnats/gnats-3.999.1.tar.gz
> and
> http://ftp.gnu.org/pub/gnu/gnats/gnats-3.999.2.tar.gz
> 
> Using the install docs at
> http://www.gnu.org/software/gnats/doc/4_0_beta_snapshot/index.html
> 
> However I've been having multiple problems following the install steps:
> 1. ./configure
> Configure seems to ignore some of the options suggested by the Install Guide

You'll find another configure script in the 'gnats' subdirectory....if you
run 'configure --help' on this one, I expect you'll have better luck
locating the options mentioned in the docs.

The Gnats configure setup is in need of some attention - generally,
there are configure scripts in most of the top level sub-directories
which can be unexpected. In any case, you can specify the configure
options presented by the gnats/configure script to the top-level
configure and it should all work.

> 2. make install-info
> Make reports that the makefile has not install-info target.

I can't see an install-info target either. Not sure what gives here.

> 3. mkdb
> Gives problems about
> /usr/local/com/gnatsdb not existing
> So I create that, and make it writeable by the gnats user
> Then it complians that it cant read
> /usr/local/etc/gnats/databases
> So I create it, then it complains that it can't get any defaults from
> /usr/local/share/gnats/
> and it turns out that that's because that directory is empty
> 
> So what am I doing wrong. I figure I must be going insane because no one else 
> (on the list) seems to be having these problems.

It seems to me that you haven't successfully run 'make install'.
If everything built, try changing to the 'gnats' subdirectory,
and running a make install from there. This should create the
stuff in /usr/local which you created manually.

I suspect that the error you're getting about not getting defaults from
'/usr/local/share/gnats' is incorrect...the error should probably be that
it can't get the defaults from '/usr/local/etc/gnats' which is where
the 4.0beta binaries look for the gnats 'databases' file (prior to 4.0beta,
the 'databases' file lived in /usr/local/share/gnats).

Note that the databases file contains the path to the gnats data
directory - this is what mkdb requires in order to do it's work.

> 
> I'd really appreciate any help
> 

Hope this helps.

--
Mel Hatzis



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

      reply	other threads:[~2003-04-07 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 13:46 Chris Jensen
2003-04-07 19:23 ` Mel Hatzis [this message]

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=3E91C24F.7040905@juniper.net \
    --to=hatzis@juniper.net \
    --cc=chris-gnats@drspirograph.com \
    --cc=help-gnats@gnu.org \
    /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).