Re: Looping around allocGlobals()
Belated follow up on this. I haven't had time to submit a support case, but I did narrow down the problem further.
Turns out there was a call to a function that had been removed from the project, but for some reason this was not reported at all during the build process - it would just churn for about 30-40 seconds and then terminate with the "Looping around allocGlobals" error.
The function was prototyped as follows, which might be a clue:
void Displayprintf(uchar cmd, const rom char *format, ...);
If I changed that definition to:
void Displayprintf(uchar cmd, const rom char *format, uint data);
and built the project, I got the expected
"error: (499) undefined symbol _Displayprintf"
So, my guess is that linker has some difficulty recognizing a missing function when it uses a variable argument list.
I will try to put together a small project that illustrates this and get it submitted next week.