You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Alex Remily (Jira)" <ji...@apache.org> on 2022/05/19 01:02:00 UTC
[jira] [Commented] (CRYPTO-132) Instructions in BUILDING.txt don't work on MacOS
[ https://issues.apache.org/jira/browse/CRYPTO-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539145#comment-17539145 ]
Alex Remily commented on CRYPTO-132:
------------------------------------
I realize this is an ancient thread, but I think this issue should be replaced by one that specifies a full update to the build process documentation that includes a dockerfile based on the 1.1.0 release process.
> Instructions in BUILDING.txt don't work on MacOS
> ------------------------------------------------
>
> Key: CRYPTO-132
> URL: https://issues.apache.org/jira/browse/CRYPTO-132
> Project: Commons Crypto
> Issue Type: Bug
> Components: Build
> Reporter: Benedikt Ritter
> Priority: Major
>
> When using HomeBrew to link openssl with the --force, HomeBrew refuses to do this, indicating that our docs are not following best practices:
> {code}
> ~/w/a/c/commons-crypto git:(upstream ⚡ CRYPTO-131) 1A > brew link openssl --force
> Warning: Refusing to link: openssl
> Linking keg-only openssl means you may end up linking against the insecure,
> deprecated system OpenSSL while using the headers from Homebrew's openssl.
> Instead, pass the full include/library paths to your compiler e.g.:
> -I/usr/local/opt/openssl/include -L/usr/local/opt/openssl/lib
> {code}
> Adapt the build so that it is no longer necessary to use link --force on MacOs
--
This message was sent by Atlassian Jira
(v8.20.7#820007)