From: Ingmar K. <ing...@gm...> - 2010-01-22 17:52:29
|
On Wed, Jan 13, 2010 at 7:47 PM, Cesar Strauss <ces...@gm...> wrote: > Ingmar Koecher wrote: >> On Tue, Jan 12, 2010 at 6:53 PM, Cesar Strauss <ces...@gm...> wrote: >>> Ingmar Koecher wrote: >>> >>> Does it solve the issue? >> >> Yes, it does indeed! > > Great! > >> I really appreciate all your efforts and the quick resolution, I am >> quite impressed with the quick fix. > > Sure, it was a pleasure. > >> If you need more information to find out the root cause then please >> let me know - I'd be happy to help out. > > Could you try the following: > 1) Install Cygwin > 2) Run the Cygwin Bash Shell > 3) Type > $ cygcheck "/cygdrive/c/devtools/microsoft/vc9/vc/bin/cl.exe" > > Does it crash cygcheck? > > The code for Cygwin cygcheck is actually quite similar to the failing > code in MSYS. Both try to list all the DLLs an executable depends upon, > by decoding the import table embedded in the executable file. If > cygcheck works, I could look into updating the MSYS code to be more like > cygcheck. Hi Cesar, Sorry for dropping the ball here and not getting back to you sooner. Apologies. I've never actually installed Cygwin, and one of our lead developers here isn't exactly encouraging me to install it ... he has concerns about Cygwin interfering with the system and it being difficult to remove completely again? The computer I'd have to do this on is fairly important, so I was wondering if there is another way for me to help with this? Can I try to run the cygcheck utility within Msys? Or are his concerns unfounded and I can just install/uninstall Cygwin? >> Will this fix be incorporated into 1.0.12? >> > > Certainly. Be sure to check the download page from time to time, or > subscribe to the "MSYS Base System" release notifications using the > corresponding orange button on the right side. Perfect. Thanks again for all your help. |