Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 3 Mar 2005 03:13:35 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Karl M <karlm30 AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Building OpenSSH
In-Reply-To: <BAY19-F159C0F9A67369B39631779B55B0@phx.gbl>
Message-ID: <Pine.GSO.4.61.0503030307090.2585@slinky.cs.nyu.edu>
References: <BAY19-F159C0F9A67369B39631779B55B0 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 3 Mar 2005, Karl M wrote:

> > From: Igor Pechtchanski
> > Subject: Re: Building OpenSSH
> > Date: Thu, 3 Mar 2005 00:25:37 -0500 (EST)
> >
> > On Wed, 2 Mar 2005, Karl M wrote:
> >
> > > I used the following command from the cygwin openssh readme file.
> > >
> > > ./configure --prefix=/usr --sysconfdir=/etc --libexecdir='$(sbindir)' \
> > > --localstatedir=/var --datadir='$(prefix)/share' \
> > > --mandir='$(datadir)/man' --with-tcp-wrappers
> > >
> > > The configure complains that commands sbindir and datadir are not
> > > defined.  Should I be doing things differently?
> >
> > Those are supposed to be braces, not parentheses.  I.e., use
> > "${sbindir}" instead of "$(sbindir)".  I would also recommend using a
> > font that makes better distinction between "(" and "{".
>
> That is what I suspected...so take a look at the openssh.README
> file...so it is a typo there.

Ah, so it is.  Initially I missed the fact that this was coming from the
README file.  FWIW, the above recommendation (about the fonts) applies
equally well to the README author.  Corinna?

> > > Also, would it be possible for the OpenSSH maintainer to create a
> > > package (pseudo package) that captures the dependencies required to
> > > build OpenSSH?  It would make building it much easier.
> >
> > Is this sentence from the end of /usr/share/doc/Cygwin/openssh.README:
> >
> > 	You must have installed the zlib, the openssl-devel and the
> > 	minires-devel packages to be able to build OpenSSH!
>
> Also TCP Wrappers and I don't recall if there was anything else (it is
> past my bedtime).  It is not worth a lot of work, but it might not be a
> bad way to "document" the dependences.

Hmm, that's certainly a valid point.  However, setup.exe doesn't currently
support source package dependencies, so I guess listing them in the README
is the only way to go ATM.

> > not enough?  Or do you mean stuff like "gcc", "ash", "make", etc?
>
> No, not the tools.

Right.  Just clarifying.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/