[ruby-core:36391] [Ruby 1.9 - Bug #4564] mingw-w64, truncate, ftruncate and ftello -- properly evalute it's existence

Issue #4564 has been updated by Luis Lavena.


Thank you Nobu,

Thing is that current 1.9.2 with MinGW do not work as you mentioned:

<pre><code>C:\Users\Luis>ruby -ve "File.open('a.data', 'w') { |f| f.truncate(1 << 32) }"
ruby 1.9.2p180 (2011-02-18) [i386-mingw32]

C:\Users\Luis>dir a.data
 Directory of C:\Users\Luis

22/05/2011  01:36 p.m.                 0 a.data
</code></pre>

But works on trunk:

<pre><code>C:\Users\Luis>ruby -ve "File.open('a.data', 'w') { |f| f.truncate(1 << 32) }"
ruby 1.9.3dev (2011-05-23 trunk 31696) [i386-mingw32]

C:\Users\Luis>dir a.data
 Directory of C:\Users\Luis

22/05/2011  01:37 p.m.     4.294.967.296 a.data
</code></pre>

----------------------------------------
Bug #4564: mingw-w64, truncate, ftruncate and ftello -- properly evalute it's existence
http://redmine.ruby-lang.org/issues/4564

Author: Luis Lavena
Status: Closed
Priority: Normal
Assignee: Luis Lavena
Category: core
Target version: 1.9.x
ruby -v: ruby 1.9.3dev (2011-04-10 trunk 31255) [i386-mingw32]


=begin
Hello,

I'm using latest mingw-w64 builds that target in a experimental way GCC 4.7.0 codebase (gcc trunk)

mingw-w64 also combines improved CRT and headers support, which in this case included truncate, ftruncate and ftello support.

Ruby's trunk for win32 currently redefines those blindly, and even forces these functions presence to be used.

The attached patch proposes rely on configure's ability to detect these functions presence, conditionally define the missing functions and rename these functions to avoid redefinitions.

Assigning to Mr. Nobuyoshi Nakada and Mr. Usaku Nakamura for review and approval.

I've tested this against GCC 3.4.5, 4.5.1, 4.5.2 and 4.7.0, all on Windows. These patches should not affect any Linux version, however could affect Visual Studio builds.

Thank you for your time looking into this.

=end



-- 
http://redmine.ruby-lang.org