> They surely store the uncompressed size somewhere
NTFS certainly stores that. It's the field referred to as "real" at eg
http://ftp.kolibrios.org/users/Asper/docs/NTFS/ntfsdoc.html#id4793056.
("allocated" is what it says on the tin. "initialized" would be smaller than
"real" if it's compre
Eli Zaretskii wrote:
> You underestimate me ;-)
>
> What I have is actually this:
> [...]
>
> and I wrote 'fcntl' emulation for Windows that uses a mutex.
Indeed, I had not expected this. :-)
> That said, I'm not wedded to the above approach, and if people like a
> completely disjoint code for
Hi,
Can I have some tutorial docs so, I can understand the way by which I can
cross compile the my driver code for Mips target board.
--
Regards,
Sourabh Bansal
___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-mak
> Date: Fri, 26 Apr 2013 09:05:18 +0100
> From: Tim Murphy
> Cc: "Paul D. Smith" , "bug-make@gnu.org"
>
> > How much would you use for the timeout, though? A sub-Make could
> > legitimately run for a very long time, depending on what's in the
> > Makefile.
> >
> > FWIW, I currently let Make wai
> Date: Thu, 25 Apr 2013 02:16:33 +0200
> Cc: e...@gnu.org, bug-make@gnu.org
> From: Frank Heckenbach
>
> > > On Windows, you said fstat was very expensive, didn't you? Or is
> > > lseek even worse?
> >
> > I think anything that potentially moves the file pointer can be
> > sometimes expensive a
On 25 April 2013 20:06, Eli Zaretskii wrote:
> > Date: Thu, 25 Apr 2013 19:36:28 +0100
> > From: Tim Murphy
> > Cc: "bug-make@gnu.org"
> >
> > 1) sem_timedwait() in posix lets you timeout so in a big build when
> > something crashes or just sits around, there is at least the option of
> > prin
