macOS: undefined SSL symbols in curl.a on x64

[artificiel]

i am building a project on a Mac M1 that must run on Intel, so turning"Build Native Architecture Only" to "NO".

it's been working fine until "recently". I'm not compiling that constantly so I can't pinpoint more precisely but with git OF and a fresh download_libs it fails to link with a bunch of undefined symbols all relating to lib curl.

for instance trying to compile imageLoaderWebExample:

etc...

reverting libs/curl/lib/osx/curl.a to an earlier version (I had one dated April 20 2023) fixes the problem.

maybe "something else" is going on here but I unfortunately can't debug more proactively on intel right now but I wanted to raise this immediately.

[artificiel]

PS the lib seems legit fat:

% file curl.a
curl.a: Mach-O universal binary with 2 architectures: [x86_64:current ar archive] [arm64:current ar archive]
curl.a (for architecture x86_64):	current ar archive
curl.a (for architecture arm64):	current ar archive

[danoli3]

Looks like it was no successfully compiled with openssl

…

On Sat, 16 Sept 2023 at 17:28, alexandre burton ***@***.***> wrote: PS the lib seems legit fat: % file curl.a curl.a: Mach-O universal binary with 2 architectures: [x86_64:current ar archive] [arm64:current ar archive] curl.a (for architecture x86_64): current ar archive curl.a (for architecture arm64): current ar archive — Reply to this email directly, view it on GitHub <#7656 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGK2HGVWNYBQMBCFIDZUMLX2VIIBANCNFSM6AAAAAA42WSZS4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ofTheo]

Hmm. Does this happen with the official 0.12.0 release too? As in the packaged version here: https://github.com/openframeworks/openFrameworks/releases/download/0.12.0/of_v0.12.0_osx_release.zip Can you cause the issue with any of the examples?

[artificiel]

Above is with an example: imageLoaderWeExample

[artificiel]

will test later today with release

[ofTheo]

So just tried with the imageLoaderWebExample in 0.12.0 release and it works fine for me.
But the nightly build does not and produces the errors you mention.

Definitely a regression then.

[ofTheo]

Okay I think its tied to this change ( by me ;) )
https://github.com/openframeworks/apothecary/pull/280/files

I can fix this as setting the deployment target to 10.15 or even 11.0 doesn't seem to make the error go away.

[artificiel]

yes i confirm on i7: fresh 0.12 works fine, the machine had a few months old git which i pulled to HEAD without running the udpdate_libs and it still worked; after updating libs it broke. notwithstanding fixing the issue, adding that example to the tests would be good to cover the curl stuff.

(i changed the title as the M1/non-native architecture thing is an irrelevant parameter)