On Thu, 11 Mar 2004, Larry Hall wrote:
> At 04:31 PM 3/11/2004, you wrote:
> >I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin.
> >When I try to run it I get _fnctl64 can not be found
> >errors.
> >
> >The reason I upgraded was because I was trying to
> >compile code that was using the >2GB calls
At 04:59 PM 3/11/2004, you wrote:
>LOL. Larry, we have got to stop doing this[*]. You take the even days,
>and I'll take the odd ones, ok? ;-)
OK, but I sometimes take weekends off. :-)
>Igor
>[*] The above replies are essentially the same, and posted withing a
>minute of each other.
On Thu, 11 Mar 2004, Larry Hall wrote:
> At 04:31 PM 3/11/2004, you wrote:
> >I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin.
> >When I try to run it I get _fnctl64 can not be found
> >errors.
> >
> >The reason I upgraded was because I was trying to
> >compile code that was using the >2GB calls
On Thu, 11 Mar 2004, Kevin Stedman wrote:
> I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin.
> When I try to run it I get _fnctl64 can not be found
> errors.
>
> The reason I upgraded was because I was trying to
> compile code that was using the >2GB calls like
> lseek64, fstat64, open64, ...
>
At 04:31 PM 3/11/2004, you wrote:
>I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin.
>When I try to run it I get _fnctl64 can not be found
>errors.
>
>The reason I upgraded was because I was trying to
>compile code that was using the >2GB calls like
>lseek64, fstat64, open64, ...
>
>What am I
I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin.
When I try to run it I get _fnctl64 can not be found
errors.
The reason I upgraded was because I was trying to
compile code that was using the >2GB calls like
lseek64, fstat64, open64, ...
What am I missing in my cygwin build, because of thes
6 matches
Mail list logo