Re: Make Parallel Jobs

2007-01-29 Thread Christopher Faylor
On Mon, Jan 29, 2007 at 02:39:16AM +, Bill Harding wrote:
>P.S. I am using make 3.80 on Windows XP.

The current cygwin version of make is 3.81.  We no longer support 3.80.

cgf

--
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/



Re: Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute a program

2007-01-29 Thread Glenn Serre

Good morning,

Christian Jullien wrote:

I installed a new version of cygwin yesterday, and find that bash starts

up and
builtins seem to execute, but when I try the first command, cygwin exits


This is not related to the new bash version but related to new cygwin
1.5.24-1.

As soon I installed this new version alone without bash or any other cygwin
package, my Windows X64 stopped to work for any cygwin command even if I run
gcc from cmd.exe. Reverting to 1.5.23 let my system work again.


[...]

Reverting to cygwin 1.5.23 worked.

Is someone working to fix this, or is this an opportunity for me to submit a 
patch?


Thanks!
--Glenn S.

--
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/



xp64 fails with latest download

2007-01-29 Thread bob sandefur
Hi

I did I did my Monday morning update to my Dell running XP 64. When I click
on the Cygwin icon now, the screen flashes and it quits.

I haven't tried this on the 32-bit version.

Questions:
Anyone else experiencing this same issue?
How do I rollback to the prior release?  (I have not searched the mail list
for this yet/)

Thanx


Robert (Bob) L. Sandefur PE
Senior Geostatistician / Reserve Analyst
CAM 200 Union Suite 430 Lakewood, Co
80228
[EMAIL PROTECTED]



--
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/



Cygwin can't open new process on Vista ; other features partial as well

2007-01-29 Thread Katy

Hi all,
I've got Vista EE build 6.00 installed . Cygwin -both the latest build
(cygwin-1.5.24-1) and earlier 1.3 are installed successfully but when
trying to run anything that should create a new process results in
exception related to "fork" ...

Any ideas on how to solve this one ??

Thanks

--
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/



Re: Cygwin can't open new process on Vista ; other features partial as well

2007-01-29 Thread Larry Hall (Cygwin)

Katy wrote:

Hi all,
I've got Vista EE build 6.00 installed . Cygwin -both the latest build
(cygwin-1.5.24-1) and earlier 1.3 are installed successfully but when
trying to run anything that should create a new process results in
exception related to "fork" ...

Any ideas on how to solve this one ??





Where did you find 1.3?  That's years out-of-date and isn't supported.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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/



trouble with bash / if in recent release / update ?

2007-01-29 Thread Tim Hanson
hi, a colleague and i recently tried upgrading an existing cygwin and found that
basic bash script features broke. he later went back to a working copy, tested
and discovered that the features worked, upgraded again and confirmed that they
were broken again. i've searched for hints that others have had this problem and
haven't found any. the symptoms are pretty easy to test.

in an interactive bash shell one can conform that these two if statements work:

  if [[ -z "17" ]]; then  echo "ja"; else   echo "ne"; fi
  ne

  if [[ -z "" ]]; then  echo "ja"; else   echo "ne"; fi
  ja

if one then builds a bash script consisting only of #!/usr/bin/bash
and this if statement (broken into separate lines) it fails along these lines:

$ test.bash
: command not test.bash: line 9:
/usr/local/bin/test.bash: line 10: syntax error in conditional 
expression
'usr/local/bin/test.bash: line 10: syntax error near `]]
'usr/local/bin/test.bash: line 10: `if [[ -z "$1" ]]

does this ring a bell for anyone?

i'd be grateful for pointers. (or advice on how to provide more clues.)

cheers,

Tim


--
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/



Re: trouble with bash / if in recent release / update ?

2007-01-29 Thread Larry Hall (Cygwin)

Tim Hanson wrote:

hi, a colleague and i recently tried upgrading an existing cygwin and found that
basic bash script features broke. he later went back to a working copy, tested
and discovered that the features worked, upgraded again and confirmed that they
were broken again. i've searched for hints that others have had this problem and
haven't found any. the symptoms are pretty easy to test.

