This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: upper limit to df reported available size?
- From: Jay K <jay dot krell at cornell dot edu>
- To: <cygwin at cygwin dot com>, <corinna-cygwin at cygwin dot com>, <eblake at redhat dot com>
- Date: Sat, 11 Dec 2010 01:51:00 +0000
- Subject: RE: upper limit to df reported available size?
- References: <1292030585.3028.ezmlm@cygwin.com>
> I guess what we really need
> is to redefine fsblkcnt_t to become a 64 bit type. Oh well, this
> requires another backward compatibility hack, just like back when we
> switched to 64 bit off_t (Cygwin 1.5). Let's do it at the same time as
> we change sigset_t and time_t to 64-bits(with knock-on effects to
> struct stat, among others). In other words,all good changes, but certainly
> something that will take a lot ofplanning to pull off in one go.
Can you fix the jmp_buf size then too maybe?
It is blown up by a factor of 4.
http://sourceware.org/ml/cygwin/2009-01/msg00863.html
I realize it has less/no value to fixing.
But I'm not sure how changing the others won't require *everything*
(just about) to be recompiled anyway. Maybe you rename functions somehow?
Thanks,
- Jay
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple