unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: guile-2.0 on mingw: the sequel
Date: Sat, 24 Aug 2013 09:31:24 +0300	[thread overview]
Message-ID: <838uzrioqr.fsf@gnu.org> (raw)
In-Reply-To: <CAMFYt2ZP-vVWX9F4Auya50F8j-iCcwfRn4SDc98SJ2OSLLTmLA@mail.gmail.com>

> Date: Fri, 23 Aug 2013 22:14:43 +0200
> From: Panicz Maciej Godek <godek.maciek@gmail.com>
> Cc: "guile-user@gnu.org" <guile-user@gnu.org>
> 
> > Configuring with --prefix=/usr is a mistake: there's no /usr on your
> > system, as far as MinGW programs are concerned.
> > [...]
> >
> 
> 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?)

> 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.



  reply	other threads:[~2013-08-24  6:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 20:25 guile-2.0 on mingw: the sequel Panicz Maciej Godek
2013-08-23  6:38 ` Eli Zaretskii
2013-08-23  9:29   ` Panicz Maciej Godek
2013-08-23 10:16     ` Eli Zaretskii
2013-08-23 20:14       ` Panicz Maciej Godek
2013-08-24  6:31         ` Eli Zaretskii [this message]
2013-08-24  8:05           ` Panicz Maciej Godek
2013-08-25 15:26             ` Eli Zaretskii
2013-08-25 16:59               ` Mark H Weaver
2013-08-25 17:47                 ` Eli Zaretskii
2013-08-25 19:03                   ` Ludovic Courtès
2013-08-25 19:34                   ` Mark H Weaver
2013-08-27 21:51                   ` Panicz Maciej Godek
2013-08-26 13:28                 ` Eli Zaretskii
2013-08-23 15:13     ` Mark H Weaver
2013-08-23 15:34       ` Eli Zaretskii
2013-08-25 18:59         ` Ludovic Courtès
2013-08-25 21:19           ` Mark H Weaver
2013-08-26  2:35           ` Eli Zaretskii
2013-08-25 19:50         ` Mark H Weaver
2013-08-25 19:56           ` Mark H Weaver
2013-08-25 20:33             ` Eli Zaretskii
2013-08-25 20:40               ` Eli Zaretskii
2013-08-25 21:42               ` Mark H Weaver
2013-08-25 23:24                 ` dsmich
2013-08-26  2:44                   ` Eli Zaretskii
2013-08-26  5:56                     ` Mark H Weaver
2013-08-26  6:26                       ` Mark H Weaver
2013-08-26 13:10                       ` Eli Zaretskii
2013-08-26  2:40                 ` Eli Zaretskii
2013-08-25 20:32           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838uzrioqr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=godek.maciek@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).