gwsocket
gwsocket copied to clipboard
" unrecognized option `--ssl-cert' "
sys: macOS Catalina[10.15.6]
openssl version: LibreSSL 2.8.3
follow =>
$ wget http://tar.gwsocket.io/gwsocket-0.3.tar.gz
$ tar -xzvf gwsocket-0.3.tar.gz
$ cd gwsocket-0.3/
$ ./configure --with-openssl=/usr/bin/openssl/
$ make
# make install
command ' gwsocket --ssl-cert=/path/to/my/ssl/cert --ssl-key=/path/to/my/ssl/key ' or ' gwsocket --ssl-cert /path/to/my/ssl/cert --ssl-key /path/to/my/ssl/key '
then failed with " unrecognized option `--ssl-cert' "
any thing wrong?
PS: here is my config.log config.log
Does it work without specifying the path? e.g.,
./configure --with-openssl
I have replicated this on Ubuntu 20,
when not using the path, the configure returns:
Linker flags : -lssl
TLS/SSL : yes
when not using the path (or using --with-openssl=yes
), the configure returns:
...
Linker flags : -lssl
TLS/SSL : yes
...
When using the path, it returns:
...
Linker flags :
TLS/SSL : /usr/bin/openssl
...
So I guess using the path is the wrong argument for that flag.
I stumbled here hopping that using the path would solve my issue, as I get the OpenSSL error when running make (#36).
Referencing #36
Any updates? Thanks
What is the fix for this?
I think one issue is libssl-dev is a dependency. Installing openssl alone does not achieve the expected result.
That's correct, since you are building from source, you need libssl-dev
.
Also, make sure to run make distclean
+ autoreconf -fiv
and then ./configure --with-openssl
+ make
after installing libssl-dev
.
Closing this. Feel free to reopen it if needed.
That's correct, since you are building from source, you need
libssl-dev
It would be helpful if that information was in the README. Installing openssl
alone still results in errors.
Also, make sure to run
make distclean
What does distclean
do?
BTW, thanks for this library. Finally got it working with https://github.com/ratboy666/qjs-ws.
distclean
will clean files that configure generated.
Glad it's working. Stay tuned as there are some fixes that I need to merge from goaccess' branch into gwsocket.
@guest271314 Take a look at what goaccess does here, may help with the ping.
@allinurl I deleted my comment re PING after re-reading this
Non-goals in the first version Exposing WebSocket pings and pongs to JavaScript.
Right now I am still working on using gwsocket in QuickJS. Unfortunately the machine froze yesterday streaming real-time audio.