DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=e/C+NC5rJtQy9Tdl1pgBqOHwiuYzl4p/PYUs3dhIjFMtNu7fkijLx
	sz1UVxDDSrnTCLMlHjQRvdcsWarywgtTaH4uip9lqRNqSS884ks1sly5RY4YFzHk
	Onnd4Hrf5+7P3c1YBfN+lO+I3W49tdUyZiiZemVlLH3yNQAe/tWMUg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 4 Apr 2013 17:05:33 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: But it is cygwin related.
Message-ID: <20130404210533.GA6863@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20130404170527.3708@binki> <20130404085538.GE25170@calimero.vinschen.de> <515D78B1.60209@farance.com> <CA+sc5mmQ9rJ85rvDbMTvp_+vCx6CQPava5N3-8yxd9soh6zxQg@mail.gmail.com> <515DA044.6070706@farance.com> <op.wu04ladynxtvbs@localhost.localdomain> <515DC91A.2070706@cs.umass.edu> <515DCD75.6070802@cs.umass.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <515DCD75.6070802@cs.umass.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote:
>On 4/4/2013 2:40 PM, Eliot Moss wrote:
>>It occurred to me to mention to the OP that the mingw package (minimal
>>Gnu for Windows is what I think it stands for) is a lighter weight
>>version of the gcc stuff for Windows.  It does not try to "fake" a
>>Linux environment to the extent that cygwin does, so it is simpler and
>>smaller, as I understand it.  (I am less familiar with mingw than with
>>cygwin.) Still, there may be something there more suited to your needs.
>
>Seeing as I had mingw installed, I built the same little programs with
>it.  Stripped .exe files turned out to be 6144 bytes long.  ldd showed
>a long list of dlls that would be dynamically linked at run time, but
>they are all Windows dlls -- no cygwin or "custom" mingw ones.  So,
>maybe this is more what you meant originally.

If you have to enter MinGW land to perform what the OP wants then that
is a really clear indication that this is off-topic.

I think we've seen an adequate amount of advice for how the OP can
proceed.  There was a suggestion that one could look at the disassembled
output from gcc to see how it does things.  That's probably the best
advice for how to proceed, regardless of the platform.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple