At Fri, 18 Dec 2015 13:21:29 -0400, David Bremner wrote:
> Just to update, the default (-j4) build is still failing on ppc64el /
> aarm64 with racket 6.3
>
>
> https://buildd.debian.org/status/fetch.php?pkg=racket=ppc64el=6.3-2
> amp=1450447398
>
> I can try a single threaded build
At Fri, 18 Dec 2015 19:04:32 -0400, David Bremner wrote:
> Juan Francisco Cantero Hurtado writes:
>
> > On Friday 18 December 2015 13:42:32 Matthew Flatt wrote:
> >>At Fri, 18 Dec 2015 13:21:29 -0400, David Bremner wrote:
> >>>
> >>> I can try a single threaded build later,
On 19/12/15 00:04, David Bremner wrote:
Juan Francisco Cantero Hurtado writes:
On Friday 18 December 2015 13:42:32 Matthew Flatt wrote:
At Fri, 18 Dec 2015 13:21:29 -0400, David Bremner wrote:
I can try a single threaded build later, but I wondered if the huge
number of
Juan Francisco Cantero Hurtado writes:
> On Friday 18 December 2015 13:42:32 Matthew Flatt wrote:
>>At Fri, 18 Dec 2015 13:21:29 -0400, David Bremner wrote:
>>>
>>> I can try a single threaded build later, but I wondered if the huge
>>> number of warnings from the JIT code
Matthew Flatt writes:
> At Fri, 18 Dec 2015 13:21:29 -0400, David Bremner wrote:
>> Just to update, the default (-j4) build is still failing on ppc64el /
>> aarm64 with racket 6.3
>>
>>
>> https://buildd.debian.org/status/fetch.php?pkg=racket=ppc64el=6.3-2
>>
Apparently, racket's threads have problems on linux/ppc64. I ran
manually each test and only failed thread.rktl.
Here is the output: http://git.io/vqm18
quiet.rktl contains this code:
;; -- set up a timeout
(set! timeout-thread
(thread
(lambda ()
(sleep 1200)
It's possible that the recent change will fix this problem, but I'm not
optimistic. Assuming that the test still fails, is it possible to get
output from `racket -f basic.rktl` to we can see more specifically the
point of failure?
At Fri, 3 Jul 2015 01:11:59 +0200, Juan Francisco Cantero Hurtado
Thanks for your help!
I now have a build that works on my Qemu installation. The problem was
that the signal-handling stack installed via sigaltstack() was too
small. Making the stack 10*SIGSTKSZ bytes instead of SIGSTKSZ bytes
solves the problem.
In retrospect, it's clear how this is related to
Matthew Flatt mfl...@cs.utah.edu writes:
I was able to get an AArch64 installation running with Qemu, and I
think I've found the main problem with these failing builds.
The end of gc2.h has a preprocessor test for `__x86_64__` or `WIN64`,
but it should have been a more general test for
Racket builds fine on linux/ppc64 with your change.
The tests fail:
$ racket -f quiet.rktl
Section(basic)
TIMEOUT -- ABORTING!
On 07/03/2015 12:31 AM, Matthew Flatt wrote:
I was able to get an AArch64 installation running with Qemu, and I
think I've found the main problem with these failing
On Tue, Jun 30, 2015 at 02:44:46AM +0200, Juan Francisco Cantero Hurtado wrote:
Similar bug:
http://bugs.racket-lang.org/query/?cmd=view%20audit-traildatabase=defaultpr=15079
David, Debian has some machine with those architectures available to give
shell accounts to upstream developers?. I
On 06/29/2015 09:31 AM, David Bremner wrote:
Matthew Flatt mfl...@cs.utah.edu writes:
It looks like this patch was submitted for v6.1. Version 6.1.1 (the
current release), uses SGC instead of Boehm's GC during the build
process by default. So, it at least avoids this immediate problem.
I
12 matches
Mail list logo