> On Feb 22, 2021, at 13:38, nicolas bats <sl1200...@gmail.com> wrote:
>
> Hi Jeremy,
> sorry for my late reply I only got access to macOS10.9 today...
> using 2.8.0_rc1, installation is fine, well done :)
>
> now when linking my app I got this error:
> -- 35/64: fixing up
> '/Users/nico/build/myApp.app/Contents/Frameworks/libX11.6.dylib'
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:
> for architecture arm64 object:
> /Users/nico/build/myApp.app/Contents/Frameworks/libX11.6.dylib malformed
> object (unknown load command 9)
> CMake Error at /usr/local/share/cmake-3.19/Modules/BundleUtilities.cmake:905
> (message):
> Command failed:
>
> '/usr/bin/install_name_tool' '-change' '/opt/X11/lib/libxcb.1.dylib'
> '@executable_path/../Frameworks/libxcb.1.dylib' '-id'
> '@executable_path/../Frameworks/libX11.6.dylib'
> '/Users/nico/build/myApp.app/Contents/Frameworks/libX11.6.dylib'
> Call Stack (most recent call first):
> /usr/local/share/cmake-3.19/Modules/BundleUtilities.cmake:980
> (fixup_bundle_item)
> cmake_install.cmake:209 (fixup_bundle)
>
>
> make: *** [install] Error 1
>
> it seems that install_name_tool does not like arm64.
It's not that install_name_tool doesn't like arm64, it's that this old
install_name_tool does not understand the new LC_BUILD_VERSION load command in
that slice:
Load command 9
cmd LC_BUILD_VERSION
cmdsize 32
platform 1
minos 11.0
sdk 11.3
ntools 1
tool 3
version 609.8
The arm64 slices are encoded with a minimum version of macOS 11.0 (since that's
the first version to support macOS 11.0), which means we can use the newer /
more-agile LC_BUILD_VERSION load command instead of the platform-specific one
(LC_VERSION_MIN_MACOSX).
> is it something I need to deal with or something that you can deal with?
Why are you embedding these libraries into your project?
Can you instead build them from source for your project?
You'll need to do this on a newer version of macOS that has a toolchain that
understand how to handle the LC_BUILD_VERSION load command. I *think* that
was Xcode 10 on macOS 10.13, but I could be wrong.
> best regards,
> nicolas
>
> Le lun. 22 févr. 2021 à 21:17, Jeremy Huddleston Sequoia <jerem...@apple.com
> <mailto:jerem...@apple.com>> a écrit :
>
>
>> On Feb 22, 2021, at 06:06, Peter Dyballa <peter_dyba...@freenet.de
>> <mailto:peter_dyba...@freenet.de>> wrote:
>>
>>
>>> Am 17.2.2021 um 22:34 schrieb Jeremy Huddleston Sequoia <jerem...@apple.com
>>> <mailto:jerem...@apple.com>>:
>>>
>>> Hey Peter, can you explain what you mean by this? There are quite a number
>>> of default client apps in /opt/X11/bin
>>
>> I just missed to see this! (And I should put this directory into search
>> path.)
>
> PATH should be setup correctly by the default shell initialization scripts.
> XQuartz installs /etc/paths.d/40-XQuartz which is used by /etc/profile and
> /etc/zprofile:
>
> if [ -x /usr/libexec/path_helper ]; then
> eval `/usr/libexec/path_helper -s`
> fi
>
>
>>
>> --
>> Greetings
>>
>> Pete
>>
>> "Debugging? Klingons do not debug. Our software does not coddle the weak."
>>
>>
>>
>>
>> _______________________________________________
>> Xquartz-dev mailing list
>> Xquartz-dev@lists.macosforge.org <mailto:Xquartz-dev@lists.macosforge.org>
>> https://lists.macosforge.org/mailman/listinfo/xquartz-dev
>> <https://lists.macosforge.org/mailman/listinfo/xquartz-dev>
>>
>
>
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev@lists.macosforge.org <mailto:Xquartz-dev@lists.macosforge.org>
> https://lists.macosforge.org/mailman/listinfo/xquartz-dev
> <https://lists.macosforge.org/mailman/listinfo/xquartz-dev>
>
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/xquartz-dev
