RE: Error: /bin/bash: bad interpreter: No such file or directory

2004-07-18 Thread Igor Pechtchanski
David, This is very puzzling. Your mounts are present in the registry, but for some reason the Cygwin DLL can't see them. Does your registry have any special permissions? Could you please post the results of cd /cygdrive/c/cygwin/bin ./ls "/proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Cygnus Solu

RE: Error: /bin/bash: bad interpreter: No such file or directory

2004-07-17 Thread Igor Pechtchanski
t; If I run a script with the initial heading of: > > > > #! /bin/bash > > > > I get this error: > > > > bash-2.05b$ ./Test > > bash: ./Test: /bin/bash: bad interpreter: No such file or directory > > bash-2.05b$ > > > > If I change the

Re: Error: /bin/bash: bad interpreter: No such file or directory

2004-07-17 Thread Igor Pechtchanski
ript with the initial heading of: > > #! /bin/bash > > I get this error: > > bash-2.05b$ ./Test > bash: ./Test: /bin/bash: bad interpreter: No such file or directory > bash-2.05b$ > > If I change the initial heading in my script to this > > #! /cygwin/bin/bash > &

Error: /bin/bash: bad interpreter: No such file or directory

2004-07-17 Thread David J Jones
Igor took a guess yesterday and I have to agree from what little I seem to remember of unix, my mounts are screwed up.The problem is this.. If I run a script with the initial heading of: #! /bin/bash I get this error: bash-2.05b$ ./Test bash: ./Test: /bin/bash: bad interpreter: No such file or

Re: bad interpreter

2004-07-16 Thread Igor Pechtchanski
tial heading of: > > #! /bin/bash > > I get this error: > > bash-2.05b$ ./Test > bash: ./Test: /bin/bash: bad interpreter: No such file or directory > bash-2.05b$ > > If I change the initial heading in my script to this > > #! /cygwin/bin/bash > > It works. >

bad interpreter

2004-07-16 Thread David J Jones
: ./Test: /bin/bash: bad interpreter: No such file or directory bash-2.05b$ If I change the initial heading in my script to this #! /cygwin/bin/bash It works. Can someone please tell me what I have set up incorrectly? Thank you, hopefully I have given enough examples this time and feel this is a

Re: bash bad interpreter - a new twist!

2004-03-30 Thread Tom Rodman
Mar 29 0j tty0 5752 /tmp > c7mkes109 adm_tsr > /adm/bin/sys/s/find_ls2 >/dev/null || echo oops > 13:20:19 Mon Mar 29 0j tty0 5752 /tmp > c7mkes109 adm_tsr > /adm/bin/sys/s/find_ls2 >/dev/null || echo oops > 13:20:42 Mon Mar 29 0j tty0 5752 /tmp > c7mkes109 adm_tsr > /adm/b

Re: bash bad interpreter - a new twist!

2004-03-27 Thread Reini Urban
Igor Pechtchanski schrieb: FWIW, the following always works on my system: #!/usr/local/bin/wrap /cygdrive/c/ActivePerl/bin/perl use English; print "Testing: $PERL_VERSION on $OSNAME\n"; well, for me this looks better: (at least needed for 5.006001) #!/usr/local/bin/wrap /cygdrive/c/ActivePerl/bin

RE: bash bad interpreter - a new twist!

2004-03-26 Thread Igor Pechtchanski
Dave, FWIW, the following always works on my system: #!/usr/local/bin/wrap /cygdrive/c/ActivePerl/bin/perl use English; print "Testing: $PERL_VERSION on $OSNAME\n"; where /usr/local/bin/wrap is #!/bin/sh pname="$1" fname="`cygpath -wi "$2"`" shift 2 && exec "$pname" "$fname" "$@" This will wor

RE: bash bad interpreter - a new twist!

