Re: Guile 2.2.0 build fails at bootstrapping language/cps/types.go

2017-03-17 Thread @相撲道
On March 17, 2017 11:31:50 AM GMT+01:00, l...@gnu.org wrote: > >What architecture and operating system is this on? x86_64 Ubuntu GNU/Linux 4.4.0-67 -- 白い熊@相撲道

Guile 2.2.0 build fails at bootstrapping language/cps/types.go

2017-03-16 Thread
ile/guile-2.2.0/bootstrap' Makefile:1857: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/shiroikume/compile/guile-2.2.0' Makefile:1743: recipe for target 'all' failed make: *** [all] Error 2 I haven't found anything on the web similar to this. How can I debug what's going on - why it's failing? -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-08-01 Thread
On 2013-08-01 16:42, 白い熊 wrote: Clisp, or Guile and it'll run. Currently I like playing with Clisp more, what I like about Guile is that it's a new project, so would Meant "GNU project", not "new project". :@) -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-08-01 Thread
it into the game a little too. Anyhow, I've been experimenting with the latest recommendation of: (with-output-to-string (lambda... and seems I'm close, however it coughs up errors in Clisp, so still no go. So if anyone would have alternate ideas, I'd be very much obliged. Thanks for helping me. -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-07-30 Thread
o-string (lambda () (apropos "clisp"))) is true in guile and there is no way to test equality with "" using = So how do I determine the string is empty with lisp equivalent code? Can't use equal? because it doesn't exist in lisp... -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-07-30 Thread
on (= ... comparison of output as= is the only equality function the three share so it seems back to square one So close -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-07-29 Thread
ned? because it's not defined in lisp or elisp. I think I'm missing something very simple... -- 白い熊

Re: Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-07-29 Thread
le open function will use the appropriate lisp syntax for opening the file. Now I'm wondering what the most effective / fastest way is to find out not whether a symbol is defined, but basically the answer to the self-awareness question: am I in guile, or am I in emacs... -- 白い熊

Determining programatically whether the interpreter is Guile or Clisp or Emcs

2013-07-29 Thread
or Emacs, or Crisp. Thank you very much for helping me. -- 白い熊