Matthew Flatt <[email protected]> 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 > `SIXTY_FOUR_BIT_INTEGERS`. > > With that repair, the AArch64 build still fails for me due to a GC > problem. If I disable generational GC, then the build seems ok. I think > I've had trouble in the past, where the signal handlers that implement > the write barrier didn't work correctly inside Qemu. The problem might > not be Qemu-specific, though, and I'm interested to hear whether the > "gc2.h" change to use `SIXTY_FOUR_BIT_INTEGERS` fixes the problem on > real machines.
looks like not qemu specific ? This is on a real (AMD X-Gene Mustang) amd64 machine: racket/racket3m -X "/home/bremner/racket-6.2/debian/tmp/usr/share/racket/collects" -G "/home/bremner/racket-6.2/debian/tmp/etc/racket" -N "raco" -l- setup --no-user -j --no-launcher --no-install --no-post-install raco setup: bootstrapping from source... SIGSEGV MAPERR si_code 1 fault on addr 0x4000 Aborted Makefile:160: recipe for target 'install-3m' failed make[2]: *** [install-3m] Error 134 make[2]: Leaving directory '/home/bremner/racket-6.2/build' d -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/878uaxgbq4.fsf%40maritornes.cs.unb.ca. For more options, visit https://groups.google.com/d/optout.
