Problems with included native library on FreeBSD, potentially others

Abierto
#604 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
java
Área
backend

Línea de trabajo

Start by locating the code that selects and extracts the platform-specific native library from the JAR; the issue does not name a file or test. Check how native libraries installed outside the JAR could be discovered and loaded on FreeBSD, while preserving the bundled library as a fallback. Done means an installed native library is used when available and the bundled one remains the fallback; add tests for both paths.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

I have stumbled upon a problem when using a snappy-java library bundled with a software package.

In my case my operating system is FreeBSD 14.1. The bundled native library seems to be much older, trying to link to the non existant libstdc++.so.6.

I have noticed that as a default snappy-java determines which native library it will need (in this case, FreeBSD) and unpacks it from the .jar file to a temporary directory. I have just started the program and the file name is:

/tmp/snappy-1.1.10-3a114908-1cf9-4b6e-a1b2-620bc8b26ea9-libsnappyjava.so

As I am using FreeBSD I have compiled snappy-java from ports myself (trivial task) and it installs two libraries:

snappyjava-1.1.10.5:
	/usr/local/lib/libsnappyjava.so. (the locally compiled native library)
	/usr/local/share/java/classes/snappy-java.jar

So, I think it would be ideal to:

  1. Check whether there is a native library installed. If present, link to it.
  2. If there is no native library, then use the bundled one as a last resort measure.

What do you think?

Lenguaje dominante
Java
Estrellas
1.1k
Forks
261
Merge medio
2 min
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de xerial/snappy-java

Todos los issues de xerial/snappy-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.