unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Synacek <jsynacek@redhat.com>
Cc: guile-devel@gnu.org
Subject: Re: Build failures - compiling TeXmacs under guile 2.0.5
Date: Fri, 25 May 2012 17:51:04 +0200	[thread overview]
Message-ID: <87zk8w5kev.fsf@gnu.org> (raw)
In-Reply-To: <20120524125756.GA10861@redhat.com> (Jan Synacek's message of "Thu, 24 May 2012 14:57:56 +0200")

Hi!

Jan Synacek <jsynacek@redhat.com> skribis:

>   Guile/Glue/glue.cpp:233:31: error: cannot convert ‘SCM {aka
>   scm_unused_struct*}’ to ‘const char*’ for argument ‘1’ to ‘scm_unused_struct*
>   scm_str2string(const char*)’

[...]

> glue.cpp:233 looks like this:
>     char* _r= scm_scm2str (s, &len_r); // my comment - s is declared as SCM

Indeed, scm_str2string expects a ‘const char *’, not an ‘SCM’.

But what is the definition of ‘scm_scm2str’?  It must be in TeXmacs.

>   Guile/Glue/glue.cpp:1267:46: error: invalid conversion from ‘FN {aka
>   scm_unused_struct* (*)()}’ to ‘scm_t_subr {aka void*}’ [-fpermissive]

[...]

>    scm_new_procedure ("tree?", (FN) treeP, 1, 0, 0);

Yes, FN should be defined like this:

  typedef scm_t_subr FN;

or:

  #define FN scm_t_subr

Can you check whether that solves the problem?

Thanks,
Ludo’.



  reply	other threads:[~2012-05-25 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  9:46 Build failures - compiling TeXmacs under guile 2.0.5 Jan Synacek
2012-04-16 21:41 ` Ludovic Courtès
2012-05-24 12:57   ` Jan Synacek
2012-05-25 15:51     ` Ludovic Courtès [this message]
2012-05-28  7:02       ` Jan Synacek
2012-05-28  8:10         ` Thien-Thi Nguyen
2012-05-28 22:29         ` Ludovic Courtès
2012-05-29  6:36           ` Jan Synacek
2012-05-29  8:50             ` Ludovic Courtès
2012-05-29 12:18               ` Jan Synacek
2012-05-29 13:54                 ` Ludovic Courtès
2012-05-30  7:22                   ` Jan Synacek
2012-05-30 12:54                     ` Ludovic Courtès

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=87zk8w5kev.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=jsynacek@redhat.com \
    /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).