On Sat, 13 Jan 2007, Kevin Ryde wrote:
Hugh Sasse [EMAIL PROTECTED] writes:
cc1: warnings being treated as errors
That's designed to force all users to be developers :-(.
Should that be in the *release* then? Prior to release definitely
makes sense.
numbers.c: In function 'xisinf':
Hi Jon,
I think your idea is silly. However you might implement it via module
binder procs. See http://article.gmane.org/gmane.lisp.guile.user/3321
for an idea of how this can be done.
Regards,
Wingo.
--
http://wingolog.org/
___
Guile-user mailing
On Mon, 15 Jan 2007, Hugh Sasse wrote:
On Sat, 13 Jan 2007, Kevin Ryde wrote:
You might be able to just stick in a prototype,
Tried to do that, it still complained about it.
or alternately just
./configure --disable-error-on-warning.
I am using Guile and Greg to build a testsuite for a special-purpose C++
library. I have written the (C++) code for a Guile extension that
serves as an interface between the Greg testcases and the C++ library;
however, do I need to do anything special when building/installing Guile
in order
Hugh Sasse [EMAIL PROTECTED] writes:
posix.c: In function 'scm_putenv':
posix.c:1332: error: 'len' undeclared (first use in this function)
Thanks. Dodgy conditionals :-(. You can use the len at the start
of the function (claiming to be for mingw).
Does that mean there's no unsetenv() on
