2013/8/24 Eli Zaretskii <eliz@gnu.org>

> > yes, it seems that this was the reason. So now the guile
> > interpreter runs properly, but I still have a problem with
> > running a program that, having been linked against
> > libguile, would call scm_with_guile or scm_init_guile, e.g.
> > ===
> > #include <libguile.h>
> > void hi(void *unused) { scm_puts("hello!\n", scm_current_output_port());
> }
> > int main() {
> >    scm_with_guile(hi, NULL);
> >   return 0;
> > }
> > ===
>
> Does this work on other platforms?  (I know almost nothing about
> linking C programs with libguile; maybe your program has a bug, or you
> are missing some function call necessary for this to work?)
>
>
It's the simplest example I could come up with.
The same code executes properly (i.e. displays "hello!") on linux.
I don't know whether windows requires any additional steps for that
to work.

> I compile it under msys in c:/guile-2.0/bin (i.e. prefix/bin) using
> > $ gcc -o hello.exe hello.c -I ../include/guile/2.0 -lguile-2.0
>
> There should be no need to compile under MSYS, you can compile from
> the Windows cmd window.  I don't think that's the reason for your
> problems, but it's worth a try.
>

I did, but the result's still the same (i.e. stack overflow exception).
I could try linking it with libguile-1.8 and see if that works, but
I''d be truly grateful if anyone who's had some experience with
libguile-2.0 linkage on mingw could help me (if such person exists :D)

Still, thanks for pushing my work ahead a little :)