Created attachment 799145 [details] The build log The new 3.0.0 version fails while building due to a fatal error since the JNI component do not find the "system/Allocators.h" file. > > FAILED: librubberband-jni.so.p/src_jni_RubberBandStretcherJNI.cpp.o > x86_64-pc-linux-gnu-g++ -m32 -Ilibrubberband-jni.so.p -I. -I../rubberband-3.0.0 -I../rubberband-3.0.0/rubberband -I../rubberband-3.0.0/src -I/opt/openjdk-bin-11.0.15_p10/include -I/opt/openjdk-bin-11.0.15_p10/include/linux -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++11 -O3 -O2 -pipe -march=haswell -msse4 -msse4.1 -msse4.2 -mcx16 -fomit-frame-pointer -mfpmath=sse -msahf -w -flto=8 -fPIC -pthread -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DHAVE_LIBSAMPLERATE -DNO_THREAD_CHECKS -DNO_TIMING -DNDEBUG -DUSE_PTHREADS -DHAVE_POSIX_MEMALIGN -MD -MQ librubberband-jni.so.p/src_jni_RubberBandStretcherJNI.cpp.o -MF librubberband-jni.so.p/src_jni_RubberBandStretcherJNI.cpp.o.d -o librubberband-jni.so.p/src_jni_RubberBandStretcherJNI.cpp.o -c ../rubberband-3.0.0/src/jni/RubberBandStretcherJNI.cpp > ../rubberband-3.0.0/src/jni/RubberBandStretcherJNI.cpp:26:10: fatal error: system/Allocators.h: No such file or directory > 26 | #include "system/Allocators.h" > | ^~~~~~~~~~~~~~~~~~~~~ > In the attachments the complete build log and the 'emerge --info' output. Regards, Iade Gesso, PhD
Created attachment 799147 [details] emerge --info output
A small update... the issue appears only when the jni use flag is enabled. Disabling it makes the build process successfully complete. Iade
Hi, I had the same problem, and I fixed it with the patch from ArchLinux: https://raw.githubusercontent.com/archlinux/svntogit-community/packages/rubberband/trunk/rubberband-3.0.0-jni_allocators_include.patch For those who prefer the "sed" command: sed -i -e "s:\#include \"system\/Allocators.h\":\#include \"..\/common\/Allocators.h\"::\" \ src/jni/RubberBandStretcherJNI.cpp || echo "damn it!" With either of them (the patch or the "sed" command), the "jni" flag can be raised(enabled) :) !
Created attachment 799625 [details, diff] Fix compiling with jni flag enabled
we don't have this version of the package anymore. i tested that with 3.2.1 and the issue did not pop up so closing this bug. if for some reason the issue still persists then please update this bug.