Updated needed for newer OpenSSL / newer Asio

[eddelbuettel]

@QuLogic opened issue 14 over at my AsioHeaders repo as an update appears needed for OpenSSL 4 as seen in the freshest Fedora release.

So I prepared a release candidate AsioHeader 1.38.4-0, based on the newest / current stable Asio headers releases. It passes with two of its CRAN reverse dependencies, but croaks for websocket. There is an older alias io_service in use here which Asio already deprecated in release 1.33 (!!).

Could team websocket please look into an update from your side? I would expect CRAN to come knocking eventually anyway.

My release candidate of AsioHeaders is at https://dirk.eddelbuettel.com/tmp/AsioHeaders_1.38.4-0.tar.gz for your persusal, and in the corresponding branch.

Thanks in advance for your consideration.

PS Subject corrected. It's OpenSSL, not curl, that bites.

[QuLogic]

There's one use of this symbol in the code:

websocket/src/client.hpp

Line 158 in 0681923

ws_websocketpp::lib::asio::io_service& get_io_service() {

but there are several in the bundled websocketpp library (one of the reasons I asked in #59, as our system copy has this fixed already.) Fixing the bundled websocketpp will require cross-porting zaphoyd/websocketpp#1164.

[jeroen]

I think we might also get around this by adding CFLAGS -DOPENSSL_API_COMPAT=0x10101000L

[eddelbuettel]

The offending line 158 listed above by @QuLogic will have to go though as the identifier simply no longer exists in Asio.

[QuLogic]

I think @jeroen is suggesting that by setting the flag, we won't have to update AsioHeaders yet. Unfortunately, I tried adding it to the build here and it still fails.