Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 24 Oct 2003 19:18:41 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problem with a cygwin App - Broken on a pristine system until I install cygwin, cygwin1.dll doesn't seem to be enough Message-ID: <20031024231841.GA14297@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031024230725 DOT 15635 DOT qmail AT web41205 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031024230725.15635.qmail@web41205.mail.yahoo.com> User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Fri, Oct 24, 2003 at 04:07:25PM -0700, Benjamin Cutler wrote: >I have a program that I originally wrote on Linux, and compiled with >cygwin to make a Windows binary. The problem is that the Windows >binary won't work properly on a system that doesn't have cygwin >installed on it. It seems to not be using fread and fwrite correctly, >or it's having some weird problem with pointers that I can't figure >out. The problem is that as SOON as I install Cygwin onto a system, >the executable works perfectly, even though I don't change anything >directly related to the program itself. > >The program is using SDL, if that makes any difference, and cygwin1.dll >is the latest version in all my test cases. So far on every machine >I've tried it on this has been the case, where it won't work properly >until I've installed cygwin. What might cygwin be installing that >suddenly lets the program work right that I need to be distributing >with my program besides cygwin1.dll? If you are distributing cygwin outside your organization, the other thing you need to include is the source code for your application and for the Cygwin DLL, as per the GPL. Assuming that you know this, you are right in assuming that just copying the cygwin DLL should be enough. You could try just copying the 'strace' program to the system in question and running the program with that to see if you can gather a clue into what is going on. Otherwise the tried and true printf debugging technique is probably your best bet. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.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/