Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Fri, 1 Jun 2001 09:27:19 -0400 (EDT)
From:	"Joseph S. Testa" <jst3290 AT cs DOT rit DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Re: Maintainer of OpenSSH
In-Reply-To:	<20010531211346.A28191@redhat.com>
Message-ID:	<Pine.GSO.4.04.10106010834320.7209-100000@tin.cs.rit.edu>
MIME-Version:	1.0

Hi --


	I'm working on a project involving the secure ftp client from
OpenSSH with cygwin.  I have realized that I must make some very minor
changes to the source code and recompile it myself, but in doing so, I've
ran into a little problem.
	Specifically, I was planning on only packaging sftp.exe &
cygwin1.dll (don't cringe -- I know this sounds odd) with my project.
This works because the sftp.exe that comes with the OpenSSH2.9p1-2 package
seems to be self-sufficient.  Now that I need to recompile the client
myself, I've noticed that after a connection to a host is made, it tries
to exec '/usr/local/bin/ssh'. This fails, of course, because sftp.exe is
being executed directly and not from a bash shell.
	So, I was wondering how exactly the maintainer of OpenSSH compiled
the package so as to create a self-sufficient executable.  Any help is
greatly appreciated.

	Thanks,
	- Joe Testa

__________________________________________
"Those who desire to give up Freedom
in order to gain Security, will not have,
nor do they deserve, either one."

                       -- Thomas Jefferson


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -