<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27;]]></title><description><![CDATA[<p dir="auto">Hi<br />
I'm trying to build a project on MacOS Tahoe 26.4 with Qt 6.11 and get the following error:</p>
<pre><code>/Users/gb/Qt/6.11.0/macos/lib/QtCore.framework/Headers/qyieldcpu.h:37:5: error: 
      implicitly declaring library function '__yield' with type 'void ()'
      [-Werror,-Wimplicit-function-declaration]
   37 |     __yield();              // Generic
      |     ^
/Users/gb/Qt/6.11.0/macos/lib/QtCore.framework/Headers/qyieldcpu.h:37:5: note: 
      include the header &lt;arm_acle.h&gt; or explicitly provide a declaration for
      '__yield'
</code></pre>
<p dir="auto">The sources of the application I am building come from a <a href="https://code.jsoftware.com/wiki/Guides/Compiling_Jqt/macOS" target="_blank" rel="noopener noreferrer nofollow ugc">project</a> that I do not own, therefore I am bound to use the components as they are with qmake/nmake. I was able to build the application with exactly the same source successfully with MacOSX26.2 and Qt 6.10.2 a few days ago.<br />
Apple published an update to MacOSX26.4 very recently - looking at other posts about this topic, I updated MacOS, XCode, XCode command line tools, reinstalled the entire Qt, erased all my source repository and replaced with a fresh one from the author (= the version which built successfully before).</p>
<p dir="auto"><strong>[ Edit ]</strong></p>
<p dir="auto">More precisely:</p>
<p dir="auto"><strong>1.</strong> Just after Mac updated to 26.4, I first got the error "no such sysroot" for which you find information on <a href="https://stackoverflow.com/questions/52385658/no-such-sysroot-directory-while-building-qt-project" target="_blank" rel="noopener noreferrer nofollow ugc">this (older) post</a>.</p>
<p dir="auto"><strong>2.</strong> I tried changing QMAKE_MAC_SDK (in the file common.pri of the project) and delete the .qmake.stash files (under main and lib folders), after which I got the current issue even before reinstalling QT - so the issue already appeared with QT 6.10.2.</p>
<p dir="auto"><strong>3.</strong> Only then I reinstalled everything before I submit this post, to make sure I hadn't corrupted anything in my own versions.</p>
<p dir="auto"><strong>[ Edit - End ]</strong></p>
<p dir="auto">I also searched for the header <em>arm_acle.h</em> listed in the error message - the only file with that name on my entire Mac appears only within an  Python Anaconda package which seems to be completely independent from QT or from the application I am building (which is in C++ btw).<br />
I'm quite new to the topic of building apps so it's difficult for me to narrow-down the steps to reproduce the issue.<br />
Just in case, here is the <a href="https://code.jsoftware.com/wiki/Guides/Compiling_Jqt/macOS" target="_blank" rel="noopener noreferrer nofollow ugc">full instruction</a> from the project's owner (the versions listed in the instruction are older, but the same methodology worked with MacOSX26.2 and QT 6.10.2).</p>
<p dir="auto">I would be very glad to hear of any hint to resolve this issue.</p>
]]></description><link>https://forum.qt.io/topic/164491/qmake-nmake-fails-on-macosx26.4-with-qt-6.11-with-error-implicitly-declaring-library-function-__yield</link><generator>RSS for Node</generator><lastBuildDate>Sun, 17 May 2026 14:02:58 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/164491.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 27 Mar 2026 08:47:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 10:18:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nw135">@<bdi>NW135</bdi></a> said in <a href="/post/837361">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">do you happen to know when (approximately) the fix will be made available through the online installer?</p>
</blockquote>
<p dir="auto">As you can see in the bug report it's fixed for 6.11.1 and 6.12</p>
<blockquote>
<p dir="auto">I don't feel able to incorporate this safely in my own installation,</p>
</blockquote>
<p dir="auto">It's just 5 lines in a header file: <a href="https://codereview.qt-project.org/c/qt/qtbase/+/725069" target="_blank" rel="noopener noreferrer nofollow ugc">https://codereview.qt-project.org/c/qt/qtbase/+/725069</a></p>
]]></description><link>https://forum.qt.io/post/837364</link><guid isPermaLink="true">https://forum.qt.io/post/837364</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Fri, 27 Mar 2026 10:18:19 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 11:46:17 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/christian-ehrlicher">@<bdi>Christian-Ehrlicher</bdi></a> said in <a href="/post/837364">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">As you can see in the bug report it's fixed for 6.11.1 and 6.12</p>
</blockquote>
<p dir="auto">... which means, according to <a href="https://wiki.qt.io/QtReleasing" target="_blank" rel="noopener noreferrer nofollow ugc">this page</a>, some time before September 2026.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/christian-ehrlicher">@<bdi>Christian-Ehrlicher</bdi></a> said in <a href="/post/837364">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">It's just 5 lines in a header file</p>
</blockquote>
<p dir="auto">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 <em>qyieldcpu.h</em> (the very same file and path provided in the compiler message) as follows (my changes are located before comments beginning with FIX):</p>
<pre><code>#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) &amp;&amp; defined(Q_CC_MSVC)
    _YIELD_PROCESSOR();     // Generic; MSVC's &lt;atomic&gt;
