Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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, 5 Nov 2004 14:33:17 -0500
From: "Shaffer, Kenneth" <shaffek AT sciatl DOT com>
X-X-Sender: shaffek AT Crunch DOT bcgssbd DOT sciatl DOT com
Reply-To: kenneth DOT shaffer AT sciatl DOT com
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: Using a.out.h from Cygwin with Mingw gcc - was Re: Binary read on textmode mount
In-Reply-To: <6.1.0.6.0.20041105135330.045d43e0@pop.prospeed.net>
Message-ID: <Pine.CYG.4.58.0411051414000.3688@Crunch.bcgssbd.sciatl.com>
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0411051050240 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com> <20041105164033 DOT 9CEF11B3FA AT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0411051309580 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20041105133813 DOT 043d0a98 AT pop DOT prospeed DOT net> <Pine DOT CYG DOT 4 DOT 58 DOT 0411051345520 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20041105135330 DOT 045d43e0 AT pop DOT prospeed DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

I now include a.out.h via #include "/usr/include/a.out.h" and don't use
the -I /usr/include which burned me.  Fortunately, a.out.h has no
#includes within it.

More comments within yours below.

--
Ken Shaffer


On Fri, 5 Nov 2004, Larry Hall wrote:

> But how appropriate it is to use 'a.out.h' or any
> other particular file not included with Mingw in a Mingw compile would be
> a topic for the Mingw list, not this one.

a.out.h defines a structure of the output on disk.  It shouldn't matter
whether compiled on cygwin, linux, solaris, etc.  With that header file, I
could create a program on solaris, ftp an executable created via cygwin to
the solaris machine and use the structure as is (with appropriate swaps as
necessary to account for endianess) provided the sizes of int, long, etc
match. Fortunately since I'm compiling under cygwin with -mno-cygwin
option, my sizes all match as well as endianess.

I suspect that even though I compile with -mno-cygwin, the structure of
the resulting a.out file should conform to the a.out.h include file. This
is a gcc file not specific to cygwin vs. no-cygwin compilations.



     - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.


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