in an interactive bash shell one can conform that these two if statements work:

  if [[ -z "17" ]]; then  echo "ja"; else   echo "ne"; fi
  ne

  if [[ -z "" ]]; then  echo "ja"; else   echo "ne"; fi
  ja

if one then builds a bash script consisting only of #!/usr/bin/bash
and this if statement (broken into separate lines) it fails along these lines:

$ test.bash
: command not test.bash: line 9:
/usr/local/bin/test.bash: line 10: syntax error in conditional 
expression
'usr/local/bin/test.bash: line 10: syntax error near `]]
'usr/local/bin/test.bash: line 10: `if [[ -z "$1" ]]

does this ring a bell for anyone?

i'd be grateful for pointers. (or advice on how to provide more clues.)


Your line-endings are CRNLs.  The best thing to do is to run d2u on the
scripts in question.  Read any recent Cygwin bash announcements for other
options to resolve this situation and further details.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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/



plans for PIL installer?

2007-01-29 Thread Mark Wendell

Just curious to know if anyone is planning on creating a python
imaging library install for cygwin setup...

I found an old thread where someone discusses the steps he went
through to do this a while ago (
http://www.cygwin.com/ml/cygwin/2003-06/msg01121.html ), but it seems
like these are some pretty involved and error-prone procedures for
casual users to follow.

thanks
Mark


--
--
Mark Wendell
[EMAIL PROTECTED]

--
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/



RE: xp64 fails with latest download

2007-01-29 Thread bob sandefur
I copied a version 3.2.9(10) from an un-updated machine and it works now.
In the future I will copy my working cygwin to cygwincya in case I need it
back.


Bob

-Original Message-
From: bob sandefur [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 29, 2007 08:36
To: cygwin@cygwin.com
Subject: xp64 fails with latest download

Hi

I did I did my Monday morning update to my Dell running XP 64. When I click
on the Cygwin icon now, the screen flashes and it quits.

I haven't tried this on the 32-bit version.

Questions:
Anyone else experiencing this same issue?
How do I rollback to the prior release?  (I have not searched the mail list
for this yet/)

Thanx


Robert (Bob) L. Sandefur PE
Senior Geostatistician / Reserve Analyst
CAM 200 Union Suite 430 Lakewood, Co
80228
[EMAIL PROTECTED]




--
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/



Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2

2007-01-29 Thread Steve Rowley
Thanks for the suggestions so far.

However, after trying all the suggestions, I'm still unable to launch
cron.  Is there anything further to try before looking for
alternatives to cron?

>Date: Thu, 25 Jan 2007 15:05:01 -0500
>From: Steve Rowley <[EMAIL PROTECTED]>
>
>>Date: Thu, 25 Jan 2007 19:55:35 +
>>From: "DePriest, Jason R." <[EMAIL PROTECTED]>
>>
>>mkgroup_l_d:S-1-5-32-545:10545:
>>
>>A Google search for
>>GID 10545
>>implies that this is 'Domain Users'.
>>
>>Not that it should make a big difference, but you might want to edit
>>your /etc/group and change
>>mkgroup_l_d:S-1-5-32-545:10545:
>>to
>>Domain Users:S-1-5-32-545:10545:
>>or however you prefer
>>dusers:S-1-5-32-545:10545:
>>domain_users:S-1-5-32-545:10545:
>>
>>Just something other than mkgroup_l_d
>
>Ok.  I'd previously tried just taking that line out of /etc/group
>altogether.  Now I'll add it back in, as you suggested:
>
>  >$ cat /etc/group
>  >SYSTEM:S-1-5-18:18:
>  >None:S-1-5-21-473916646-3257906905-3362627345-513:513:
>  >Administrators:S-1-5-32-544:544:
>  >Backup Operators:S-1-5-32-551:551:
>  >Guests:S-1-5-32-546:546:
>  >Network Configuration Operators:S-1-5-32-556:556:
>  >Power Users:S-1-5-32-547:547:
>  >Remote Desktop Users:S-1-5-32-555:555:
>  >Replicator:S-1-5-32-552:552:
>  >Users:S-1-5-32-545:545:
>  >Debugger Users:S-1-5-21-473916646-3257906905-3362627345-1004:1004:
>  >HelpServicesGroup:S-1-5-21-473916646-3257906905-3362627345-1001:1001:
>  >Domain Users:S-1-5-32-545:10545:
>
>But cron-config still stalls out in the same place.

-- 
Steve Rowley <[EMAIL PROTECTED]> http://alum.mit.edu/www/sgr/ Skype: sgr000
It is very dark & after 2000.  If you continue, you are likely to be eaten by a 
bleen.



--
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/



Re: plans for PIL installer?

2007-01-29 Thread Larry Hall (Cygwin)

Mark Wendell wrote:

Just curious to know if anyone is planning on creating a python
imaging library install for cygwin setup...

I found an old thread where someone discusses the steps he went
through to do this a while ago (
http://www.cygwin.com/ml/cygwin/2003-06/msg01121.html ), but it seems
like these are some pretty involved and error-prone procedures for
casual users to follow.



I don't recall anybody posting an ITP for this, though I may have
forgotten it in the last 3+ years. ;-)  If you or anyone else is
interested, I recommend reading:

  

It has all the details of the process to get a new package included in
the Cygwin distribution.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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/



/etc/bash_completion & svn/svk completion

2007-01-29 Thread Jared Silva

The command "svn update DIR" results in "svn update DIR " instead
of "svn update DIR/".  The same goes for svk.  The space being added
instead of a slash is annoying.  Does anyone know what causes this and
how to fix it?

--
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/



Re: How to resolve hiccups by patch program?

2007-01-29 Thread Markus Elfring
How are the chances to fix this issue without to repeat the desired 
updates by manual edits with vim or emacs?


Regards,
Markus

--
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/



bug with cat and backticks? (was: bug with built-in ...)

2007-01-29 Thread Norton Allen



According to Norton Allen on 1/28/2007 1:08 PM:

I'm wondering if the problem I am seeing is from the same source. I find
that 'apachectl stop' no longer works since a recent cygwin update. I
can see that the PIDFILE is being written with a \r\n line ending.
'apachectl stop' then reads the file with

   PID=`cat $PIDFILE`


cat is not a bash builtin, so no this is not the same problem.  Are you
running a script with CRLF line endings on a binary mount?  If so, read
the announcment, and use d2u on your script.
http://cygwin.com/ml/cygwin-announce/2007-01/msg00015.html




No, this is a text mount:

Cygwin> mount
[cut]
d:\Data on /Data type user (textmode)
[cut]
Cygwin> cd /Data
Cygwin> echo hello >test.txt
Cygwin> xxd test.txt
000: 6865 6c6c 6f0d 0ahello..
Cygwin> foo=`cat test.txt`
Cygwin> echo "'$foo'"
'hello
Cygwin>

Note the trailing quote is missing because of in intervening CR. It 
seems that the discussion of confusion about whether a program should be 
in text mode or binary mode when pipes are involved would still be 
relevant here.


-Norton


--
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/



Re: /etc/bash_completion & svn/svk completion

2007-01-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Jared Silva on 1/29/2007 1:14 PM:
> The command "svn update DIR" results in "svn update DIR " instead
> of "svn update DIR/".  The same goes for svk.  The space being added
> instead of a slash is annoying.  Does anyone know what causes this and
> how to fix it?

This would be an upstream bug; I'm cc'ing the upstream maintainer to see
if we can get a response.

You can also try debugging it yourself.  At the command line, turn on the
options 'set -xv', then when you hit TAB, you will see what bash is trying
to do during the tab completion.  I don't personally use svn, so I'm not
the best candidate to help you fix the _svn() helper function used when
tab-completing svn, but compgen is loaded with options to try to help
decipher when to use directories with or without a trailing slash.

- --
Don't work too hard, make some time for fun as well!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin bash_completion maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvsEx84KuGfSFAYARAliAAJ0ZeIteaG51LK0b9ybWt6PoWqK6bgCgkUrm
LD1OThXLiqZdGFcYoNmSmgs=
=JT+X
-END PGP SIGNATURE-

--
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/



Re: bug with cat and backticks? (was: bug with built-in ...)

2007-01-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Norton Allen on 1/29/2007 8:00 PM:
>>>
>>>PID=`cat $PIDFILE`
>>
>> No, this is a text mount:

That's the answer.  You are creating PIDFILE with \r\n line endings, but
cat always reads in binary mode.

Try PID=`cat $PIDFILE | d2u` instead.  Or try using the igncr shell option.

- --
Don't work too hard, make some time for fun as well!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvsHC84KuGfSFAYARAthSAJ4ueC7VGD3iZR33FVoVcb7YqYr05QCgrIGA
5nGWqQDb23jeRsrPO/12mT8=
=cund
-END PGP SIGNATURE-

--
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/



Re: Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute a program

2007-01-29 Thread jm . challier
Good morning.

I'm quite happy to find this thread - I thought I was the one who messed things
up... ;^)

I experience exactly the same problem : XP64, recently updated cygwin -> bash
exits with code 128 when trying to execute anything (except builtins, of
course). Same thing for gcc (tried from emacs too).

To answer a question that was asked in the "xp64 fails with latest download"
thread (which deals with the same problem) : I have only one cygwin1.dll file on
the system.

> Reverting to cygwin 1.5.23 worked.
> Is someone working to fix this, or is this an opportunity for me to submit a
patch?

If you have a patch working, pease go ahead. Reverting to 1.5.23 is not a patch,
but a workaround :-) Meanwhile, I'll stick with my good'ol'32-bit laptop...

