<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I dug a little deeper, I can confirm that this issue occurs when ffmpeg is being installed and it occurs whether or not the cache is used. It is already incorrectly linked in the image directory in the craft build directory for ffmpeg. It seems that the cause is that the install name is incorrect for two of the ffmpeg packages. Here is a piece of the build log for ffmpeg during the building of these libraries showing the two similar issues which then cause the aforementioned linking problem:<div class=""><br class=""></div><div class="">/usr/bin/clang -dynamiclib -Wl,-single_module -Wl,-install_name,/Users/rlancaste/AstroRoot/craft-root/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/rlancaste/AstroRoot/craft-root/lib/libavdevice.59.dylib,-current_version,59.4.100,</div><div class=""><br class=""></div><div class="">/usr/bin/clang -dynamiclib -Wl,-single_module -Wl,-install_name,/Users/rlancaste/AstroRoot/craft-root/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/rlancaste/AstroRoot/craft-root/lib/libavfilter.8.dylib,-current_version,8.24.100,</div><div class=""><br class=""></div><div class="">Here is one where the install name is correct, which means that it will then be fine when linked:</div><div class=""><br class=""></div><div class="">/usr/bin/clang -dynamiclib -Wl,-single_module -Wl,-install_name,/Users/rlancaste/AstroRoot/craft-root/lib/libavutil.57.dylib,-current_version,57.17.100,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">So, somehow either something in the code in the new version of ffmpeg for these two libraries is incorrectly giving them the wrong install name, or something is wrong with the recipe causing the same problem.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class=""></div><div class="">Rob<br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 14, 2022, at 4:07 PM, Robert Lancaster <<a href="mailto:rlancaste@gmail.com" class="">rlancaste@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I believe there was a commit that you made around that time that changed ffmpeg, but I can’t guarantee that this must be the cause.<div class=""><br class=""></div><div class=""><a href="https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/fe148aaee6d777e9e808a4613f942ec734516b7e" class="">https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/fe148aaee6d777e9e808a4613f942ec734516b7e</a></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 14, 2022, at 4:05 PM, Robert Lancaster <<a href="mailto:rlancaste@gmail.com" class="">rlancaste@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Hi Hannah,</span><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">Something changed in the craft build of FFMPEG between May 2nd and May 4th. We are now getting this error when packaging KStars on Binary Factory. <a href="https://binary-factory.kde.org/view/MacOS/job/KStars_Nightly_macos/" class="">https://binary-factory.kde.org/view/MacOS/job/KStars_Nightly_macos/</a></div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">The last successful build was May 2nd.</div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);"><pre class="" style="word-wrap: break-word; white-space: pre-wrap;">[2022-05-05T17:22:22.892Z] /Users/packaging/Craft/BinaryFactory/macos-64-clang/build/kde/applications/kstars/archive/Applications/KDE/kstars.app/Contents/Frameworks/libavdevice.59.4.100.dylib: don't know how to handle otool -L output: '/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib'</pre></div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">It looks to me like there is a linking issue. For some reason, the (nonexistent) path for libavfilter stored in libavdevice is:</div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);"><pre class="" style="word-wrap: break-word; white-space: pre-wrap;">'/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib'</pre><div class="">When it should be either </div></div><div class="" style="caret-color: rgb(0, 0, 0);"><pre class="" style="word-wrap: break-word; white-space: pre-wrap;">/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib</pre><pre class="" style="word-wrap: break-word; white-space: pre-wrap;">Or </pre><pre class="" style="word-wrap: break-word; white-space: pre-wrap;">@rpath/libavfilter.8.dylib</pre><div class="">In fact all the other ffmpeg dylibs are linked like this:</div><div class=""><span class="" style="white-space: pre-wrap;"><br class=""></span></div><div class=""><span class="" style="white-space: pre-wrap;">/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib</span></div><div class=""><div class=""><br class=""></div></div><div class="">It is just that one that is wrong.</div></div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">Was there some sort of craft change which would break this?</div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">Thanks,</div><div class="" style="caret-color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0);">Rob</div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></body></html>