Author Topic: Did not find libGLESv2.so libGLESv2.so  (Read 3093 times)

Offline m44miri

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Did not find libGLESv2.so libGLESv2.so
« on: May 21, 2014, 04:35:44 am »
I installed ubuntu image on the Cubieboard 1, after running the java -jar JavaFXApplication1.jar
I see this message.
Did not find libGLESv2.so libGLESv2.so: cannot open shared object file: No such file or directory
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000, pid=1011, tid=2793178224
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) Client VM (25.0-b70 mixed mode linux-arm )
# Problematic frame:
# C  0x00000000
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /opt/hs_err_pid1011.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
root@linaro-alip:/opt# java -jar JavaFXApplication1.jar
Did not find libGLESv2.so libGLESv2.so: cannot open shared object file: No such file or directory
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000, pid=1046, tid=2793874544
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) Client VM (25.0-b70 mixed mode linux-arm )
# Problematic frame:
# C  0x00000000
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /opt/hs_err_pid1046.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

how can i solve it?