Re: cygwin1.dll possible bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gland Vador on 2/21/2006 2:01 AM: > > While I can understand the fix for the bat files (from the snapshot > diffs), what could have solved the wilcard one ? The improved implementation of readdir(), in concert with improved detection of whether a remote drive supports valid inodes, is probably what fixed your wildcard issue (since wildcarding relies on proper readdir() semantics). There are several patches that have been spread out over several snapshots. Which is why my earlier post in this thread was telling you to use the most recent one (it was just unfortunate that .bat processing happened to be temporarily broken in the meantime). - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD+xzp84KuGfSFAYARArJKAJ45EhwhoCoIdaRenljMfgUXFDL5WQCeNdvT 9CNT/QiuZSYaCWs9x0m33jw= =wh86 -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: cygwin1.dll possible bug
Christopher Faylor wrote:
I've created a Makefile that looks like this:
_module1_DIR=/share/tmp/module1
_module2_DIR=/share/tmp/module2
_module3_DIR=/share/tmp/module3
REQUIRES:=module1 module2 module3
all:
@echo $(foreach z,$(strip $(REQUIRES)),\
$(if $(_$(z)_DIR), $(wildcard $(_$(z)_DIR)/inc),))
And created directories /share/tmp/module{1,2,3} and /share/tmp/module1/inc.
When I run this makefile, /share/tmp/module1/inc is output with both 1.5.19
DLLs and with a snapshot DLL. (/share/tmp is, of course, a remote drive)
So, I've gone the extra mile and tried to come up with a "simple test case"
(patent pending) but apparently I didn't duplicate your scenario adequately
and, so, we need more details about your environment.
I used this "simple test case" (sorry for patent violation) and of
course it worked fine. But in my huge framework it broke.
Anyway the latest snapshot 02-20 solved both (.bat and the wilcard)
problems. Thanks for the fix.
A last question:
While I can understand the fix for the bat files (from the snapshot
diffs), what could have solved the wilcard one ?
Edd.
--
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: cygwin1.dll possible bug
Gland Vador wrote: Eric Blake wrote: What about the newest one? I have tried almost all snapshots available on this page. I went until the oldest in order to track on which snapshot it broke. The newest one doesn't work for me. When I launch a dos batch file in the bash, it tries to execute it line by line and not calling the cmd.exe. Warning: this is a "me too" message. For those of your emotionally sensitive to this type of message, you should probably just skip this message. This is something that I've noticed about the newer snapshots too, running .bat files dies on "@ECHO" command not found (and every other DOS batch file construct). -- 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: cygwin1.dll possible bug
On Mon, Feb 20, 2006 at 04:41:46PM +0100, Gland Vador wrote:
>Eric Blake wrote:
>>>I have found a strange behaviour in the last (cygwin-1.5.19-4)
>>>cygwin1.dll.
>>>
>>>where $(REQUIRES) are ie: module1 module2 module3
>>> $(_module*_DIR) is a folder on a nework drive, inside this folder
>>>I have a optional subfolder named "inc".
>>
>>Try a snapshot. There are some known issues with inode calculations
>>on network drives that have been addressed in snapshots, and which
>>might improve your situation.
>>
>>>This problem appears with the oldest snapshot available at
>>>http://cygwin.com/snapshots/.
>>
>>What about the newest one?
>
>I have tried almost all snapshots available on this page. I went until
>the oldest in order to track on which snapshot it broke.
>
>The newest one doesn't work for me. When I launch a dos batch file in
>the bash, it tries to execute it line by line and not calling the cmd.exe.
You might find reading http://cygwin.com/problems.html instructive. The
above email has a few issues which make it difficult to figure out what
you're trying to report.
I've created a Makefile that looks like this:
_module1_DIR=/share/tmp/module1
_module2_DIR=/share/tmp/module2
_module3_DIR=/share/tmp/module3
REQUIRES:=module1 module2 module3
all:
@echo $(foreach z,$(strip $(REQUIRES)),\
$(if $(_$(z)_DIR), $(wildcard $(_$(z)_DIR)/inc),))
And created directories /share/tmp/module{1,2,3} and /share/tmp/module1/inc.
When I run this makefile, /share/tmp/module1/inc is output with both 1.5.19
DLLs and with a snapshot DLL. (/share/tmp is, of course, a remote drive)
So, I've gone the extra mile and tried to come up with a "simple test case"
(patent pending) but apparently I didn't duplicate your scenario adequately
and, so, we need more details about your environment.
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: cygwin1.dll possible bug
Eric Blake wrote: I have found a strange behaviour in the last (cygwin-1.5.19-4) cygwin1.dll. where $(REQUIRES) are ie: module1 module2 module3 $(_module*_DIR) is a folder on a nework drive, inside this folder I have a optional subfolder named "inc". Try a snapshot. There are some known issues with inode calculations on network drives that have been addressed in snapshots, and which might improve your situation. This problem appears with the oldest snapshot available at http://cygwin.com/snapshots/. What about the newest one? I have tried almost all snapshots available on this page. I went until the oldest in order to track on which snapshot it broke. The newest one doesn't work for me. When I launch a dos batch file in the bash, it tries to execute it line by line and not calling the cmd.exe. -- 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: cygwin1.dll possible bug
> > I have found a strange behaviour in the last (cygwin-1.5.19-4) cygwin1.dll. > > where $(REQUIRES) are ie: module1 module2 module3 >$(_module*_DIR) is a folder on a nework drive, inside this folder > I have a optional subfolder named "inc". Try a snapshot. There are some known issues with inode calculations on network drives that have been addressed in snapshots, and which might improve your situation. > This problem appears with the oldest snapshot available at > http://cygwin.com/snapshots/. What about the newest one? -- Eric Blake -- 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/
