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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20041105135330.045d43e0@pop.prospeed.net>
X-Sender: 
Date: Fri, 05 Nov 2004 14:07:31 -0500
To: kenneth DOT shaffer AT sciatl DOT com, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Using a.out.h from Cygwin with Mingw gcc - was Re: Binary read on textmode mount
In-Reply-To: <Pine.CYG.4.58.0411051345520.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:52 PM 11/5/2004, you wrote:
>Now, now, it seems perfectly legitimate to write a windows program which
>can access files created by gcc to run under cygwin.  


I'm not sure what you're saying here actually says what you mean so I'm
not going to agree, disagree, or otherwise.  Anyway, I don't think clarity
there is critical to the thread.


>The structure of the
>a.out shouldn't depend on whether I'm compiling under windows, cygwin,
>linux, solaris, whatever.  


While I won't disagree with this as a general assertion, I cannot confirm
or deny that 'a.out.h' works for Mingw (I haven't tried it).  Mingw is 
essentially the version of the compiler you're using when you invoke 'gcc' 
with '-mno-cygwin'.  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.  I will point out, however, that 
even if using 'a.out.h' from the Cygwin includes works in this case, it's 
not something that's guaranteed to work in all cases.  By including the 
Cygwin include path to get this file, you pulled in many other files which 
pretty much guarantees you're going to have some problem, as you found out.  
So it *may* work to compile your program with 'gcc -mno-cygwin' if you 
copy 'a.out.h' somewhere that you can access it for your purposes.  This 
isn't a recipe for success for any file you need in Mingw that is in Cygwin.  
And pointing to the Cygwin include directory for your compile is far from a 
solution (as I expect you realize now).


>I just need the a.out.h file for the system on
>which it was created.  (Time to change the subject line, I guess)


OK, done.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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