@Christian-Ehrlicher said in qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield':
As you can see in the bug report it's fixed for 6.11.1 and 6.12
... which means, according to this page, some time before September 2026.
@Christian-Ehrlicher said in qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield':
It's just 5 lines in a header file
When reading that same description, I was struggling at which file and which 5 lines to adjust, eventually I solved the issue on my own installation by editing qyieldcpu.h (the very same file and path provided in the compiler message) as follows (my changes are located before comments beginning with FIX):
#if __has_builtin(__builtin_arm_yield) // FIX moved from below and replaced elif by if
__builtin_arm_yield();
#elif __has_builtin(__yield) // FIX replaced if with elif
__yield(); // Generic
#elif defined(_YIELD_PROCESSOR) && defined(Q_CC_MSVC)
_YIELD_PROCESSOR(); // Generic; MSVC's <atomic>
// ... elided a few other unchanged lines here
#elif defined(Q_PROCESSOR_X86)
__asm__("pause"); // hopefully asm() works in this compiler
// FIX moved __has_builtin(__builtin_arm_yield to the top
I was able to test successfully on my own machine, yet no clue what this means and implies.
I hope this information may be useful for other users in a similar situation.
In any case, many thanks for the fast answer and the prompts which helped me address the concern.
