From: Wayne Dernoncourt <wayned@cpcug.org>
To: Ian Roxborough <irox@redhat.com>
Cc: SourceNav <sourcenav@sources.redhat.com>
Subject: Re: help on installation
Date: Wed, 14 Mar 2001 07:56:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.1010314103255.29300A-100000@cpcug.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010314065557.10164A-100000@cpcug.org>
<lightbulb goes off>
Parallel == Peer - I suppose that does make it easier to clean up later
on, but I don't know.
It gets much farther along before it quits, but it does complain.
Error message:
- - - -
checking whether included gettext is requested... no
checking for libintl.h... (cached) yes
checking for gettext in libc... (cached) yes
checking for msgfmt... (cached) /usr/5bin/msgfmt
checking for dcgettext... (cached) yes
checking for gmsgfmt... (cached) /usr/5bin/msgfmt
checking for xgettext... (cached) /usr/5bin/xgettext
found xgettext programs is not GNU xgettext; ignore it
checking for catalogs to be installed... de es fr ko nl no pl ru sl sv
creating ./config.status
creating Makefile
creating src/Makefile
creating tests/Makefile
creating po/Makefile.in
creating intl/Makefile
creating config.h
config.h is unchanged
Configuring snavigator...
configure: error: can not find sources in ../../SN452/snavigator
Configure in /home1/hermes/wayned/trgt/snavigator failed, exiting.
10:23:25
~/trgt
$
- - - -
sources? here are some C files, what else is needed?
./snavigator/db/dbcp.c
./snavigator/db/dbdump.c
./snavigator/db/dbimp.c
./snavigator/db/dbutils.c
./snavigator/db/longstr.c
./snavigator/db/srchtbl.c
./snavigator/demo/asm_demo/cfunc.c
./snavigator/demo/c++_demo/editline/complete.c
./snavigator/demo/c++_demo/editline/editline.c
./snavigator/demo/c++_demo/editline/sysos9.c
(lots more)
a demo directory doesn't sound right... where and what should these
files be called? Redo the untar process -- this doesn't look
right:
x
SN452-source/snavigator/doc/html/edk/gnupro/2_comp/The_C_Preprocessor
/cppC_Preprocessor_Output.html,
3630 bytes, 8 tape blocks
tar: directory checksum error
where is this in the tree? I'll go out and get this tar file again.
Take care | This clown speaks for himself, his job doesn't
Wayne D. | pay for this, etc. (directly anyway)
next prev parent reply other threads:[~2001-03-14 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 7:04 Wayne Dernoncourt
2001-03-13 10:48 ` Ian Roxborough
2001-03-13 11:39 ` Wayne Dernoncourt
2001-03-13 13:01 ` Wayne Dernoncourt
2001-03-13 19:01 ` Ian Roxborough
2001-03-14 4:05 ` Wayne Dernoncourt
2001-03-14 7:56 ` Wayne Dernoncourt [this message]
2001-03-14 9:39 ` Wayne Dernoncourt
2001-03-14 9:53 ` Ian Roxborough
2001-03-14 11:51 ` D-Man
2001-03-14 13:35 ` Wayne Dernoncourt
2001-03-14 13:54 ` Ben Elliston
2001-03-14 14:46 ` Wayne Dernoncourt
2001-03-14 14:14 ` Ian Roxborough
2001-03-14 14:36 ` Wayne Dernoncourt
2001-03-14 14:48 ` Ian Roxborough
2001-03-14 15:57 ` Wayne Dernoncourt
2001-03-15 0:40 ` Khamis Abuelkomboz (UUNET)
2001-03-15 11:21 ` Syd Polk
2001-03-14 9:51 ` Ian Roxborough
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.GSO.3.96.1010314103255.29300A-100000@cpcug.org \
--to=wayned@cpcug.org \
--cc=irox@redhat.com \
--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).