Re: Using a.out.h from Cygwin with Mingw gcc - was Re: Binary read on textmode mount

At 02:33 PM 11/5/2004, you wrote: >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. Well I'm glad you were able to find a suitable resolution to your issue, at least this time. -- Lar

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

Using a.out.h from Cygwin with Mingw gcc - was Re: Binary read on textmode mount

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