From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: erik quanstrom <quanstro@speakeasy.net>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Release candidate rc-1.6c4 available
Date: Thu, 1 Nov 2001 12:46:10 -0500 [thread overview]
Message-ID: <20011101174610.24409.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from erik quanstrom <quanstro@speakeasy.net> of "Thu, 01 Nov 2001 11:20:00 EST." <20011101162000.072423F403@quanstro.net>
Grep in /usr/include. Defining _LARGEFILE_SOURCE and/or
_FILE_OFFSET_BITS=64 does magic in your system header files so that
open() becomes open64(), etc. On solaris, man lf64.
The failure mode is that if you have a large file, and you run rc -c
'foo <bar', foo can fail if bar was opened in 32 bit mode. The latest
rc works properly in that case.
next prev parent reply other threads:[~2001-11-01 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 16:20 erik quanstrom
2001-11-01 17:46 ` Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-31 16:18 Tim Goodwin
2001-11-01 17:35 ` Stefan Dalibor
2001-11-04 17:58 ` Scott Kenney
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=20011101174610.24409.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=quanstro@speakeasy.net \
--cc=rc@hawkwind.utcs.toronto.edu \
--subject='Re: Release candidate rc-1.6c4 available' \
/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
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 NNTP newsgroup(s).