From: "Mills, John" <john.mills@atl.viasat.com>
To: "Source Navigator Users (E-mail)" <sourcenav@sources.redhat.com>
Subject: SN-5.0 Building Question
Date: Thu, 26 Apr 2001 06:05:00 -0000 [thread overview]
Message-ID: <5C44CEE7DF7AD4119783000629A813F0D48723@SRV32-EXCH-NTS> (raw)
Hello -
I just built SN-5.0 from 'SN50-010322-source.tar.gz' in a GNU/Linux RH6.2
setup. The "% make" build was successful except for the following error:
"...
make[1]: Leaving directory `/tmp/build/snavigator/libgui'
make: *** No rule to make target `all-libremote', needed by `all-sid'.
Stop.
make[1]: Entering directory `/tmp/build/snavigator/db'
..."
I forced the build to complete ("% make -k") with no further errors, and the
results installed and at least start OK.
What am I missing, and is it important? If so, how can I build the missing
piece(s)?
Thanks.
- John Mills
next reply other threads:[~2001-04-26 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 6:05 Mills, John [this message]
2001-04-26 12:02 ` Mo DeJong
2001-04-26 14:46 Mills, John
2001-04-26 17:17 ` Mo DeJong
2001-04-27 5:59 Mills, John
2001-04-27 15:14 ` Bruce Stephens
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=5C44CEE7DF7AD4119783000629A813F0D48723@SRV32-EXCH-NTS \
--to=john.mills@atl.viasat.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).