public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ftruncate64() question?
Date: Mon, 24 May 2004 09:37:00 -0000	[thread overview]
Message-ID: <20040523211450.GA919@coe.bosbc.com> (raw)
In-Reply-To: <006f01c440cc$13eef530$64fda287@docbill002>

On Sun, May 23, 2004 at 09:29:23AM -0400, Bill C. Riemers wrote:
>> On Sat, May 22, 2004 at 04:24:22PM -0400, Bill C. Riemers wrote:
>>   bash-2.05b$ ./off_t
>>   sizeof(off_t) = 8
>
>>You don't use ftruncate64.  You use ftruncate.  Cygwin is 64 bit by
>>default.
>
>I stand correct.  The bug was elsewhere in my code.  I have been
>working with java so much recently, I had forgotten that on Intel
>platforms long is only 32 bits...  My workaround because I implemented
>it on the filename before the value was truncated by passing it to my
>function as a long...
>
>>How about referencing these messages so we'd have some clue as to what
>>you're talking about?
>
>Sorry, as I originally commented RedHat now considers my IE 6.0 browser
>a spambot.  The way I ended up working around the problem to view the
>messages anyway did not allow me to cut and paste URL's.

If you search google, you'll probably be able to fix your Internet
Explorer installation so that "RedHat" (sic) does not consider you to be
a spambot.

Regardless, this should be only a minor inconvenience since you would be
able to at least point to google cache of the articles or, if you were
able to read the articles, include the articles themselves.

cgf

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

  reply	other threads:[~2004-05-23 21:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 15:33 where is at at? Clemson, Chris
2004-05-21 16:04 ` Dave Korn
2004-05-21 16:23   ` Andrew DeFaria
2004-05-21 19:15     ` Igor Pechtchanski
2004-05-21 20:04       ` Dave Korn
2004-05-21 20:17         ` Larry Hall
2004-05-21 20:19           ` Christopher Faylor
2004-05-21 20:29             ` Igor Pechtchanski
2004-05-21 20:38               ` Joshua Daniel Franklin
2004-05-21 20:43                 ` [OT] " Igor Pechtchanski
2004-05-21 22:21                   ` Christopher Faylor
2004-05-22  0:51                     ` ftruncate64() question? Bill C. Riemers
2004-05-22  1:39                       ` Brian Ford
2004-05-22 19:09                         ` Larry Hall
2004-05-25  2:11                           ` [OT] " Igor Pechtchanski
2004-05-25  2:42                             ` Christopher Faylor
2004-05-25  8:55                               ` Larry Hall
2004-05-23  6:58                         ` Bill C. Riemers
2004-05-23  9:36                           ` Christopher Faylor
2004-05-23 21:14                             ` Hannu E K Nevalainen
2004-05-24  9:25                             ` Bill C. Riemers
2004-05-24  9:37                               ` Christopher Faylor [this message]
2004-05-24 16:16                                 ` spambot? Bill C. Riemers
2004-05-24 16:31                                   ` spambot? Larry Hall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040523211450.GA919@coe.bosbc.com \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).