Scott Thompson wrote:
Hi all. I'm trying to do the following and running into some
problems:
1. Install cygwin on a host computer (works).
2. Compile a set of binaries and dll's using gcc/make (works).
3. Sanity check that the binaries actually run and execute
properly (works).
4. Zip the compiled binaries and dlls, then unzip on a different
cygwin install (works).
5. Run the compiled binaries (some of which use the dll's) (does
not work on some systems).
What does 'cygcheck <foo>' on the target system in the context in which
<foo> should be run say, where <foo> is your executable? If this doesn't
point at a missing DLL, you can do 'echo $?' after running the executable
in question and get some insight as to why it's failing. Also,
it's worthwhile looking at the output of 'cygcheck -s -r -v' on both
the original and target system to look for important differences.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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/
