On Sun, Mar 23, 2008 at 01:48:15PM -0700, Brian Dessent wrote: >Christopher Faylor wrote: >>After poking at this a little, I think it would be better to issue a >>linux-like error message. >> >>In my sandbox, I now have this: >> >>bash-3.2$ ./libtest /cygdrive/s/test/libtest.exe: error while loading >>shared libraries: liba.dll: cannot open shared object file: No such >>file or directory >> >>I haven't done the work to report on missing symbols yet but I think >>that's a much less common error condition. > >Excellent. The wording isn't really that important to me. But I think >what is important is that we don't allow the situation where something >was unable to start and we are totally silent. That leads to confusion >because people start to try to debug or blame the program being run >when in fact the program never saw the light of day in the first place. >It's totally baffling when it happens and you're not aware to look for >it. So even if we can't give the name of the symbol in the case of a >missing import, I think it's still important to say something.
Yes. I really have been meaning to fix this for a long time. It's my fault that cygwin has this bug. I appreciate your point the way to how this could be solved. cgf