Message-ID: <4B19EFEA.7070502@gmail.com>
Date: Sat, 05 Dec 2009 05:30:18 +0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: nasm -- what format does cygwin use?
References: <4B19A77D.3080704@tlinx.org> <4B19B12F.7030707@aol.com>
In-Reply-To: <4B19B12F.7030707@aol.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Tim Prince wrote:
> Linda Walsh wrote:
>> I am trying to compile a program that use nasm and it thought that
>> gnuwin32 was a format for nasm (don't know if it used to be, but it's
>> not now).
>>
>> Does cygwin use standard linux format now 'elf', or is it using
>> win32?..or
>> something else)?
> If running inside cygwin, you let the cygwin developers make the choice,
> which the binutils as will select automatically (PE-i386?).

  Well, nasm != binutils, so in theory it could do things differently if it chose.

>  nasm might
> be used, I suppose, with mingw, as your comment almost implies, so
> becomes off topic for this list, if you refer to development for
> non-cygwin targets.

  Nope, it has nothing to do with that.  nasm is an assembler.  It generates
relocatable object files.  It has no concept of an ABI, or a system library,
or anything like that.

  Linda, my reading of the "nasm -hf" output suggests you'd want the win32
output format.  If you check the generated .o files it using "objdump -h" you
should see "file format pe-i386", which is right.  After you've got .o files,
you'll still need to link them; hopefully your makefiles will work with
cygwin's LD easily enough.

    cheers,
      DaveK


--
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