Greetings!
Alright then if you want to set up an instance for me on Monday I can
try to take a look then.
Take care,
Lucas Nussbaum writes:
> On 22/11/16 at 15:09 -0500, Camm Maguire wrote:
>> Greetings, and thanks for your reply!
>>
>> Lucas Nussbaum
On 22/11/16 at 15:09 -0500, Camm Maguire wrote:
> Greetings, and thanks for your reply!
>
> Lucas Nussbaum writes:
>
> > Hi Camm,
> >
> > I can still reproduce the build failure.
> > Do you want access to an Amazon AWS node where you could see it
> > yourself?
> > Do you do
Greetings, and thanks for your reply!
Lucas Nussbaum writes:
> Hi Camm,
>
> I can still reproduce the build failure.
> Do you want access to an Amazon AWS node where you could see it
> yourself?
> Do you do IRC, can you ping me? (those instances are quite expensive,
> I'd
Hi Camm,
I can still reproduce the build failure.
Do you want access to an Amazon AWS node where you could see it
yourself?
Do you do IRC, can you ping me? (those instances are quite expensive,
I'd rather not keep them running for days)
Lucas
On 19/11/16 at 10:43 -0500, Camm Maguire wrote:
>
severity 844148 normal
tags 844148 unreproducible
thanks
Greetings, and thanks for your report!
This is not an issue with GCL or acl2.
>From upstream:
=
Hi, Camm --
Yes, I think that's right. The comments in
Greetings, and thanks! To my understanding, this is only active on
thread-supporting lisps (e.g. ccl), not GCL. These should be no-op
wrappers in Debian. Can verify this with strace if needed.
Take care,
Stepan Golosunov writes:
> 14.11.2016 в 11:24:04 -0500 Camm
14.11.2016 в 11:24:04 -0500 Camm Maguire написал(а):
> Neither ACL2 nor underlying gcl makes any use of threads or locks, but
Note that the failing memoize-tests.lisp creates some sort of threads
and mentions lock contention in comments.
> > **CERTIFICATION FAILED** for
> >
On 2016-11-14 22:53, Aurelien Jarno wrote:
> control: reassign 844148 acl2
>
> On 2016-11-14 11:24, Camm Maguire wrote:
> > reassign 844148 glibc
> > thanks
> >
> > Greetings, and thanks so much for your report!
> >
> > Neither ACL2 nor underlying gcl makes any use of threads or locks, but
> >
control: reassign 844148 acl2
On 2016-11-14 11:24, Camm Maguire wrote:
> reassign 844148 glibc
> thanks
>
> Greetings, and thanks so much for your report!
>
> Neither ACL2 nor underlying gcl makes any use of threads or locks, but
> does rely on standard libc calls, which are known to turn on
9 matches
Mail list logo