Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
There's your problem. You didn't quote properly. Try: $ echo [:upper:] [:lower:] to see what you were really invoking, then try: $ tr '[:upper:]' '[:lower:]' to do what you meant. My guess is that you have a file in your home directory that uses a single letter, so the bracket expansion of bash

Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
One final point. It's considered bad netiquette to commandeer another thread. Replying to another's message and changing the subject is not the way to post to this list. Please just send email to the list directly when you want to start some new topic. It makes following a thread much easier

RE: "replaced while being copied" - was ... RE: Solved partially by findutils 4.3 - RE: "inode changed", ...

2006-09-23 Thread Miller, Raul D
Eric Blake wrote: > Is the network drive running an older version of Samba? I am not an administrator of the systems running the network drives that have this problem (the one I documented is just the one where I most recently encountered this problem) and I do not know. > Also, are you sure it i

Re: "replaced while being copied" - was ... RE: Solved partially by findutils 4.3 - RE: "inode changed", ...

2006-09-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Miller, Raul D on 9/23/2006 7:26 PM: > In the current release of cygwin, I'm still having the problem where > I can't use cp with a network appliance drive. Is the network drive running an older version of Samba? If so, one solution is t

Re: "replaced while being copied" - was ... RE: Solved partially by findutils 4.3 - RE: "inode changed", ...

2006-09-23 Thread Miller, Raul D
In the current release of cygwin, I'm still having the problem where I can't use cp with a network appliance drive. Below is an illustration of my problem, along with the information requested in http://sourceware.org/ml/cygwin/2006-01/msg00818.html $ mkdir /tmp/target $ cp *.html /tmp/target/.

Re: tr command suddenly behaves differently

2006-09-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Logu on 9/23/2006 4:46 AM: > After analysing I found that the tr command did not work correctly. So > the command > $ /usr/bin/tr [:upper:] [:lower:] There's your problem. You didn't quote properly. Try: $ echo [:upper:] [:lower:] to se

Re: tr command suddenly behaves differently

2006-09-23 Thread Larry Hall (Cygwin)
Logu wrote: Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follow

Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follows while loggi

tr command suddenly behaves differently

2006-09-23 Thread Logu
Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follows while logging

Perl's use locale don't work on Cygwin ?

2006-09-23 Thread Sergei Kolodka
Hello, List, Just wonder is whole Perl's "use locale" and "setlocale()" thing doesn't works on Cygwin or I'm just too dumb to find out how to use it ? I've tried everything I could find in perllocale to make it work, without any success. I've even straced same script on Linux and Cygwin and notic

gcc 4.x with libmudflap - is it possible on cygwin?

2006-09-23 Thread Lenives
Good day. I trying to compile gcc (4.1.1 release and 4.2 from snapshot) and it's all ok, but i can't compile it with mudflap library: checking for the name of the symbol used for the entry point... unknown configure: error: none of the known symbol names works make[1]: *** [configure-target-libmud