X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Mime-Version: 1.0 (Apple Message framework v753.1) Content-Transfer-Encoding: 7bit Message-Id: <0D6D42D2-1441-4985-81BB-1BFEFC96666E@von-campe.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: cygwin AT cygwin DOT com From: Alfred von Campe Subject: Strange problem with running dmake via ssh Date: Wed, 1 Apr 2009 17:03:15 -0400 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I have a strange problem when trying to compile a project under Cygwin with dmake. If I start a remote desktop connection to our Windows 2003 server, and start a Cygwin window (i.e., run Cygwin.bat), I am able to build our project just fine. This also works in a native CMD window. However, if I ssh into the same server (using the same user account), when I try to run dmake I get the following error: $ dmake flashimage dmake .\trioimage.elf LINK_FILE=trioflashimage.ld BOOTING=BOOT_FROM_FLASH dmake: Error -- \bin\bash: No such file or directory dmake.exe: Error code 255, while making 'flashimage' The dmake executable was provided by a 3rd party. What's so different about running a bash shell under ssh than running a bash shell in a CMD window that would cause dmake to behave this way? We'd like to run remote builds automatically, so getting this to work with ssh is kind of important. Thanks, Alfred -- 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/