Bruno Haible <[EMAIL PROTECTED]> wrote:
> This, I can't tell, as I'm only cross-compiling. I can't do more than "nm"
> on the object files.
At least we know gnulib-based applications that use ftruncate
will continue to link when compiled for mingw.
>> If we're no closer to removing the module, th
Hi Jim,
> Now that you've done it, that's fine.
OK, I'm committing it now, after you are saying that it's fine.
> BTW, since you seem to care about mingw, can you tell us which part
> of lib/ftruncate.c is used on that system?
It uses a call to 'chsize'. 'chsize' is a documented function of the
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Hello Jim,
>
>> * m4/ftruncate.m4: Adjust comment to give this module a 3-year reprieve.
>> Prompted by a report from Bruno Haible that mingw lacks ftruncate.
>
> I also meant to make life easier to people using mingw. mingw will not have
> gone a
Hello Jim,
> * m4/ftruncate.m4: Adjust comment to give this module a 3-year reprieve.
> Prompted by a report from Bruno Haible that mingw lacks ftruncate.
I also meant to make life easier to people using mingw. mingw will not have
gone away in three years - that's more a matter of 10-
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Hi Jim,
>
> A gnulib testdir with the module 'ftruncate', cross-compiled to mingw
> (--host=i386-pc-mingw32), showed me this:
>
> configure: error: Your system lacks the ftruncate function.
> Please report this, along with the output of "uname -a"
