Thanks so much for your response and help. Now, instead of just applying the entitlements on the app bundle, I applied it on all the bundled binaries (postgres, pg_ctl, etc), .so and the dependent .dylibs (using codesign -f -i <> -s <> --options runtime --entitlements <list>) and now the extension loads successfully.I was also wondering if I need to use 10.14SDK to compile the binaries and .dylibs, to fix this issue, but that doesn't seem be the case now. Thanks.
Post
Replies
Boosts
Views
Activity
Hi,When I overwrite the old binaries with the newer one, I get "Killed: 9" error: Bad executable (or shared library)" when I execute any binary that has a dependecy on .dylib. The binaries that just depends on "/usr/lib/libSystem.B.dylib" works fine. When I reboot the machine, then all the binaries work fine and no error is seen.Do I need to flush dylib cache or any other cache to avoid the reboot? Or How can I fix it please?Thank you.
I too seeing the same issue.When I overwrite the old binaries with the newer one (with additional entitlements), I get "Killed: 9" error: Bad executable (or shared library)" when I execute any binary that has a dependecy on .dylib. The binaries that just depends on "/usr/lib/libSystem.B.dylib" works fine. When I reboot the machine, then all the binaries work fine and no error is seen.Do I need to flush dylib cache or any other cache to avoid the reboot? Or How can I fix it please?
Could you please eleborate? We create postgresql-12.2-1-osx.dmg and postgresql-12.2-1-osx.zip that includes the .app bundle. When you install the app bundle it will extract the executables, .so's and dependent .dylib'sSince we codeisgn each binary and .so, I made a change to add --entitlements and rebuilt a new version of DMG (postgresql-12.2-2-osx.dmg). Now, when I install this new DMG which overwrites executables and .so's.
I believe installer upgrades follow Option A. Because the new installer (DMG) carries the new builds and get overwritten in the same location where the older files exist on disk. But, let me confirm from the Bitrock team and get back.
yes, you were right. That was the problem. The installer tool fixed the issue and now after the upgrade installation is done, the binaries work fine. Thanks so much for explaining the problem.
OK, This seems to be Qt issue on macOS BigSur and the suggested work-around is to export QTMACWANTS_LAYER=1