Void-packages: vscode: live share plugin from market place needs openssl to work

[lalincedeldeserto]

System

• xuname:
  output of xuname (part of xtools)
  Void 4.19.45_1 x86_64 GenuineIntel uptodate rrFF

• package:
  affected package(s) including the version
  vscode live-share from microsoft (search into vscode market place)

I installed correctly from the marketplace live-share plugin but it doesn't start because it needs openssl.

File log:
liveshare-log.zip

A screenshot to the extension:

[Duncaen]

Not sure what we can or do about it, this is third party code installed from a third party package manager.

Edit: And this seems to be closed source, even if we would try to help, it wouldn't be possible.

[Johnnynator]

https://github.com/MicrosoftDocs/live-share
@Duncaen seems MIT licensed to me :)

@lalincedeldeserto the issue you opened there is still relevant and was wrongly closed https://github.com/MicrosoftDocs/live-share/issues/1936

Nothing we can do about this.

[lalincedeldeserto]

Thank you guys, I hope someone would solve the problem in the nearest future :smile:
@Johnnynator thank you for having modified the tag in my report issue :+1:
I know this is a third party software so it's not easy to solve because as @Duncaen said, it's closed source (I thought that it was entirely opened :disappointed_relieved: )

[lalincedeldeserto]

@Johnnynator , @Duncaen
There's a little trick to may it work, but I haven't proofed any connection.
Thanks to a person, the solution may be this:
open a terminal and paste:
sudo ln -s libssl.so.46 /usr/lib/libssl.so.1.0.0
using symbolic links to emulate the library

[Johnnynator]

There is no guaranteed on ABI compatibility between LibreSSL and OpenSSL, if it would work now it could break after every LibreSSL update.

[vdo]

This fixes the issue in my environment (Void Linux with libressl)

export CLR_OPENSSL_VERSION_OVERRIDE=46

[obunden]

@Johnnynator Can this issue be closed since it can't be solved on our end?

[lalincedeldeserto]

Dear @obunden, the problem still remains not solved. I don't think there's a standard solution to be applied. The only thing you can do is to turn around the problem through some tricks (that may not work because of some incompatibilities).
This issue cannot be solved because, if I'm not wrong, the source codes of this module aren't opened.
So I leave this post in the hands of the administrators.