Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-07 Thread Konstantinos Makrodimitris
permissions to the executable and re-'make' the program_exe was build finally. Best, Konstantinos From: Igor Pechtchanski <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: Konstantinos Makrodimitris <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: 1.3.20-1 CYGWIN ;

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-06 Thread Corinna Vinschen
Randal, Igor, On Wed, Mar 05, 2003 at 08:15:09AM -0800, Randall R Schulz wrote: > If you're asking me, I'd say it's probably a good idea. It would > probably help keep lunkheads like me from doing stupid things like > copying tcsh to csh... I've uploaded a new release with a postinstall script.

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Randall R Schulz
Corinna, At 08:04 2003-03-05, Corinna Vinschen wrote: ... Would you think it makes sense to create a csh symlink to tcsh.exe in the package? Seems to be common on Linux at least. If you're asking me, I'd say it's probably a good idea. It would probably help keep lunkheads like me from doing stu

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Igor Pechtchanski
On Wed, 5 Mar 2003, Corinna Vinschen wrote: > > At 01:47 2003-03-05, Corinna Vinschen wrote: > > >P.S.: No, it doesn't. Create your own symlink or change the first > > >script line to `#!/bin/tcsh' > > Would you think it makes sense to create a csh symlink to tcsh.exe in > the package? Seems to

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Corinna Vinschen
On Wed, Mar 05, 2003 at 07:38:17AM -0800, Randall R Schulz wrote: > At 01:47 2003-03-05, Corinna Vinschen wrote: > >P.S.: No, it doesn't. Create your own symlink or change the first > >script line to `#!/bin/tcsh' > > Corinna, Igor, > > I wonder what this means: > > % ll /bin/{t,}csh.exe > -rwx

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Randall R Schulz
At 01:47 2003-03-05, Corinna Vinschen wrote: On Tue, Mar 04, 2003 at 03:20:52PM -0500, Igor Pechtchanski wrote: > Konstantinos, > > First off, the script is written for csh. Why would you expect sh or bash > to be able to interpret it? These shells use different syntax. > > The original script fa

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Igor Pechtchanski
On Wed, 5 Mar 2003, Corinna Vinschen wrote: > On Tue, Mar 04, [EMAIL PROTECTED]:20:52PM -0500, Igor Pechtchanski wrote: > > Konstantinos, > > > > First off, the script is written for csh. Why would you expect sh or bash > > to be able to interpret it? These shells use different syntax. > > > > T

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-05 Thread Corinna Vinschen
On Tue, Mar 04, 2003 at 03:20:52PM -0500, Igor Pechtchanski wrote: > Konstantinos, > > First off, the script is written for csh. Why would you expect sh or bash > to be able to interpret it? These shells use different syntax. > > The original script failed because you don't have csh installed.

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-04 Thread Max Bowsher
Konstantinos Makrodimitris wrote: > I am trying to run a configure file > ./config Cygwin-i686 > The file “config” is like: > _ > #!/bin/csh -f > Changing the first line of the “config” in sh mode > #!/bin/sh –f You do realize

Re: 1.3.20-1 CYGWIN ; csh,bash and ./config

2003-03-04 Thread Igor Pechtchanski
Konstantinos, First off, the script is written for csh. Why would you expect sh or bash to be able to interpret it? These shells use different syntax. The original script failed because you don't have csh installed. Cygwin does not have a "csh" package, but it does have a "tcsh" package that m