-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executable no longer statically linked #211
Comments
Indeed, Unfortunately, there are no real tests for Websocat, so each release may introduce regressions. Now investigating how to restore staticness. |
Dynamicness originates from built-in OpenSSL. Here is a version of Websocat without TLS support, if this is enough for you. |
Here is another attempt to build for websocat.arm-unknown-linux-musleabi.zip If this is a |
I am interested in this, but can confirm segmentation fault on my Raspberry Pi 2.
|
Here is a Websocat executable for Raspberry Pi 2 (using system openssl): It is enough? |
I don't personally need secure websockets, but I was interested in some of the changes introduced in 1.13. What do I need installed for this, exactly?
|
Probably Here is a version with a static openssl that is hopefully more portable: And here is one without TLS support: They are not static, but built on Raspbian Jessie, so should work fine with RPi2. |
First link seems to work, thanks! |
The file websocat.arm-unknown-linux-musleabi used to be statically linked in V11, but in V12, it is now dynamically linked, which does not work on several of the legacy systems I have tried it on.
As an example, the dynamic linker mentioned in the V12 file is /usr/lib/ld.so.1, but on one of my systems, the actual (incompatible) dynamic linker is /lib/ld-linux-armhf.so.3 on another system it's /lib/ld-linux.so.3.
So I'd just appreciate if (on the next release, perhaps), you could reintroduce a version for arm that is statically linked.
The text was updated successfully, but these errors were encountered: