This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Using a.out.h from Cygwin with Mingw gcc - was Re: Binary read on textmode mount
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/