Chuck wrote:
> Folks I could really use some help here. I still cannot get the ls
> command to work reliably. It worked for years and about two weeks ago
> started sputtering. I have completely unstalled all cygwin packages,
> deleted the directories, and reinstalled from scratch. Even just
> inst
Cesar Strauss wrote:
> Chuck wrote:
>> Cesar Strauss wrote:
>>> Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
Chuck wrote:
Cesar Strauss wrote:
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled
On 02/20/2007, Chuck wrote:
I downloaded the source for coreutils and see that in ls.c the same source
code is used to compile ls, dir, and vdir. The strange thing is that dir
and vdir never fail. Only ls does. I haven't figured out how to compile
with the debugging info yet.
make CFLAGS="-g"
Cesar Strauss wrote:
> Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and reinstalled fro
> Can you please check these md5sum's for me?
>
> $ md5sum /bin/ls.exe /usr/bin/ls.exe /usr/bin/dir.exe
> 64e3dc0e3a5ef0eeeaa4f2e9b984844d */bin/ls.exe
> 64e3dc0e3a5ef0eeeaa4f2e9b984844d */usr/bin/ls.exe
> 60a0c7768052ec4306c3e0f680331afa */usr/bin/dir.exe
/bin and /usr/bin are typically the same
Larry Hall (Cygwin) wrote:
> On 02/20/2007, Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>> > Can you send the output of a successful 'ls -l' from within a directory
>> > with one file and then the strace of a failing case of 'ls' within this
>> > directory and a non-failing case of the same to the l
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing t
Chuck wrote:
I think it's actually something to do with the gmane interface that I
post to. I attach the files with Thunderbird but when they post to the
list, they end up being embedded. Apologies but there doesn't seem to be
any way for me to control that.
No, it's working right... your files
Larry Hall (Cygwin) wrote:
> Frodak Baksik wrote:
>> On 2/20/07, Chuck wrote:
>>
>>> Your wish is my command. Attached are two strace output files. The names
>>> should be self-explanatory. Please let me know if you see anything. In
>>> the mean time I'm going to refresh myself on the use of gcc a
Frodak Baksik wrote:
On 2/20/07, Chuck wrote:
Your wish is my command. Attached are two strace output files. The names
should be self-explanatory. Please let me know if you see anything. In
the mean time I'm going to refresh myself on the use of gcc and gdb and
see if I can trace the execution
Frodak Baksik wrote:
> On 2/20/07, Chuck wrote:
>
>> Your wish is my command. Attached are two strace output files. The names
>> should be self-explanatory. Please let me know if you see anything. In
>> the mean time I'm going to refresh myself on the use of gcc and gdb and
>> see if I can trace
On 02/20/2007, Chuck wrote:
Larry Hall (Cygwin) wrote:
> Can you send the output of a successful 'ls -l' from within a directory
> with one file and then the strace of a failing case of 'ls' within this
> directory and a non-failing case of the same to the list?
>
> Does it work fine without 'tt
On 2/20/07, Chuck wrote:
Your wish is my command. Attached are two strace output files. The names
should be self-explanatory. Please let me know if you see anything. In
the mean time I'm going to refresh myself on the use of gcc and gdb and
see if I can trace the execution of ls. Like I said in
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwi
Gary Johnson wrote:
> On 2007-02-20, Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and r
Gary Johnson wrote:
On 2007-02-20, Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled
On 2007-02-20, Chuck wrote:
> Folks I could really use some help here. I still cannot get the ls
> command to work reliably. It worked for years and about two weeks ago
> started sputtering. I have completely unstalled all cygwin packages,
> deleted the directories, and reinstalled from scratch. E
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinst
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and reinstall
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing t
Can you please check these md5sum's for me?
$ md5sum /bin/ls.exe /usr/bin/ls.exe /usr/bin/dir.exe
64e3dc0e3a5ef0eeeaa4f2e9b984844d */bin/ls.exe
64e3dc0e3a5ef0eeeaa4f2e9b984844d */usr/bin/ls.exe
60a0c7768052ec4306c3e0f680331afa */usr/bin/dir.exe
Same.
~$ md5sum /bin/ls.exe /usr/bin/ls.exe /u
Ken Shaffer wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably.
>
> Well, I ran sum -r (I'm running cygwin 1.5.24):
>
>~$ sum -r /bin/ls.exe /bin/cygwin1.dll
>0875696 /bin/ls.exe
>59473 1830 /bin/cygwin1.dll
>
> You might do
Folks I could really use some help here. I still cannot get the ls
command to work reliably.
Well, I ran sum -r (I'm running cygwin 1.5.24):
~$ sum -r /bin/ls.exe /bin/cygwin1.dll
0875696 /bin/ls.exe
59473 1830 /bin/cygwin1.dll
You might do the same and see if there is perhaps a
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing the bare mimimum
25 matches
Mail list logo
