This is the mail archive of the
mailing list for the Cygwin project.
There is no prompt message if shared object file cannot open, when I was running a program.
- From: "kou yu" <ckyoog at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 18 Jan 2007 22:57:58 +0800
- Subject: There is no prompt message if shared object file cannot open, when I was running a program.
Problem: when running a program from bash and the program requires a
lib that is missing, I do not get any error message. Only a exit
status of 128. Can I change this behavior?
I've exhausted those help resources (include FAQ, User's Guide,
mailing list archives and even google). The closer I have found so far
is this thread: "no message or dialog when a DLL is missing", its link
is http://sourceware.org/ml/cygwin/2006-08/msg00895.html. But that
thread disappointed me by ending up with nothing definited. The
posters and replyers seemed to be regardless to this problem.
On Linux, etc., when a shared library is missing at runtime, any
attempt to execute a binary depending on it will get an error like:
/usr/bin/xvidtune: error while loading shared libraries:
libXdmcp.so.6: cannot open shared object file: No such file or
I'm pretty this message is coming directly from (in this case)
ld-linux.so (the "DLL loader" on linux).
If Cygwin is intercepting the equivalent exception on Windows, perhaps
a possible compromise would be for cygwin1.dll to emit such an error
Failing with return code 128 is far less helpful, but printing to
"stderr" (or whatever is eating off that pipe) is much more
script-friendly than a GUI pop-up.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html