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
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
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
On Fri, Nov 05, 2004 at 01:52:34PM -0500, Shaffer, Kenneth wrote:
>Now, now, it seems perfectly legitimate to write a windows program
>which can access files created by gcc to run under cygwin.
Of course, if you know *exactly* what you're doing, you can get away
with all sorts of stuff in any walk
> -Original Message-
> From: cygwin-owner On Behalf Of Shaffer, Kenneth
> Sent: 05 November 2004 18:53
> To: Cygwin List
> Subject: Re: Binary read on textmode mount
>
> Now, now, it seems perfectly legitimate to write a windows
> program which
> can access
Now, now, it seems perfectly legitimate to write a windows program which
can access files created by gcc to run under cygwin. The structure of the
a.out shouldn't depend on whether I'm compiling under windows, cygwin,
linux, solaris, whatever. I just need the a.out.h file for the system on
which
At 01:11 PM 11/5/2004, you wrote:
>I need a.out.h apparently not available with the -mno-cygwin compile
>option.
And now you know why. ;-)
>--
>Ken Shaffer
>
>
>On Fri, 5 Nov 2004, Christopher Faylor wrote:
>
>> You are really asking for trouble. The fact that you needed to go out
>> of your w
I need a.out.h apparently not available with the -mno-cygwin compile
option.
--
Ken Shaffer
On Fri, 5 Nov 2004, Christopher Faylor wrote:
> You are really asking for trouble. The fact that you needed to go out
> of your way to include a cygwin header file in a windows program should
> be a clu
On Fri, Nov 05, 2004 at 01:00:03PM -0500, Shaffer, Kenneth wrote:
>I see the problem now... O_BINARY is 0x8000 on mingw and 0x1 in
>cygwin and I needed a header file from cygwin and use the -I option
>which brought in the wrong fcntl.h Sigh.
You are really asking for trouble. The fact
I see the problem now... O_BINARY is 0x8000 on mingw and 0x1 in
cygwin and I needed a header file from cygwin and use the -I option which
brought in the wrong fcntl.h Sigh.
--
Ken Shaffer
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any att
On Fri, Nov 05, 2004 at 11:48:31AM -0500, Shaffer, Kenneth wrote:
>I'm using the cygwin development environment and so thought this was the
>correct place to post a problem. But you make a good point, so I copied
>the file to /tmp, mounted as binary, and got the same results.
You are running a win
I'm using the cygwin development environment and so thought this was the
correct place to post a problem. But you make a good point, so I copied
the file to /tmp, mounted as binary, and got the same results.
So, I guess the gcc libraries are at fault? Is this the right list?
--
Ken Shaffer
On
On Fri, Nov 05, 2004 at 11:26:31AM -0500, Shaffer, Kenneth wrote:
>I have a program doing a binary read on a file which happens to exist on a
>textmode mount and find that once a ctrl-Z (0x1a) byte is read, it doesn't
>read the rest of the file since ctrl-Z is a DOS EOF.
>
>The program is compiled
13 matches
Mail list logo
