l...@gnu.org (Ludovic Courtès) writes:
> Yes, Valgrind can't cope with libgc, which is inconvenient.
Interesting. That sounds like a shame, but actually I guess it's not
so bad because libgc will remove many of things that make valgrind of
interest to us. Also, in the last resort, we can contri
"carlo.bramix" writes:
> Hello!
>
>> > LIBGUILE/GSUBR.C
>> >
>> > function alloca() is undefined because under Windows the intrinsic
>> > function is called _alloca().
>>
>> Hm, I thought the Gnulib alloca thing should have fixed this. Does
>> adding #include in gsubr.c not fix
l...@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> Attached is a patch that aggregates makefiles under `examples'. OK to
> apply?
Looks good to me.
Neil
Albert Chin writes:
>> 1. Do all of the standalone tests fail with a stack overflow, or just
>> those two?
>
> Unknown. Some of the tests fail to dlopen some modules:
> ERROR: In procedure dynamic-link:
> ERROR: file: "libguile-srfi-srfi-1-v-3", message: "can't open the module"
> FAIL: test
Hello,
Neil Jerram writes:
> "carlo.bramix" writes:
>
>> Hello!
>>
>>> > LIBGUILE/GSUBR.C
>>> >
>>> > function alloca() is undefined because under Windows the intrinsic
>>> > function is called _alloca().
>>>
>>> Hm, I thought the Gnulib alloca thing should have fixed this. Do
Hello,
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Yes, Valgrind can't cope with libgc, which is inconvenient.
>
> Interesting. That sounds like a shame, but actually I guess it's not
> so bad because libgc will remove many of things that make valgrind of
> interest to us.
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hello!
>>
>> Attached is a patch that aggregates makefiles under `examples'. OK to
>> apply?
>
> Looks good to me.
Thanks, pushed.
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=branch_release-1-8&id=9a84dc8bbcf02993109f1e
On Tue, Mar 24, 2009 at 08:50:59PM +, Neil Jerram wrote:
> Albert Chin writes:
>
> >> 1. Do all of the standalone tests fail with a stack overflow, or just
> >> those two?
> >
> > Unknown. Some of the tests fail to dlopen some modules:
> > ERROR: In procedure dynamic-link:
> > ERROR: file
