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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C3E0FAF.2030609@ece.gatech.edu> Date: Thu, 10 Jan 2002 17:03:27 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Robert Collins CC: cygwin AT cygwin DOT com, hschwentner AT yahoo DOT com Subject: Re: Compiling apps to Mingw32 with cygwin References: <047601c19a1f$df92d450$0200a8c0 AT lifelesswks> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Robert Collins wrote: > No. Specify --host. The meaning is clearly documented in the autoconf > documentation. > For clarity: > build - what OS the compilation is running on.. > host - what OS the binaries created should run on. > target - what OS the binaries created should target their output to. Thank you thank you thank you. I have *never* really understood what all those were *really* for -- only what I *thought* they were for. Guess what -- I was wrong. I thought (wrongly) host: what OS the compilation is running on target: what OS the binaries created should run on build: And I never understood what this was for. THANKS for the succinct explanation. I'm going to tattoo this on my arm. (Well, not really, but you get the idea) --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/