X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 5 Dec 2009 13:47:00 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: nasm -- what format does cygwin use? Message-ID: <20091205184700.GD25819@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4B19A77D DOT 3080704 AT tlinx DOT org> <4B19B12F DOT 7030707 AT aol DOT com> <4B19EFEA DOT 7070502 AT gmail DOT com> <4B1A2B6E DOT 90400 AT tlinx DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B1A2B6E.90400@tlinx.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, Dec 05, 2009 at 01:44:14AM -0800, Linda Walsh wrote: >I knew Eric Blakes answer was hopelessly unhelpful and just trying to >wind me up since PE-coff isn't even on the list (though coff is), That's a rather paranoid way of looking at someone's attempts to help you. Eric was, unsurprisingly, right in noting that the binary format for executables on Windows is "PE/COFF". Look it up. cgf -- 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