Hello, Bug found. The problem seems to happen because the libguile-i18n-v-0 is missing these flags: -export-dynamic -no-undefined Infact it created a static library and not a DLL, I believe it failed for this reason. Now I try to quickly fix it, I will retest and I will report the result.
Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : "Andy Wingo" wi...@pobox.com To : "carlo.bramix" carlo.bra...@libero.it Cc : "guile-devel" guile-devel@gnu.org Date : Sat, 20 Jun 2009 12:53:48 +0200 Subject : Re: Again on Windows support (2) > On Fri 19 Jun 2009 21:11, "carlo.bramix" <carlo.bra...@libero.it> writes: > > > Under Cygwin, compilation advanced much more with newer sources > > (yeah!) > > Cool :) > > > but it gave another error: > > > > GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o > > "ice-9/i18n. > > go" "ice-9/i18n.scm" > > Backtrace: > [...] > > ?: 34* [load-extension "libguile-i18n-v-0" "scm_init_i18n"] > > > > <unnamed port>: In procedure dynamic-link in expression (load-extension > > "libguile-i18n-v-0" "scm_init_i18n"): > > <unnamed port>: file: "libguile-i18n-v-0", message: "can't open the > > module" > > Perhaps something is wrong when linking this module. "Can't open the > module" is not a very good warning :) > > If you've gotten to here, you might be able to run Guile: > > $ meta/guile > > If it doesn't error about srfi-1 lib loading, that means you do have > dynamic library loading working, that it's just a problem with the i18n > lib. > > Good luck, > > Andy > -- > http://wingolog.org/ >
