all goes well with building on Mac OS 10.15.6 until the make hits variable for x86_64 architecture, see below. Claws starts but is severely handicapped, not all plugins available even though the early configure steps recognized and placed them in the plugins directory. "_SecTrustGetCertificateAtIndex", referenced from: _mailstream_low_cfstream_get_certificate_chain in libetpan.a(mailstream_cfstream.o) "_SecTrustGetCertificateCount", referenced from: _mailstream_cfstream_set_ssl_enabled in libetpan.a(mailstream_cfstream.o) _mailstream_low_cfstream_get_certificate_chain in libetpan.a(mailstream_cfstream.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: *** [claws-mail] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 alex@Alex-MacBook-Pro claws-mail-3.17.6 % /usr/local/Cellar/claws-mail/3.17.6/etc/mime.types: claws_fopen: No such file or directory (claws-mail:21868): Gtk-WARNING **: 22:30:55.678: Attempting to store changes into `/Users/alex/.local/share/recently-used.xbel', but failed: Failed to create file “/Users/alex/.local/share/recently-used.xbel.IHYXN0”: No such file or directory (claws-mail:21868): Gtk-WARNING **: 22:30:55.678: Attempting to set the permissions of `/Users/alex/.local/share/recently-used.xbel', but failed: No such file or directory [1] + done /usr/local/Cellar/claws-mail/3.17.6/bin/claws-mail alex@Alex-MacBook-Pro claws-mail-3.17.6 %
A couple of things: - I think you should use gcc for building Claws Mail, not clang, but you're free to try, of course ;-) - The missing symbol comes from libetpan, so it's probably a bug of that library. - I don't understand how you can get a binary to run if the linker fails to do its job, unless the errors you posted are mixed from two different build attempts. - "Not all plugins available" can be a nice summary, but doesn't help much. If you're reporting some bug be more specific, please. If not, please subscribe to devel@ list and lets discuss there.