Re: cross building 1.9.14 for mingw

2011-02-24 Thread Jan Nieuwenhuizen
Andy Wingo schreef op di 22-02-2011 om 09:34 [+0100]: Hi Andy, Excuse the long quote here No problem. I did, and Bruno Haible does not really care about this brokenness or about cross compiling; That is a totally unfair characterization, Jan. You met him in the Hague and he did not

Re: cross building 1.9.14 for mingw

2011-02-24 Thread Ludovic Courtès
Hi! BTW I added cross-compilation jobs to Hydra (the ‘xbuild_*’ things): http://hydra.nixos.org/jobset/gnu/guile-2-0/ The cross-MinGW one needs some love, but at least the cross-GNU one works fine without special hacks. Thanks, Ludo’.

Re: SCM_BOOL_T became #nil -- et al. ?

2011-02-24 Thread Ken Raeburn
On Feb 23, 2011, at 15:14, Bruce Korb wrote: * guile should provide autoconf macros to do checking, like for wrong version headers. That seems like a good idea, but unless all the other packages' header directories have already been added to the include path by the time this test is run,

Re: What version of GMP should we require?

2011-02-24 Thread Ludovic Courtès
Hi Mark, Mark H Weaver m...@netris.org writes: I recently noticed that scm_i_big2dbl contains some crufty and inefficient compatibility code to work around unspecified rounding behavior of mpz_get_d in GMP prior to version 4.2. GMP 4.2 was released in March 2006 and has been in Debian since

Re: What version of GMP should we require?

2011-02-24 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: For 2.0, what about AC_CHECK_LIB ‘mpz_rootrem’, and provide a replacement when it’s not available? [...] Sounds reasonable. In ‘master’ you can of course require 4.2 and clean things up as you see fit. :-) Great, thanks! :) Mark

Re: SCM_BOOL_T became #nil -- et al. ?

2011-02-24 Thread Bruce Korb
On 02/24/11 08:35, Ken Raeburn wrote: On Feb 23, 2011, at 15:14, Bruce Korb wrote: * guile should provide autoconf macros to do checking, like for wrong version headers. That seems like a good idea, but unless all the other packages' header directories have already been added to the

Re: [PATCH] guile-snarf: allow multiple init actions on one line

2011-02-24 Thread Andreas Rottmann
l...@gnu.org (Ludovic Courtès) writes: Hi Brian, Thanks for the patches! I haven’t look at the other patch yet, but about this one: BT Templeton b...@hcoop.net writes: +#!/bin/sh Can you add a copyright/license header here? +snarf_test () +{ +local x +x=$(snarf $1) +

Re: [PATCH] guile-snarf: allow multiple init actions on one line

2011-02-24 Thread Ludovic Courtès
Hi, Andreas Rottmann a.rottm...@gmx.at writes: That's not true for '$(...)', see SUSv3, Section 2.6.3. Solaris 5.10 /bin/sh: --8---cut here---start-8--- echo $(echo foo) syntax error: `(' unexpected --8---cut

Re: on second/.go-cached run: ERROR: Unbound variable: for-each - simplified

2011-02-24 Thread Ludovic Courtès
Hi Jan, Jan Nieuwenhuizen janneke-l...@xs4all.nl writes: ERROR: In procedure module-lookup: ERROR: Unbound variable: for-each It’s very likely another problem with the ‘merge-generics’ strategy. Would you like to debug further, e.g., by adding ‘pk’s in boot-9.scm in ‘merge-generics’?

Re: reprise: scm_c_eval_string_from_file_line

2011-02-24 Thread Bruce Korb
On 02/24/11 08:56, Ludovic Courtès wrote: It compiles fine up to here: --8---cut here---start-8--- make[4]: Entering directory `/home/ludo/tmp/autogen-5.11.7pre1/getdefs' exec gd.c ; \ echo '#include config.h' ; \ echo '#undef PKGDATADIR' ; \ echo

Re: Set debug output width in REPL

2011-02-24 Thread Ludovic Courtès
Hi, Mike Gran spk...@yahoo.com writes: From:Mark H Weaver m...@netris.org Mark wrote: It seems to me that *width* should not be a global variable, but rather a per-repl setting. It probably belongs in the options field of the repl record, no? See repl-default-options in

Re: Set debug output width in REPL

2011-02-24 Thread Mike Gran
From:Ludovic Courtès l...@gnu.org How about having a per-REPL setting that’s automatically set to the terminal’s width by default? What’s the exact call to get the width? The lightweight way is to just check for the COLUMNS environment variable. Most of the xterm-like terminals set COLUMNS