Hello. I just tried to download and build the 2.3.0.p1 (portable) release with Cygwin on an NT box. It fails to build because of the use of a perl script. Cygwin does not have Perl installed by default and to be honest it seems like a bit of a stretch to require perl to be able to build shh, that just makes it harder to build. I poked around and it seems like these files depend on perl: contrib/make-shh-known-hosts.pl fixpaths fixprogs I took a quick peek at the fixpaths script and it does not look too complex, seems like something an AWK script would be able to handle. The fixprogs looks more complex, it is used during the build process or just for testing ala "make check" ? I am willing to hack up an awk script to take the place of fixpaths if it will be accepted into the next release. I have checked out the CVS version of the code but I don't see the scripts in there, is there some other CVS module where these scripts live? thanks Mo DeJong Red Hat Inc
The CVS tree you are poking around is the OpenBSD tree. The most recent copy can be picked up from the current nightly snapshot at: http://www.mindrot.org/misc/openssh/ I don't believe that OpenSSH portable CVS tree is public at this point. - Ben On Fri, 1 Dec 2000, Mo DeJong wrote:> Hello. > > I just tried to download and build the 2.3.0.p1 > (portable) release with Cygwin on an NT box. > It fails to build because of the use of a perl > script. Cygwin does not have Perl installed > by default and to be honest it seems like > a bit of a stretch to require perl to be > able to build shh, that just makes it harder > to build. > > I poked around and it seems like these files > depend on perl: > > contrib/make-shh-known-hosts.pl > fixpaths > fixprogs > > I took a quick peek at the fixpaths script > and it does not look too complex, seems > like something an AWK script would be > able to handle. The fixprogs looks > more complex, it is used during the > build process or just for testing > ala "make check" ? > > I am willing to hack up an awk script > to take the place of fixpaths if it > will be accepted into the next release. > > I have checked out the CVS version of > the code but I don't see the scripts > in there, is there some other CVS > module where these scripts live? > > thanks > Mo DeJong > Red Hat Inc >
On Fri, 1 Dec 2000, Mo DeJong wrote:> I took a quick peek at the fixpaths script > and it does not look too complex, seems > like something an AWK script would be > able to handle. The fixprogs looks > more complex, it is used during the > build process or just for testing > ala "make check" ?It is used for building if you are using the builtin random number collection routines.> I am willing to hack up an awk script > to take the place of fixpaths if it > will be accepted into the next release.I am not really that keen on fixing what isn't broken. If you need to do it for other reasons then sure - go ahead, but IMO you energy would be better spent on one of the TODO items :) -d -- | ``We've all heard that a million monkeys banging on | Damien Miller - | a million typewriters will eventually reproduce the | <djm at mindrot.org> | works of Shakespeare. Now, thanks to the Internet, / | we know this is not true.'' - Robert Wilensky UCB / http://www.mindrot.org