By the way, in case it's a version consistency problem, what mirror are you
using ? I'm using ftp://mirror.cict.fr/ - nearest from home.

TIA

JMC



--
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/



Re: Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute a program

2007-01-29 Thread Glenn Serre

Good evening,

[EMAIL PROTECTED] wrote:

Good morning.

I'm quite happy to find this thread - I thought I was the one who messed things
up... ;^)

I experience exactly the same problem : XP64, recently updated cygwin -> bash
exits with code 128 when trying to execute anything (except builtins, of
course). Same thing for gcc (tried from emacs too).

To answer a question that was asked in the "xp64 fails with latest download"
thread (which deals with the same problem) : I have only one cygwin1.dll file on
the system.


Reverting to cygwin 1.5.23 worked.
Is someone working to fix this, or is this an opportunity for me to submit a

patch?

If you have a patch working, pease go ahead. Reverting to 1.5.23 is not a patch,
but a workaround :-) Meanwhile, I'll stick with my good'ol'32-bit laptop...


I have no working patch, I was going to use this problem as an opportunity for 
my first attempt to build and debug the cygwin DLL (while maybe even charging a 
client for it) but it looked to me as if it may already be being addressed. 
Looking again, I see that this might not be that case, so I'll see what I can do 
(no promises, as I'm a newbie at cygwin development).




By the way, in case it's a version consistency problem, what mirror are you
using ? I'm using ftp://mirror.cict.fr/ - nearest from home.

[...]

http://cygwin.elite-systems.org.

--Glenn S.


--
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/



Re: trouble with bash / if in recent release / update ?

2007-01-29 Thread Daniel Brockman


Tim Hanson  faz.de> writes:

> 
> hi, a colleague and i recently tried upgrading an existing cygwin and found 
that
> basic bash script features broke. 
> [...]
> 
> does this ring a bell for anyone?
> 
> i'd be grateful for pointers. (or advice on how to provide more clues.)
> 
> cheers,
> 
> Tim
> 
> 
You aren't alone, Tim.

I have same problem. I updated last night. My sh (bourne shell) scripts didn't 
work this morning. I diff the bash.exe and sh.exe binaries and they are the 
same. I tried updating from a differnt mirror, but that didn't fix the problem.

Workaround: I'm using zsh instead of sh .

Back to the bugs ... `echo' command seems to work backwards! 
In a script...

  echo foo bar

produces output ...

  bar foo

A blank line in the script file produces err msg 

: command not found

I can't figure out a way to make the new version of sh.exe work. Imho, it's 
broken.



db





--
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/



Re: Compile-time detection of EOL translation mode (CLISP)

2007-01-29 Thread Reini Urban

Reini Urban schrieb:

Aaron Brown schrieb:

Reini Urban wrote:


Confirmed.
Bug patched at 
http://sourceforge.net/tracker/index.php?func=detail&aid=1633552&group_id=1355&atid=101355 



It's been moved to  with the
following comment from Sam Steingold:


This patch does not seem right.
on linux O_BINARY==0 and I see no reason to default line
termination to :DOS there.
I am rejecting it pending your convincing me that I am
wrong here.


To be honest, it didn't seem quite right to me either, but I
figured that was down to me not knowing the ins and outs of
how Cygwin handles text modes.

The original logic was:


#if defined(WIN32) || (defined(UNIX) && (O_BINARY != 0))
 pushSTACK(S(Kdos));   /* :line-terminator */
#else
 pushSTACK(S(Kunix));  /* :line-terminator */


which translates to "if O_BINARY is something other than 0,
then this unix must differentiate between text and binary
streams, so assume that text streams use dos EOLs".  That
makes sense, except that O_BINARY is nonzero even on (for
instance) my Cygwin installation, where I selected unix EOLs
as the default with setup.exe.

The patch changes the condition to:


#if defined(WIN32) || (defined(UNIX) && (O_BINARY == 0))


which, as Sam pointed out, would make most unixes (on which
O_BINARY is 0) use dos EOLs.


I tought the UNIX O_BINARY logic was only for CYGWIN and wondered what 
other UNIX that could be.

Ok, so we'll have to use
#if defined(WIN32) || \
  (defined(UNIX) && (O_BINARY != 0) && !defined(__CYGWIN__))

or make the call slower by doing a dynamic textmount check.
But I really don't want to do that.


This issue was solved here
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=1633552&group_id=1355
by adding a documentation chapter to clisp's next version:
  http://clisp.podval.org/impnotes/encoding.html#line-term-default

See also:
  http://clisp.cons.org/impnotes/clhs-newline.html
  http://www.unicode.org/reports/tr13/tr13-9.html

The original problem is best solved by a
  (setq *default-file-encoding* :unix)
in ~/.clisprc.lisp
--
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/

--
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/



Re: trouble with bash / if in recent release / update ?

2007-01-29 Thread Daniel Brockman
Tim Hanson  faz.de> writes:

> [...]
> i'd be grateful for pointers. (or advice on how to provide more clues.)
> 
> cheers,
> 
> Tim
> 
> 

I found this in the archive...

From: Eric Blake  byu.net>
Subject: [ANNOUNCEMENT] Updated: bash-3.2.9-11
Newsgroups: gmane.os.cygwin
Date: 2007-01-27 16:30:22 GMT (2 days, 14 hours and 41 minutes ago)
[...]
4a. For a single affected script, add this line just after the she-bang:
 (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
4b. For a single script, invoke bash explicitly with the shopt, as in
'bash -o igncr ./myscript' rather than the simpler './myscript'.
[...]


The value of the latest enhancement isn't immediately apparent to me.

db




--
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/



Re: Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute a program

2007-01-29 Thread Daniel Brockman
Glenn Serre  spiresoftware.com> writes:

> 
> Good morning,
> 
> I installed a new version of cygwin yesterday, and find that bash starts up 
and
> builtins seem to execute, but when I try the first command, cygwin exits
> silently.  
> [...]
> Any hints? Should I wait until I can try 3.2.9-11 from a mirror?
> 
> Thanks for your attention,
> 
> --Glenn S.
> 
> 
> [...]

Consider content of a message that appeared a little earlier:


From: Eric Blake  byu.net>
Subject: [ANNOUNCEMENT] Updated: bash-3.2.9-11
Newsgroups: gmane.os.cygwin
Date: 2007-01-27 16:30:22 GMT (2 days, 14 hours and 41 minutes ago)
[...]
4a. For a single affected script, add this line just after the she-bang:
 (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
4b. For a single script, invoke bash explicitly with the shopt, as in
'bash -o igncr ./myscript' rather than the simpler './myscript'.
[...]


db


--
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/



Re: trouble with bash / if in recent release / update ?

2007-01-29 Thread Tim Hanson
Larry Hall (Cygwin  cygwin.com> writes:

> Your line-endings are CRNLs.  The best thing to do is to run d2u on the
> scripts in question.  Read any recent Cygwin bash announcements for other
> options to resolve this situation and further details.

thanks. much appreciated.

Tim Hanson





--
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/