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).
Instead of working , the claim is that the binary actually ends execution and does not show up in the running process list through cygwin (ps -ef). The exectuable in question does call the 'daemon' system call, which may or may not be the source of trouble here. Aside from removing that daemon call and running in the foreground, the only other options I can think of would be to provide the full source package and have the end user compile the package themselves; however, would prefer to only hand out binaries in this case if I can help it. Questions for this list: 1 -- is the migration method used above supported by cygwin? 2 -- any idea what can cause the termination of a program in this manner? 3 -- any other thoughts? Thanks in advance; if there is an FAQ or other thread that covers this please just post a link. --------------------------------------- Scott Thompson / www.fileandstream.com --------------------------------------- -- 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/
