guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build failures - compiling TeXmacs under guile 2.0.5


From: Jan Synacek
Subject: Re: Build failures - compiling TeXmacs under guile 2.0.5
Date: Thu, 24 May 2012 14:57:56 +0200
User-agent: Mutt/1.5.21 (2011-07-01)

On 04/16/12 at 11:41pm, Ludovic Courtès wrote:
> Hi Jan,
> 
> Thanks for the report.
> 
> Jan Synacek <address@hidden> skribis:
> 
> > I'm trying to build TeXmacs 1.0.7 with guile 2.0.5 and I'm getting tons of
> > errors like these:
> >
> >   usr/include/guile/2.0/libguile/gsubr.h:64:12: error:   initializing 
> > argument 5
> >   of ‘scm_unused_struct* scm_c_define_gsubr(const char*, int, int, int,
> >   scm_t_subr)’ [-fpermissive]
> >
> >   Guile/Glue/glue_server.cpp:1173:56: error: invalid conversion from
> >   ‘scm_unused_struct* (*)()’ to ‘scm_t_subr {aka void*}’ [-fpermissive]
> 
> Can you show the line where this occurs?  Presumably the code lacks a
> cast to ‘scm_t_subr’, which is implicit in C but not in C++.
> 
> Thanks,
> Ludo’.
> 
> 

Sorry for such late response, I gave it up after a while:) But..
One more try on this:

$ make

  <snip>

  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*)’

  <snip>

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

  <snip>

Again, tons of errors like those two above, and I expect there will be more
like that.

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

glue.cpp:1267:
   scm_new_procedure ("tree?", (FN) treeP, 1, 0, 0);

I'm aware that C++ is pretty strict about casting. Is there any way I could fix
those? I guess that if it is possible to bend g++ to allow me to recast all
those, I could use macros somehow.

Thanks,
-- 
Jan Synacek
Software Engineer, BaseOS team Brno, Red Hat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]