Yep, should be changed, although in that specific case, it doesn't
matter, since we no longer use that part of libffi; ruby-ffi
implements its own closure allocator.

Speaking of win64, the libffi version in ruby-ffi has been updated to
3.0.9rc1, which theoretically includes win64 support, so it would be
interesting to see if that works with mingw64.  There are probably a
few win32-isms in the windows support in ruby-ffi that need to be
cleaned up.

2009/10/14 Luis Lavena <luislavena@gmail.com>:

>
> On Wed, Oct 14, 2009 at 10:14 AM, Jon <jon.forums@gmail.com> wrote:

>>
>> Should line 21 in ext/ffi_c/extconf.rb
>>
>> mf.puts "FFI_MMAP_EXEC=-DFFI_MMAP_EXEC_WRIT=#{Config::CONFIG['host_os'] =~ /(win32|mingw)/ ? 0 : 1}"
>>
>> use /mswin|mingw/ instead of /(win32|mingw)/
>>

>
> That is correct, the issue become a problem when Ruby is x86_64 (x64-mswin64_80)
>
> The proper evaluation should be mswin or mingw, since mingw can be 64
> bits too (working on that).
>
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exupéry
>