From: "Jim Avera" <jima@simplex.com>
To: <sourcenav@sources.redhat.com>
Subject: SN50 build issues on Solaris 8
Date: Mon, 18 Mar 2002 01:46:00 -0000 [thread overview]
Message-ID: <AGEHKAPBGMHCDOPJJJFACEGOCAAA.jima@simplex.com> (raw)
Hi,
I downloaded SN50-010322-source.tar.gz from sources.redhat.com and
built it on a sun machine running SunOS 5.8 (Solaris 8).
The following issues arose:
1. The top-level README seems to be a copy of a README
from a gnu tool distribution, not this project, i.e. it is bogus.
I could not find any instructions for configuring or building.
So I did "configure --prefix=$HOME" followed by "gmake"
(using gcc 2.95.3).
2. The Makefile tries to build "all-libremote" but there is no rule
in the Makefile to build this target. So "gmake" fails.
I did "touch all-libremote" to circumvent the above problem,
and then gmake succeeded.
3. "snavigator --batchmode" fails with an error message which implies
that additional options are needed to create a new project.
However the documentation
(source/snavigator/doc/html/enterprise/userguide/cmdlineops.html,
second Example) says that --batchmode (without other options) should
create a new project in the current directory.
I tried various combinations of -p newprojectname and -c but could not
get
batch project creation to work.
What exactly are the correct options to create
a new project in batch mode?
The docs should be coerced into telling the truth.
-Jim Avera
jima@simplex.com
next reply other threads:[~2002-03-15 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 1:46 Jim Avera [this message]
2002-03-18 9:10 ` snavigator bug after 'unload directory' Jim Avera
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=AGEHKAPBGMHCDOPJJJFACEGOCAAA.jima@simplex.com \
--to=jima@simplex.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).