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
# a bug report to inform us about it.
! if test x"$SKIP_FTRUNCATE_CHECK" != xyes; then
! AC_MSG_FAILURE([Your system lacks the ftruncate function.
! Please report this, along with the output of "uname -a", to the
! bug-coreutils@gnu.org
s, along with the output of "uname -a", to the
> bug-coreutils@gnu.org mailing list. To continue past this point,
> rerun configure with SKIP_FTRUNCATE_CHECK=yes.
> E.g., ./configure SKIP_FTRUNCATE_CHECK=yes
>
> Since mingw will still be arou
tils@gnu.org mailing list. To continue past this point,
rerun configure with SKIP_FTRUNCATE_CHECK=yes.
E.g., ./configure SKIP_FTRUNCATE_CHECK=yes
Since mingw will still be around for a few years, we need to keep this module.
(But if you didn't have many reports like this and
