Thanks - I think there is actually no tls support yet.
I will take a look at the autoconf issue when I have time - but I'm very
busy at work this week.
l...@gnu.org (Ludovic Courtès) writes:
> Neil Jerram writes:
>
>> I noticed that the docs on the Guile web pages are a bit out of date.
>> The 1.8 ones are behind those in 1.8.7 (the latest release).
>
> http://www.gnu.org/software/guile/manual/html_node/index.html appears to
> correspond to 1.8.
EHLO
On Fri 23 Oct 2009 11:16, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo writes:
>
>> On Fri 02 Oct 2009 02:15, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Because of the macrology that’s used to statically allocate stringbufs [0],
>>> the string has to be a literal:
>>>
>>> SCM_SY
I saw an interesting bug today. Can you guess the cause of this error?
ERROR: In procedure memoization:
ERROR: Bad formal #...@0+0 in expression (lambda (#...@0+0) (apply (lambda
(#{filename\ 2520}# #{proc\ 2521}# #{reference\ 2522}#) (let
((#{template\ 2523}# (string-append #{filename\ 2520}# ".X
On Thu 22 Oct 2009 23:09, l...@gnu.org (Ludovic Courtès) writes:
> I’ve been tracking unbound variables and found numerous typos easily
> fixed [0]. Most of them had been there for years.
Excellent catch, thanks!
A
--
http://wingolog.org/
Hi,
Andy Wingo writes:
> On Fri 02 Oct 2009 02:15, l...@gnu.org (Ludovic Courtès) writes:
>
>> Because of the macrology that’s used to statically allocate stringbufs [0],
>> the string has to be a literal:
>>
>> SCM_SYMBOL (s_foo, "foo");
>>
>> What do you think?
>
> Need more information :) H
Hi Greg,
NetBSD builds have been failing since the introduction of TLS support
(http://autobuild.josefsson.org/guile/log-200910220603170256000.txt):
gcc -I/usr/pkg/include -I/usr/y0/include -Wall -Wmissing-prototypes -Werror
-fvisibility=hidden -I/usr/pkg/include -g -O2 -I/usr/pkg/include
-I/
