Re: any ideas on undefined reference

Hi Gopi, Thanks very much for the information, particularly about the alloca bug. It looks at present like it is a problem with autoconf (which is where the ./configure script comes from, among other things), that is sort of inherited by guile. That particular bit of code changed quite a bit

Re: any ideas on undefined reference

Hi You are welcome.Everything under guile is working fine now.I have to go through other libgraph forumns.Is my guile error really a bug?Was my information useful?Are you member of guile development team? Regards Gopi Jon Wilson <[EMAIL PROTECTED]> wrote: Hi Gopi, Thanks for all the

Re: alloca bug

Jon Wilson <[EMAIL PROTECTED]> writes: > > scmconfig.h seems to only be created while make all is running (try > make scmconfig after ../configure). Yes, it's generated. > However, on my system, and Gopi's > FreeBSD system as well, scmconfig.h includes . So, > indirectly, eval.c includes , and d

Re: 1.8.1 config fails, but gmp passed its tests.

I have explored this a little further. If I export CC=gcc\ -v I get no more information out of this really. It is skipping those libraries, but I can't see why. GNU ld seems to lack a verbose option. Running configure --without-gnu-ld doesn't help -- configure sees that GCC uses /usr/local/

alloca bug

Hi, So it looks like the blob in libguile/eval.c (lines 40-56) from the autoconf manual to define alloca doesn't work on BSD systems. This is in guile 1.8.1. In the subdirectory libguile: eval.c includes __scm.h __scm.h includes scmconfig.h scmconfig.h seems to only be created while make all

Re: any ideas on undefined reference

Hi Gopi, Thanks for all the information. So guile is working now? Wonderful! I hope that you can get libgraph working just fine as well. Regards, Jon Gopi kumaran wrote: Hi Jon Sorry for confusing you with libgraph.I am trying to use graphics in unix environment with c program.Guile was ne

Re: debugging scheme module

Hi, Al Nikolov <[EMAIL PROTECTED]> writes: > Fatal error: [library-name] wrong-type-arg: ("caddar" "Wrong type argument > in position ~A: ~S" (1 ()) #f) This means that at some point, `caddar' is invoked and is passed `#f' instead of a list. :-) > Since my scheme code is bigger than two parent

debugging scheme module

Hello, all! I'm totally newbie in Guile and R5RS, faced to write a scheme module for an application written with Guile. When i do just another wierd mistake and run the app, i usually get uncomprehensive error messages like: Fatal error: [library-name] wrong-type-arg: ("caddar" "Wrong type argum