Closed eniraa closed 2 years ago
It's not clear what Lavaplayer's requirements are so I wouldn't know what to list. That said, this is the first time I have seen a JVM crash involving Lavaplayer.
This seems to be an issue with the way that the jar
files are compiled—it's not really a problem with the code itself. People have made it work on non-glibc platforms.
I think the best way to approach this could be to note that the jars provided under the releases section (and in other sources) are usually glibc-based. Whether that means to say something about glibc under the requirements section or something else entirely is up to you.
For the record, since that link points to a message and a Lavalink.jar I made, I have a linux 64 bit musl native file for lavaplayer-natives and I didn't change the native loader any, and inserted that file in the appropriate native directory... no changes needed for Lavalink code.
I'm going to close this is essentially a feature request for lavaplayer and not lavalink
Description
Some operations crash Lavalink, such as changing the volume. This appears to be an issue involving C's standard library—specifically, there is no
musl
support.Since the README broadly mentions official support for Linux AMD64 using Zulu or OpenJDK, but makes no mention of C's stdlib, the README should probably be changed to reflect this?
Version info
Client used: lavalink-rs 0.9.0-rc.1
Output of
java -version
:Logs