---
title: Troubleshooting the PingID SSH installation on Solaris 10
description: Dealing with problems with Solaris 10.
component: pingid
page_id: pingid:pingid_integrations:pid_troubleshooting_ssh_installation_on_solaris_10
canonical_url: http://docs.pingidentity.com/pingid/pingid_integrations/pid_troubleshooting_ssh_installation_on_solaris_10.html
revdate: January 25, 2024
---

# Troubleshooting the PingID SSH installation on Solaris 10

Dealing with problems with Solaris 10.

If you are experiencing problems with Solaris 10, checking the following items may assist.

* Run the `pkginfo` command. The output might be helpful to find missing packages and for general investigation of Solaris hosts

* Check the console output and contents of `config.log` file produced during execution of the `./configure` script. It plays vital role in investigation of compilation/installation issues

* If you use `opencsw` repository to satisfy requirements of **PingID SSH**, then the **libcurl4**, **libcurl\_dev**,**libssl1\_0\_0**,**libssl\_dev**,**libcares\_dev**,**librtmp\_dev**,**libssh2\_dev**,**libkrb5\_dev**,**libbrotli\_dev** and **openldap\_dev** packages are mandatory (this list is far longer than the official requirements due to a bug in curl-config from `opencsw` repository). These libraries can be installed with the command:

  `/opt/csw/bin/pkgutil -y -i libcurl4 libcurl_dev libssl1_0_0 libssl_dev libcares_dev librtmp_dev libssh2_dev libkrb5_dev libbrotli_dev openldap_dev`

* `curl-config` allows the `./configure` script to locate **libcurl** dependencies and their location, so it is preferable to have the containing directory of `curl-config` in the **PATH** (for example, `/opt/csw/bin`). Solaris 11 hosts usually do not require any additional changes in this regard.

* If you use the `opencsw` repository it is preferable to install and use a more modern compiler, than default **GCC** which comes with the operating system. One such compiler can be installed with the `/opt/csw/bin/pkgutil -y -i gcc5core` command. Preference to the latter **GCC** over the original one is achieved by setting `/opt/csw/bin` ahead of `/usr/sfw/bin` in the command below:

  `export PATH=/usr/sbin:/usr/bin:/opt/csw/bin:/usr/ccs/bin:/usr/sfw/bin`

* If the **cURL** and **OpenSSL** libraries are installed outside of the default-search-path-for-libraries-during-linking (which are usually `/lib` and `/usr/lib`), then it is preferable to add this path via the LDFLAGS variable when calling the `./configure` script. For example, if these libraries are installed into `/opt/csw/lib`, the `./configure` command becomes:

  ```
  LDFLAGS="-L/opt/csw/lib"
  ./configure --with-pam --prefix=/usr
  ```