A thought about the current error building Gem on MinGW, perhaps it is because ./configure is detecting libdl, which MinGW has, but the libdl code doesn't work for Gem on MinGW. This is similar to what patco was sorting out with pure-data on MinGW. So something like this:
http://www.trilithium.com/johan/2004/12/problem-with-dlsym/
.hc
----------------------------------------------------------------------------
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-07-26 00:31, Hans-Christoph Steiner wrote:
A thought about the current error building Gem on MinGW, perhaps it is because ./configure is detecting libdl, which MinGW has, but the libdl code doesn't work for Gem on MinGW. This is similar to what patco was sorting out with pure-data on MinGW. So something like this:
no
anyhow, i do think it is fixed now (at least Dylib now compiles on cygwin; i forgot the passwd for the gui login on the w32 build machine so i could not test on mingw)
fgmasdr IOhannes
PS: hint to hans: could you please send me the password off-list?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-07-26 09:26, IOhannes m zmoelnig wrote:
On 2011-07-26 00:31, Hans-Christoph Steiner wrote:
A thought about the current error building Gem on MinGW, perhaps it is because ./configure is detecting libdl, which MinGW has, but the libdl code doesn't work for Gem on MinGW. This is similar to what patco was sorting out with pure-data on MinGW. So something like this:
no
on 2nd read, maybe yes.
anyhow, i'm still hoping i fixed it.
fgmasdr IOhannes
-
Hans-Christoph Steiner -
IOhannes m zmoelnig