Mail Archives: cygwin/2004/11/05/14:11:00
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/
- Raw text -