diff options
author | Richard Levitte <levitte@openssl.org> | 2000-07-11 21:44:53 +0000 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2000-07-11 21:44:53 +0000 |
commit | b364e5d27bb23433f5cbe3543add1ccdc0681006 (patch) | |
tree | 8d1c13989289d1c23af116641ba79f3c22ea8a12 | |
parent | 16ece03a2e46850dd5089ff1c820d125f82a53b0 (diff) |
FAQ about ar "missing" on Solaris.
-rw-r--r-- | FAQ | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -24,6 +24,7 @@ OpenSSL - Frequently Asked Questions * Why does the OpenSSL test fail with "bc: command not found"? * Why does the OpenSSL test fail with "bc: 1 no implemented"? * Why does the OpenSSL compilation fail on Alpha True64 Unix? +* Why does the OpenSSL compilation fail with "ar: command not found"? * Which is the current version of OpenSSL? @@ -368,3 +369,20 @@ This will only compile sha_dgst.c with -O0, the rest with the optimization level chosen by the configuration process. When the above is done, do the test and installation and you're set. + +* Why does the OpenSSL compilation fail with "ar: command not found"? + +Getting this message is quite usual on Solaris 2, because Sun has hidden +away 'ar' and other development commands in directories that aren't in +$PATH by default. One of those directories is '/usr/ccs/bin'. The +quickest way to fix this is to do the following (it assumes you use sh +or any sh-compatible shell): + +----- snip:start ----- + PATH=${PATH}:/usr/ccs/bin; export PATH +----- snip:end ----- + +and then redo the compilation. What you should really do is make sure +'/usr/ccs/bin' is permanently in your $PATH, for example through your +'.profile' (again, assuming you use a sh-compatible shell). + |