Subject: Re: [ruby-ffi] Re: segfault on windows MRI but not windows JRuby |
From: Luis Lavena |
Date: 12/4/09 1:03 PM |
To: ruby-ffi@googlegroups.com |
On Fri, Dec 4, 2009 at 3:49 PM, Wayne Meissner <wmeissner@gmail.com> wrote:
<luislavena@gmail.com>:2009/12/5 Luis LavenaWhich versions of packages for mingw32 do you have installed? luis@seyori ~$ port installed | grep "mingw32" i386-mingw32-binutils @2.19.1_0 (active) i386-mingw32-gcc @3.4.5-20060117-2_0 (active) i386-mingw32-runtime @3.15.2_0 (active) i386-mingw32-w32api @3.13_0 (active)/could/ be what was used. gcc-core-3.4.5-20060117-1-src.tar.gz binutils-2.17.50-20060716-1-src.tar.gz mingw-runtime-3.10-20060909-1-src.tar.gz w32api-3.7-src.tar.gz I re-installed that machine last weekend, so I am just assuming those are the versions that were used (and that I didn't download later versions for it to use).Thats a good question. I built the cross compiler from source using the x86-mingw32-build.sh-0.0-20061107-1 build script from the mingw site. By default it downloads the following versions, so that
Hmn, trying to create a gem here with OSX (Leopard) and got this: http://gist.github.com/249257 Which may indicate that using the macport version of mingw32 is not playing so well with cross compiling, and /could/ be related to the issue we are seeing.-- 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