Skip to content

Commit

Permalink
Adding brew link workaround to known issues document
Browse files Browse the repository at this point in the history
  • Loading branch information
Zlatko Knezevic authored Jul 21, 2016
1 parent 9516bda commit 6fd4047
Showing 1 changed file with 14 additions and 1 deletion.
15 changes: 14 additions & 1 deletion cli/known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,20 @@ sudo port upgrade openssl
sudo port -f uninstall openssl @0.9.8
```

You can verify whether you have the right version using the `openssl version` command from the Terminal.
You can verify whether you have the right version using the `openssl version` command from the Terminal.

## Problems using `brew` to link `openssl` after uprading
Some users have reported problems when using `brew link --force openssl` command to link the upgraded OpenSSL. The error reported is a variation of the below:

```console
Linking /usr/local/Cellar/openssl/1.0.2h_1...
Error: Could not symlink share/man/man5/config.5ssl /usr/local/share/man/man5 is not writable
```

This is due to permissions being set in a certain way on the `/usr` directory on El Capitan. In order to workaround this problem, you need to give your user ownership of the directory and its contents. More information can be found on the following links:

* http://blog.blakesimpson.co.uk/read/89-fix-homebrew-error-usr-local-bin-is-not-writable-on-os-x-el-capitan
* http://stackoverflow.com/questions/26647412/homebrew-could-not-symlink-usr-local-bin-is-not-writable

## Running .NET Core CLI on Nano Server

Expand Down

0 comments on commit 6fd4047

Please sign in to comment.