https://bugs.documentfoundation.org/show_bug.cgi?id=172033
--- Comment #8 from Patrick (volunteer) <[email protected]> --- OK. I did a "make distclean" and rebuilt master with the ./configure command arguments (except for the --with-external-tar or --srcdir arguments) in the following nightly build log: https://ci.libreoffice.org/job/lo_daily_tb_mac_arm64/lastBuild/consoleFull I can still reproduce this bug in the 12 May 2026 nightly build but not in the .dmg built with the same nightly build ./configure command arguments. So I compared the output of "otool -L Contents/Frameworks/libmergedlo.dylib" in both installations and found the following: - /Users/tdf/lode/jenkins/workspace/lo_gerrit/tb/build_master/workdir/UnpackedTarball/fontconfig/src/.libs/libfontconfig.1.dylib (compatibility version 18.0.0, current version 18.1.0) + /Volumes/LOBuilds/lode/dev/core/workdir/UnpackedTarball/fontconfig/src/.libs/libfontconfig.1.dylib (compatibility version 18.0.0, current version 18.1.0 >From the above, I think the build is linking libfontconfig.1.dylib in the wrong location. The reason LibreOffice launches in my locally built .dmg is that the "/Volumes/LOBuilds/.../libfontconfig.1.dylib" path exists in my machine's build. I would think the otool -L output should be "@loader_path/libfontconfig.1.dylib" instead of an absolute path like all of the other *.dylib files in the installation's Contents/Frameworks folder. Let me see if I can find where the build does the @loader_path stuff. I am guessing there is a list of *.dylib files somewhere in the build that libfontconfig.1.dylib needs to be added to. -- You are receiving this mail because: You are the assignee for the bug.
