Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <75F8791C7793D211B64D080036DE1504151C77@milton.sonosight.com> From: "Stewart, Wayne" To: "'earnie_boyd@yahoo.com'" , "Stewart, Wayne" Cc: cygwin users Subject: RE: HELP! - Please Date: Fri, 23 Apr 1999 13:22:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" > > Oh! This has to do with porting issues. To execute the > script from cygtclsh80 > you'll have to `sh -c /tmp/junk' and make sure that the DOS > PATH can find > sh.exe. > Thank you. That works! bash$ cygtclsh80 % sh -c /tmp/junk Test executing a shell script from cygtclsh80 % exec /tmp/junk couldn't execute "\tmp\junk": no such file or directory % exit bash$ So, getting back to my original original question - why dejagnu fails its testsuite (remember that one?): this would mean dejagnu has a bug, since 'runtest' exec's configure scripts (which are also #!/bin/sh scripts) - like 'config.guess' to get the target_triplet under certain circumstances. It uses cygtclsh80's 'exec' command and does not use 'sh -c'. Dejagnu's testsuite also exec's runtest which is a sh script (using expect, not cygtclsh80, but with the same result). Hello dejagnu maintainer! Are you out there somewhere? Wayne -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com