Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    When installing an APK, it automatically extracts the libraries of the right arch type and has them available for System.loadLibrary. But, if you're trying to load a non-standard library, the installer won't know your app has 32bit native code.

  2. ,

    This is a sub-class of the LinkageError class and indicates that the JVM cannot find an appropriate native-language definition of a method declared as native. Compile a 64-bit version of your .dylib file.

Solutions on the web

via GitHub by andronix3
, 1 year ago
C:\Users\andro\.rootbeer\rootbeer_cuda_x64.dll: Can't find dependent libraries
via Oracle Community by 843829, 2 years ago
C:\dlls\manufacturing.dll: Can't find dependent libraries
via Coderanch by Alan Shiers, 1 year ago
C:\PNS_1.0\PersonalNetSearch\native\some.dll: Can't find dependent libraries
via Stack Overflow by user1379574
, 9 months ago
C:\jni_training\Hello World.dll: Can't find dependent libraries
java.lang.UnsatisfiedLinkError: C:\Users\andro\.rootbeer\rootbeer_cuda_x64.dll: Can't find dependent libraries	at java.lang.ClassLoader$NativeLibrary.load(Native Method)	at java.lang.ClassLoader.loadLibrary0(Unknown Source)	at java.lang.ClassLoader.loadLibrary(Unknown Source)	at java.lang.Runtime.load0(Unknown Source)	at java.lang.System.load(Unknown Source)	at org.trifort.rootbeer.runtime.CUDALoader.doLoad(CUDALoader.java:93)	at org.trifort.rootbeer.runtime.CUDALoader.load(CUDALoader.java:86)	at org.trifort.rootbeer.runtime.Rootbeer.(Rootbeer.java:15)	at org.trifort.rootbeer.entry.Main.printDeviceInfo(Main.java:222)	at org.trifort.rootbeer.entry.Main.run(Main.java:187)	at org.trifort.rootbeer.entry.Main.main(Main.java:244)