Tiny Core Extensions > TCE Q&A Forum
x11vnc "path" to openssl doesn't match openssl location
bigpcman:
--- Code: ---could not find openssl(1) program in PATH.
(also checked: :/usr/bin:/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/sfw/bin)
could not find openssl(1) program in PATH.
(also checked: :/usr/bin:/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/sfw/bin)
31/01/2010 16:18:09 openssl_init: could not create or open saved PEM: (null)
--- End code ---
--- Code: --- tc@box2:/$ sudo find . -name "openssl"
./tmp/tcloop/openssl-0.9.8k/usr/local/openssl-0.9.8k/bin/openssl
./usr/local/openssl-0.9.8k/bin/openssl
--- End code ---
^thehatsrule^:
try something like:
--- Code: ---export PATH="${PATH}:/usr/local/openssl-0.9.8k/bin/openssl"
x11vnc
--- End code ---
bigpcman:
--- Quote from: ^thehatsrule^ on February 01, 2010, 02:48:35 PM ---try something like:
--- Code: ---export PATH="${PATH}:/usr/local/openssl-0.9.8k/bin/openssl"
x11vnc
--- End code ---
--- End quote ---
Yeah that's a good idea. I wonder if this should be added to the openssl startup script?
Jason W:
No, that should be done if needed on an extension by extension basis. And it would be done if needed by a wrapper script for the extension. Installing openssl into a directory that is not in $PATH is normal, and many programs will recognize an openssl not installed into $PATH. For those that don't, a wrapper script can be used.
bigpcman:
--- Quote from: Jason W on February 01, 2010, 06:26:50 PM ---No, that should be done if needed on an extension by extension basis. And it would be done if needed by a wrapper script for the extension. Installing openssl into a directory that is not in $PATH is normal, and many programs will recognize an openssl not installed into $PATH. For those that don't, a wrapper script can be used.
--- End quote ---
OK that makes sense.
So the x11vnc.tcz extension should be remade with a wrapper script.
Navigation
[0] Message Index
[#] Next page
Go to full version