From: Tim Buck <tbuck@rrinc.com>
To: help-gnats@gnu.org
Subject: My experiences building GNATS 4.10
Date: Wed, 23 Mar 2005 08:35:00 -0000 [thread overview]
Message-ID: <c653610b6e0c49fe3bb6a71d3434527f@rrinc.com> (raw)
In-Reply-To: <20050306205715.GB30918@wookimus.net>
I got an error building GNATS 4.10:
Creating gnats-databases...
make: don't know how to make gnats-pwconv.o. Stop
*** Error code 2
Stop in /usr/projects/tim/gnats-4.1.0.
This is on FreeBSD-4.9 using gcc-2.95.4. I edited gnats/Makefile
and appended "gnats-pwconv.c" to the SOURCES line, which got me
past this error. Then I got this one:
make: don't know how to make send-pr. Stop
*** Error code 2
I can get past this one by going into the send-pr directory and
doing a "make" there. Next I get this error:
-I . -o gnats.info
-I:No such file or directory
*** Error code 1
Stop in /usr/projects/tim/gnats-4.1.0.
I manually ran "makeinfo -I . -o gnats.info gnats.texi" from the
doc directory to get around this.
Tim Buck * Information Technology Manager * Recognition Research, Inc.
PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL tbuck@rrinc.com
Good judgment comes from bad experience; a lot of that comes from
bad judgment.
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2005-03-22 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 21:07 GNATS 4.1.0 Released! Chad Walstrom
2005-03-07 17:35 ` David S Gathright
2005-03-07 18:10 ` 'Chad Walstrom'
2005-03-08 15:42 ` 'Chad Walstrom'
2005-03-08 2:44 ` David S Gathright
2005-03-23 8:35 ` Tim Buck [this message]
2005-03-23 13:37 ` My experiences building GNATS 4.10 Mike M. Volokhov
2005-03-23 15:33 ` Tim Buck
2005-03-24 9:07 ` My experiences building GNATS 4.1.0 Chad Walstrom
2005-03-28 16:59 ` Mike M. Volokhov
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=c653610b6e0c49fe3bb6a71d3434527f@rrinc.com \
--to=tbuck@rrinc.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).