2004-03-26 Thread david mallon
Thanks Tom, I believe you are right. I noticed yesterday that if the interpreter was a binary the problem went away, so I rewrote my script as a C program and everything is stable again. -- dave From: [EMAIL PROTECTED] (Tom Rodman) >I'm using cygwin (september 2003 build) and ActiveState perl.

Re: bash bad interpreter - a new twist!

2004-03-25 Thread Christopher Faylor
On Thu, Mar 25, 2004 at 11:02:24PM -0600, Tom Rodman wrote: >>I'm using cygwin (september 2003 build) and ActiveState perl. To connect >>ActiveState into cygwin I use a proxy /usr/local/bin/perl bourne shell >>script that essentially transalates the paths (cygpath -w) and delegates to >>the Act

bash bad interpreter - a new twist!

2004-03-25 Thread Tom Rodman
>I'm using cygwin (september 2003 build) and ActiveState perl. To connect >ActiveState into cygwin I use a proxy /usr/local/bin/perl bourne shell >script that essentially transalates the paths (cygpath -w) and delegates to >the ActiveState perl.exe binary. Given the following foobar script: >

bash bad interpreter - a new twist!

2004-03-24 Thread david mallon
Hi I seem to have an intermittant problem with bash that I cannot work out---in which a script usually works fine, but sometimes in the same session attempting to run it gives the bash message: bad interpreter. I'm using cygwin (september 2003 build) and ActiveState perl. To co

Re: Bad interpreter?

2003-11-07 Thread Brian Ford
On Fri, 7 Nov 2003, Shaffer, Kenneth wrote: > If the first line of scripts is #!bash.exe, I get back a bad interpreter > message. > Did you try it without the .exe? I think this works in Cygwin, but is, AFAIK, unportable. -- Brian Ford Senior Realtime Software Engineer VITAL

Bad interpreter?

2003-11-07 Thread Shaffer, Kenneth
If the first line of scripts is #!bash.exe, I get back a bad interpreter message. Is there a way that I can get the above line to correctly find bash? I thought if the full path wasn't specified, that PATH would be used to find it. (I've tried copying bash.exe to / and c: and get the

Re: {par script path}: {chld script path}: /bin/bash: bad interpreter: Permission denied

2003-03-07 Thread nicebounce
gt; >> >> Here's an error message example: >> >> /adm/bin/ccm_build_scripts/run_large_nb.sh: >> s:/adm/bin/ccm_build_scripts/run_nb.sh: /bin/bash: bad interpreter: Permission denied >^^ >One thing that comes to m

{par script path}: {chld script path}: /bin/bash: bad interpreter: Permission denied

2003-03-06 Thread nicebounce
Here's an error message example: /adm/bin/ccm_build_scripts/run_large_nb.sh: s:/adm/bin/ccm_build_scripts/run_nb.sh: /bin/bash: bad interpreter: Permission denied "run_nb.sh" aborts immediately, not executing a single line as far as I know. Misc info: $ p

RE: New install, script execution, bad interpreter

2003-02-11 Thread [EMAIL PROTECTED]
n mapoles [EMAIL PROTECTED] Date: Tue, 11 Feb 2003 08:41:14 -0800 (PST) To: [EMAIL PROTECTED] Subject: New install, script execution, bad interpreter I recently re-installed cygwin. The install went well but I have one problem concerning executing scripts. I usually use the perl that comes with

Re: New install, script execution, bad interpreter

2003-02-11 Thread Ronald Landheer-Cieslak
On Tue, 11 Feb 2003, john mapoles wrote: > bash: ./testAS: /usr/local/bin/perl: bad interpreter: > No such file or directory Look whether /usr/local/bin/perl exists - I bet it doesn't (because that's what it says: /usr/local/bin/perl: (...) No such file or directory > I&#

New install, script execution, bad interpreter

2003-02-11 Thread john mapoles
get (using the script testAS): bash: ./testAS: /usr/local/bin/perl: bad interpreter: No such file or directory I've check a number of things. The scripts are all unix, dos2unix has no effect. Running a simple bash script works fine, althought ?? if I move the script to my bin director