> Dennis Clarke skribis:
>
> > Only question I have, am I safe to install the resultant binaries
> ?
>
> Yes, of course.
>
> Though there is NO WARRANTY, to the extent permitted by law. ;-)
No problem, that is the same as windows 7 and that thing is trash. At least
with open source it
Dennis Clarke skribis:
> Only question I have, am I safe to install the resultant binaries ?
Yes, of course.
Though there is NO WARRANTY, to the extent permitted by law. ;-)
Ludo’.
> Hi Dennis,
>
> Dennis Clarke skribis:
>
> > Well based on what I see here :
> >
> > http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00135.html
> >
> > .. this is a bug that has been around a while and isn't going away
> easily.
>
> Well, more than a bug, it’s a consequence of the u
Hi Dennis,
Dennis Clarke skribis:
> Well based on what I see here :
>
> http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00135.html
>
> .. this is a bug that has been around a while and isn't going away easily.
Well, more than a bug, it’s a consequence of the use of a conservative
garba
Hi, and sorry for the delay,
Dennis Clarke skribis:
> Simply looking at that output fills me with a sense of dread.
> How can one trust anything that issues messages like those ?
Well, there’s really nothing to be worried about. Most are harmless
warnings, some are debugging output from the L
Well based on what I see here :
http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00135.html
.. this is a bug that has been around a while and isn't going away easily.
$ ./check-guile threads.test
Testing /usr/local/build/guile-2.0.6_2.6.32-5-amd64_002/meta/guile ...
threads.test
with
$ time -p gmake check
GEN public-submodule-commit
gmake check-recursive
gmake[1]: Entering directory `/usr/local/build/guile-2.0.6_2.6.32-5-amd64_002'
Making check in lib
gmake[2]: Entering directory
`/usr/local/build/guile-2.0.6_2.6.32-5-amd64_002/lib'
gmake check-recursive
gmake[3]: En
Hi Dennis,
> This is not going well at all :
>
> $ dpkg -S /usr/lib/libgc.so
> ...
try this:
dpkg -l | grep libgc1c2
dpkg -l | grep libgc-dev
i am on testing and the answers here are 7.1-8. if these packages are not
installed,
or if the -dev is not installed, do insta
- Original Message -
From: l...@gnu.org (Ludovic Courtès)
Date: Tuesday, July 10, 2012 4:09 am
Subject: Re: bug#11885: guile-2.0.6 1 of 1 test failed
To: Dennis Clarke
Cc: 11...@debbugs.gnu.org
> Hi,
>
> Dennis Clarke skribis:
>
> >> > Not sure how
Hi,
Dennis Clarke skribis:
>> > Not sure how to get your libC version
>>
>> IIRC “dpkg -l libgc” should tell you.
>
> $ dpkg -l libgc
I’m really talking about libgc (aka. Boehm-GC or BDW-GC), not libc.
Perhaps “dpkg -S /usr/lib/libgc.so”?
Ludo’.
- Original Message -
From: l...@gnu.org (Ludovic Courtès)
Date: Monday, July 9, 2012 12:47 pm
Subject: Re: bug#11885: guile-2.0.6 1 of 1 test failed
To: Dennis Clarke
Cc: 11...@debbugs.gnu.org
> >
> >> Which GCC optimization options, and which libgc ver
> > Not sure how to get your libC version
>
> IIRC “dpkg -l libgc” should tell you.
$ dpkg -l libgc
No packages found matching libgc.
hrmmm ... let me dig around in there
Dennis
Hi,
Dennis Clarke skribis:
>> Dennis Clarke skribis:
>>
>> > FAIL: gc.test: gc: Lexical vars are collectable
>>
>> [...]
>>
>> > FAIL: threads.test: mutex-ownership: mutex with owner not retained
>> (bug #27450)
>>
>> These two tests are GC-sensitive, so unfortunately failure rarely
>> ind
> Hi,
>
> Dennis Clarke skribis:
>
> > FAIL: gc.test: gc: Lexical vars are collectable
>
> [...]
>
> > FAIL: threads.test: mutex-ownership: mutex with owner not retained
> (bug #27450)
>
> These two tests are GC-sensitive, so unfortunately failure rarely
> indicates a problem. IOW, it is sa
Hi,
Dennis Clarke skribis:
> FAIL: gc.test: gc: Lexical vars are collectable
[...]
> FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug
> #27450)
These two tests are GC-sensitive, so unfortunately failure rarely
indicates a problem. IOW, it is safe to ignore them.
Whic
Let me know what may be needed. The report says "failures: 2" and the final
message at the bottom says "1 of 1 test failed".
I think that the test results are a "fail" also but that is just an opinion.
Seems to be a well known bug regardless :
FAIL: threads.test: mutex-ownership:
16 matches
Mail list logo
