Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <75F8791C7793D211B64D080036DE1504151C72@milton.sonosight.com>
From: "Stewart, Wayne" <wayne DOT stewart AT sonosite DOT com>
To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: HELP! - Please
Date: Fri, 23 Apr 1999 10:55:47 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

Hello again,

I have narrowed down my problem a bit since my
original posting.  Also did a mailing list search
on "no such file or directory" and found nothing
that matches this problem.  Can *anyone* reproduce
the behavior I'm seeing, or is something just really
hosed with my setup.  If the latter, any clues, hints,
pointers, rtfms, etc. would be greatly appreciated!

Here's the scenario (cygwin-b20.1):

bash$ mount
Device           Directory           Type        Flags
f:               /zip                native      text!=binary
a:               /floppy             native      text!=binary
e:               /cdrom              native      text!=binary
c:               /c                  native      text!=binary
d:               /                   native      text!=binary
bash$ cat /tmp/junk
#!/bin/sh

echo "Test executing a shell script from cygtclsh80"
bash$ /tmp/junk
Test executing a shell script from cygtclsh80
bash$ ls -l /tmp/junk
-rwxr-xr-x   1 wstewa   users          67 Apr 23 10:44 /tmp/junk
bash$ type cygtclsh80
cygtclsh80 is hashed (/cygnus/CYGWIN~1/H-I586~1/bin/cygtclsh80)
bash$ cygtclsh80
% /tmp/junk
couldn't execute "\tmp\junk": no such file or directory
% exec /tmp/junk
couldn't execute "\tmp\junk": no such file or directory
% exit
bash$

Thanks,
    Wayne Stewart
    wstewart AT sonosite DOT com

> -----Original Message-----
> From: Stewart, Wayne [mailto:wayne DOT stewart AT sonosite DOT com]
> Sent: Thursday, April 22, 1999 11:10 AM
> To: 'cygwin AT sourceware DOT cygnus DOT com'
> Subject: errors in dejagnu's own testsuite
> 
> 
> 
> Hi (from a newbie):
> 
> Has anyone gotten dejagnu's own testsuite to
> run successfully?  I'm using cygwin b20.1
> w/ egcs 1.1.2 binary distribution.
> I get the same results using the dejagnu
> in the cygwin source tree and the dejagnu
> from dejagnu-19981026.tar.gz in
> ftp://go.cygnus.com/pub/ftp.cygnus.com/egcs/infrastructure
> (which is better, i.e., more up-to-date w/ fixes ??)
> 
> Thanks,
>     Wayne Stewart
>     wstewart AT sonosite DOT com
> 
> Here's what happens (does not instill confidence):
> 
> bash$ mount
> Device           Directory           Type        Flags
> f:               /zip                native      text!=binary
> a:               /floppy             native      text!=binary
> e:               /cdrom              native      text!=binary
> c:               /c                  native      text!=binary
> d:               /                   native      text!=binary
> bash$ make check
> rootme=`pwd`; export rootme; \
> srcdir=/cygnus/cygwin-b20/src/dejagnu/testsuite ; export srcdir ; \
> EXPECT=/cygnus/cygwin-b20/obj/dejagnu/../expect/expect ; 
> export EXPECT ; \
> if [ -f ${rootme}/../../expect/expect ] ; then  \
>    TCL_LIBRARY=`echo -I/cygnus/cygwin-b20/src/tcl/generic | 
> sed -e 's/-I//'
> -e 's/generic/library/'` ; \
>    export TCL_LIBRARY ; fi ; \
> /cygnus/cygwin-b20/src/dejagnu/runtest
> RUNTEST=/cygnus/cygwin-b20/src/dejagnu/runtest --tool runtest --srcdir
> /cygnus/cygwin-b20/src/dejagnu/testsuite
> WARNING: Couldn't find the global config file.
> WARNING: Couldn't find tool init file
> Test Run By wstewa on Thu Apr 22 10:27:01 1999
> Native configuration is i686-pc-cygwin32
> 
> 		=== runtest tests ===
> 
> Schedule of variations:
>     unix
> 
> Running target unix
> Using 
> /cygnus/cygwin-b20/src/dejagnu/testsuite/../config/base-config.exp as
> tool-and-target-specific interface file.
> Using /cygnus/cygwin-b20/src/dejagnu/baseboards/unix.exp as board
> description file for target.
> Using /cygnus/cygwin-b20/src/dejagnu/config/unix.exp as 
> generic interface
> file for target.
> Using /cygnus/cygwin-b20/src/dejagnu/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running 
> /cygnus/cygwin-b20/src/dejagnu/testsuite/runtest.all/libs.exp ...
> Running 
> /cygnus/cygwin-b20/src/dejagnu/testsuite/runtest.all/options.exp ...
> FAIL: No arguments
> FAIL: Loading library files
> FAIL: Loading basic packages
> FAIL: Bad argument
> FAIL: Bad tool name
> FAIL: Display help
> FAIL: Verbose set correctly
> FAIL: --version
> FAIL: --target option
> FAIL: --host option
> FAIL: --all option
> FAIL: --objdir option
> FAIL: --tool option
> FAIL: --debug option
> FAIL: --D0 option
> Running 
> /cygnus/cygwin-b20/src/dejagnu/testsuite/runtest.all/stats-sub.exp
> ...
> Running 
> /cygnus/cygwin-b20/src/dejagnu/testsuite/runtest.all/stats.exp ...
> FAIL: pass
> FAIL: fail
> FAIL: xpass
> FAIL: xfail
> FAIL: untested
> FAIL: unresolved
> FAIL: unsupported
> 
> 		=== runtest Summary ===
> 
> # of expected passes		30
> # of unexpected failures	22
> couldn't execute "\cygnus\cygwin-b20\src\dejagnu\runtest": no 
> such file or
> directory
> 
> make[1]: *** [check] Error 1
> make: *** [check] Error 2
> bash$ ############### why the backslashes ^^^^^^^^^^ in above 
> pathname????
> bash$ ls /cygnus/cygwin-b20/src/dejagnu/runtest*
> /cygnus/cygwin-b20/src/dejagnu/runtest
> /cygnus/cygwin-b20/src/dejagnu/runtest.exp
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com