// ... 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
</code></pre>
<p dir="auto">I was able to test successfully on my own machine, yet no clue what this means and implies.</p>
<p dir="auto">I hope this information may be useful for other users in a similar situation.</p>
<p dir="auto">In any case, many thanks for the fast answer and the prompts which helped me address the concern.</p>
]]></description><link>https://forum.qt.io/post/837367</link><guid isPermaLink="true">https://forum.qt.io/post/837367</guid><dc:creator><![CDATA[NW135]]></dc:creator><pubDate>Fri, 27 Mar 2026 11:46:17 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 10:18:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nw135">@<bdi>NW135</bdi></a> said in <a href="/post/837361">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">do you happen to know when (approximately) the fix will be made available through the online installer?</p>
</blockquote>
<p dir="auto">As you can see in the bug report it's fixed for 6.11.1 and 6.12</p>
<blockquote>
<p dir="auto">I don't feel able to incorporate this safely in my own installation,</p>
</blockquote>
<p dir="auto">It's just 5 lines in a header file: <a href="https://codereview.qt-project.org/c/qt/qtbase/+/725069" target="_blank" rel="noopener noreferrer nofollow ugc">https://codereview.qt-project.org/c/qt/qtbase/+/725069</a></p>
]]></description><link>https://forum.qt.io/post/837364</link><guid isPermaLink="true">https://forum.qt.io/post/837364</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Fri, 27 Mar 2026 10:18:19 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 10:04:53 GMT]]></title><description><![CDATA[<p dir="auto">Thank you for pointing me to the recent bug report - for my convenience, do you happen to know when (approximately) the fix will be made available through the online installer?</p>
<p dir="auto">Reading the <a href="https://codereview.qt-project.org/c/qt/qtbase/+/724619" target="_blank" rel="noopener noreferrer nofollow ugc">fix description</a>, I don't feel able to incorporate this safely in my own installation, at least with my modest knowledge. Your recommendation is welcome whether I'm just missing some obvious piece of information or I should wait for a regular update.</p>
<p dir="auto">With "routine task", I was meaning "building a project" - agreed the versions are recent, but if I understand they are stable releases (not beta). This was just to explain why I didn't try this first hand - I understand also that your recommendation aimed at circumventing the issue.</p>
<p dir="auto">In fact, I put an edit in my initial post; the information I have tends to confirm that the issue was triggered by the recent MacOS update rather than QT 6.11, as stated in the bug description.</p>
]]></description><link>https://forum.qt.io/post/837361</link><guid isPermaLink="true">https://forum.qt.io/post/837361</guid><dc:creator><![CDATA[NW135]]></dc:creator><pubDate>Fri, 27 Mar 2026 10:04:53 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 09:31:28 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nw135">@<bdi>NW135</bdi></a> said in <a href="/post/837358">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">, I would not expect that it would be required to modify the QT's source for what should be a routine task.</p>
</blockquote>
<p dir="auto">What routine task? You're using a very recent toolchain which came out after 6.11.0 was tagged...<br />
It was just a try to see if it can be fixed locally as there is for sure already a bug report for it as you can see here: <a href="https://qt-project.atlassian.net/browse/QTBUG-145239" target="_blank" rel="noopener noreferrer nofollow ugc">https://qt-project.atlassian.net/browse/QTBUG-145239</a></p>
<p dir="auto">The fix is also trivial to add to your local Qt installation.</p>
]]></description><link>https://forum.qt.io/post/837359</link><guid isPermaLink="true">https://forum.qt.io/post/837359</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Fri, 27 Mar 2026 09:31:28 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 09:08:42 GMT]]></title><description><![CDATA[<p dir="auto">Many thanks for your prompt answer, this is appreciated.</p>
<p dir="auto">I didn't try from the beginning, because qyieldcpu.h is a file provided by the QT installer, I would not expect that it would be required to modify the QT's source for what should be a routine task.</p>
<p dir="auto">However, based on your hint, I just tried now and get a cascade of errors:</p>
<pre><code>/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:21:2: error: 
      "ACLE intrinsics support not enabled."
   21 | #error "ACLE intrinsics support not enabled."
      |  ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:60:9: error: 
      use of undeclared identifier '__builtin_arm_ldrex'; did you mean
      '__builtin_ia32_lddqu'?
   60 |     v = __builtin_arm_ldrex(__p);
      |         ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:60:29: error: 
      cannot initialize a parameter of type 'const char *' with an lvalue of
      type 'volatile uint32_t *' (aka 'volatile unsigned int *')
   60 |     v = __builtin_arm_ldrex(__p);
      |                             ^~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:61:10: error: 
      use of undeclared identifier '__builtin_arm_strex'
   61 |   while (__builtin_arm_strex(__x, __p));
      |          ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:91:3: error: 
      use of undeclared identifier '__builtin_arm_nop'; did you mean
      '__builtin_trap'?
   91 |   __builtin_arm_nop();
      |   ^~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:127:10: error: 
      use of undeclared identifier '__builtin_arm_clz'
  127 |   return __builtin_arm_clz(__t);
      |          ^~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:135:10: error: 
      use of undeclared identifier '__builtin_arm_clz64'
  135 |   return __builtin_arm_clz64(__t);
      |          ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:141:10: error: 
      use of undeclared identifier '__builtin_arm_clz64'
  141 |   return __builtin_arm_clz64(__t);
      |          ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:147:10: error: 
      use of undeclared identifier '__builtin_arm_cls'
  147 |   return __builtin_arm_cls(__t);
      |          ^~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:155:10: error: 
      use of undeclared identifier '__builtin_arm_cls64'
  155 |   return __builtin_arm_cls64(__t);
      |          ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:161:10: error: 
      use of undeclared identifier '__builtin_arm_cls64'
  161 |   return __builtin_arm_cls64(__t);
      |          ^~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:213:10: error: 
      use of undeclared identifier '__builtin_arm_rbit'
  213 |   return __builtin_arm_rbit(__t);
      |          ^~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:222:10: error: 
      use of undeclared identifier '__builtin_arm_rbit64'
  222 |   return __builtin_arm_rbit64(__t);
      |          ^~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:595:10: error: 
      use of undeclared identifier '__builtin_arm_crc32b'
  595 |   return __builtin_arm_crc32b(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:600:10: error: 
      use of undeclared identifier '__builtin_arm_crc32h'; did you mean
      '__builtin_ia32_crc32hi'?
  600 |   return __builtin_arm_crc32h(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:605:10: error: 
      use of undeclared identifier '__builtin_arm_crc32w'
  605 |   return __builtin_arm_crc32w(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:610:10: error: 
      use of undeclared identifier '__builtin_arm_crc32d'; did you mean
      '__builtin_ia32_crc32di'?
  610 |   return __builtin_arm_crc32d(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:595:10: note: 
      '__builtin_ia32_crc32di' declared here
  595 |   return __builtin_arm_crc32b(__a, __b);
      |          ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:615:10: error: 
      use of undeclared identifier '__builtin_arm_crc32cb'
  615 |   return __builtin_arm_crc32cb(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/21/include/arm_acle.h:620:10: error: 
      use of undeclared identifier '__builtin_arm_crc32ch'
  620 |   return __builtin_arm_crc32ch(__a, __b);
      |          ^~~~~~~~~~~~~~~~~~~~~
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
</code></pre>
<p dir="auto">Sounds like something that should be better placed in more expert hands than mine...</p>
]]></description><link>https://forum.qt.io/post/837358</link><guid isPermaLink="true">https://forum.qt.io/post/837358</guid><dc:creator><![CDATA[NW135]]></dc:creator><pubDate>Fri, 27 Mar 2026 09:08:42 GMT</pubDate></item><item><title><![CDATA[Reply to qmake&#x2F;nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function &#x27;__yield&#x27; on Fri, 27 Mar 2026 08:57:33 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nw135">@<bdi>NW135</bdi></a> said in <a href="/post/837355">qmake/nmake fails on MacOSX26.4 with Qt 6.11 with error implicitly declaring library function '__yield'</a>:</p>
<blockquote>
<p dir="auto">include the header &lt;arm_acle.h&gt;</p>
</blockquote>
<p dir="auto">Did you try what the compiler tells you? Add it to qyieldcpu.h</p>
]]></description><link>https://forum.qt.io/post/837356</link><guid isPermaLink="true">https://forum.qt.io/post/837356</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Fri, 27 Mar 2026 08:57:33 GMT</pubDate></item></channel></rss>