Why is there no libJOCL_2_0_4-linux-arm64.so?

[ashesfall]

I've switched to arm64 to support Apple, and its awesome to see libJOCL_2_0_4-apple-arm64.dylib in the jar, but what about libJOCL_2_0_4-linux-arm64.so?

I need this to work on linux also, and I don't see why it wouldn't - save for this being missing.

[gpu]

Nobody provided it. I can not (easily or reasonably) build the binaries for all possible combinations of operating systems and architectures. You can compile the native library on your own, as described at https://github.com/gpu/JOCL#building-the-native-libraries , and put the native library into your project root directory (it should be picked up from there, usually).

If someone is willing to contribute pre-built binaries for other architectures, then they can be integrated into future releases as well. (There is no timeline for specific updates for the near future, but in doubt, I could create a Maven release with the additional library, if someone provided it)

[ashesfall]

I will try and build it and contribute it back. Thank you for providing aarch anyway that one was very useful.

[ashesfall]

I've deployed an arm64 VM and installed the relevant tools, I should be able to supply the lib back to the project this week.

@gpu what version of the JDK should I build it against?

CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find JNI (missing: JAVA_AWT_LIBRARY JAVA_JVM_LIBRARY
  JAVA_INCLUDE_PATH JAVA_INCLUDE_PATH2 JAVA_AWT_INCLUDE_PATH)

[gpu]

I don't know whether that makes any difference. I guess it's just OpenJDK? Maybe @blueberry can give a hint here.

[blueberry]

I don't know. I've never used arm64, nor do I have a computer with that architecture.

[gpu]

what version of the JDK should I build it against?

Do you have a JDK installed right now (and not only a JRE)?

(I think that CMake should be able to figure out these paths automatically, but that might not be the case here, depending on where/how exactly it was installed...)

[ashesfall]

@gpu @blueberry Its a fresh VM, I didn't want to have any chance of contamination for a library that other people may rely on.

I can install any jdk version really, even jdk 8 is available on arm64. The question is just about the java version that the other libraries were compiled against. If you used the header files from jdk 10, for example, for all the other libs - I would install jdk10. If it really doesn't matter, I will install jdk17.

[ashesfall]

And to be clear, I would be using openjdk for versions 10 or above, and oracle jdk for version 9 and below. But the header files are essentially part of the specification, I don't think the vendor of the jdk is relevant - only the version.

[gpu]

The version may be a relevant point here. Usually, in terms of compatibility, it's good to use "the lowest version that works". To be honest, I never thought about where and how the JDK version comes into play for JOCL (that's the good thing with Java - it usually "just works"...). But I'd like to avoid a situation where someone has Java 10, and JOCL bails out due to some dependency to a newer Java version. If it works with JDK 8 (which I'm still using, by the way), then it could/should be that.

[ashesfall]

I built it on arm using jdk 8.

[ec2-user@ip-172-31-54-246 ~]$ arch
aarch64

[ec2-user@ip-172-31-54-246 ~]$ cmake --build jocl-build
[  7%] Building CXX object JOCLCommon/CMakeFiles/JOCLCommon.dir/src/main/native/Logger.cpp.o
[ 15%] Building CXX object JOCLCommon/CMakeFiles/JOCLCommon.dir/src/main/native/CLJNIUtils.cpp.o
[ 23%] Building CXX object JOCLCommon/CMakeFiles/JOCLCommon.dir/src/main/native/JNIUtils.cpp.o
[ 30%] Building CXX object JOCLCommon/CMakeFiles/JOCLCommon.dir/src/main/native/PointerUtils.cpp.o
[ 38%] Building CXX object JOCLCommon/CMakeFiles/JOCLCommon.dir/src/main/native/ConversionsCL.cpp.o
[ 46%] Linking CXX static library libJOCLCommon.a
[ 46%] Built target JOCLCommon
[ 53%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/JOCL.cpp.o
[ 61%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/CLFunctions.cpp.o
[ 69%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/FunctionPointerUtils.cpp.o
[ 76%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/FunctionPointerUtils_Linux.cpp.o
[ 84%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/FunctionPointerUtils_Win.cpp.o
[ 92%] Building CXX object CMakeFiles/JOCL_2_0_4-linux-x86_64.dir/src/main/native/Sizeof.cpp.o
[100%] Linking CXX shared library /home/ec2-user/JOCL/nativeLibraries/libJOCL_2_0_4-linux-x86_64.so
[100%] Built target JOCL_2_0_4-linux-x86_64

@gpu @blueberry but for some reason its labeled as x86_64. is this a known issue?

[ec2-user@ip-172-31-54-246 ~]$ objdump -f /home/ec2-user/JOCL/nativeLibraries/libJOCL_2_0_4-linux-x86_64.so

/home/ec2-user/JOCL/nativeLibraries/libJOCL_2_0_4-linux-x86_64.so:     file format elf64-littleaarch64
architecture: aarch64, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x0000000000000000

[gpu]

The "x86_64" part is only part of the file name, used for disambiguating (the specific combination of Linux+Arm is not yet covered at

JOCL/CMakeLists.txt

Line 44 in fefa66d

if(ANDROID)

)

So it should be OK to just rename that file. It would be important to know what

String osArch = System.getProperty("os.arch");

returns on such a system, to make sure that the name matches what is computed at

JOCL/src/main/java/org/jocl/LibUtils.java

Line 580 in fefa66d

private static ArchType calculateArch()

[ashesfall]

It emits the same value as shown in my response above:

[ec2-user@ip-172-31-54-246 ~]$ cat Test.java
public class Test {
	public static void main(String args[]) {
		System.out.println(System.getProperty("os.arch"));
	}
}

[ec2-user@ip-172-31-54-246 ~]$ java Test
aarch64

I assume I can fork the repo where this is located, and open a pull request? Where are the native libs located?

The correct name should be:

libJOCL_2_0_4-linux-arm64.so 

is that right?

[ashesfall]

I have uploaded the library to dropbox so that you can include it in a future release if you are able:

https://www.dropbox.com/s/fzm9mc83ynfchs1/libJOCL_2_0_4-linux-arm64.so?dl=0

[gpu]

Thanks @ashesfall - there wasn't a release planned, but I'll schedule some time for an update, and integrade the new binary with that.

[ashesfall]

@gpu thank you. this repository does not appear to be participating in github sponsors. If there is another way to support the project let me know.