AMIGASYSTEMDistro MaintainerPosted
9 months agoIt seems that the Guru in question is generated by the GCC, see attached video:
You do not have access to view attachments
AMIGASYSTEMDistro MaintainerPosted
10 months agoI tried increasing the stack, but nothing changed. I am using Build 68k v11 from deadwood.
I also tried the updated Build 68k from ‘aros.sourceforge.io’, but it was even worse: the ROMs do not work, and GCC is not executable!
amigamiaAdminPosted
10 months agoDid you try to increase the stack in the shell before running the compiler?
The issue seems to be very similar to when I was experimenting with compiling OpenTyrian. Increasing the stack seemed to have worked.
Edited by amigamia on 17-10-2025 06:56,
10 months ago
AMIGASYSTEMDistro MaintainerPosted
10 months ago
I tried compiling some simple sources for AROS 68k, see screenshot, GCC 10.5.0. included on AROS 68k works, but if you try to compile complex sources, a Guru appears that should concern RAM.
The Guru appears in these cases:
- Compile large sources cause Guru or WinUAE restart
- If you close the Shell after typing GCC
- The Make command is case sensitive.
Now I don't know if this Guru might depend on WinUAE, we would need to test GCC on a different Amiga emulator or on native Amigas with modern expansions.
You do not have access to view attachments