Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <078401c086fd$cfc47320$360510ac@ERDELYM> From: "Erdely, Michael" To: References: <258E47267E4BD3118DCA00805FA72E08052AF423 AT hqmsgsrf03 DOT autodesk DOT com> Subject: Re: Cygwin commands crashes after ssh login Date: Thu, 25 Jan 2001 13:37:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Frank's recompilation success has been repeated. And, I recompiled ASH as well. Problem is gone on three machines. Thanks, Frank (and Yadin). If you're interested in pre-re-compiled binaries, check out ftp://ftp.erdelynet.com/ftp/downloads/bash.exe.gz and ftp://ftp.erdelynet.com/ftp/downloads/sh.exe.gz. If you want some information about installing these files, look at http://mike.erdelynet.com/sshd-error.asp#solution. One note, when I re-compiled bash, I had to create _distribution and _patchlevel files to work. After doing so, though, I was successful. Please let me know if you have any questions/comments, Mike Erdely mailto:mike AT erdelynet DOT com http://mike.erdelynet.com/ ----- Original Message ----- From: To: Sent: Wednesday, January 17, 2001 4:11 PM Subject: Re: Cygwin commands crashes after ssh login > > Hello, > > I'm a newbie to cygwin, but I have this exact problem with sshd, and a little more info on it. > > I'm running Win2K SP1 and using inetd to launch sshd. > I rebuilt bash.exe from the sources and the problem disappeared! > However, I also tried replacing the shell of the logon user with /bin/sh and the problem still occurs. I haven't rebuilt sh.exe. > > Could there be something wrong with the bash.exe in the binary distribution..? > > By the way, it seems that a few lines failed in the configure.in for bash: > > dnl Use GNU m4 macros to get the distribution and patchlevel information > dnl into configure without requiring the files to be distributed > [BASHVERS=]dnl > esyscmd(cat _distribution)dnl > [BASHPATCH]dnl > esyscmd(cat _patchlevel)dnl > > I had to to hack those two lines to get bash to build, is that normal? > > Thanks, > Frank Palazzolo > > frank DOT palazzolo AT autodesk DOT com > > > -- > Want to unsubscribe from this list? > Check out: http://cygwin.com/ml/#unsubscribe-simple > > -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple