Eclipse executable launcher error: Unable to locate companion shared library

Question

I had Eclipse Indigo installed on my computer with the Android plugin and it was working perfectly for about two weeks. Today, I updated java and quicktime then restarted my

Answer 1

I also faced ths problem, I just deleted the extracted file and extracted it again.

I have a .rar file.

This problem occurs when the file is not extracted completely.

Answer 2

I have create Demo.exe using Eclipse RCP.

I have run Demo.exe using C-Drive to same error generate like...

Solution : You might changed your drive for example

 C:\Demo.exe to D:\Demo.exe

Step 1 : First Copy/Cut your .exe file like C:\Demo.exe

Step 2 : After Paste another drive like D:\Demo.exe

After executable file launching successfully.

I hope my answer is useful.

Answer 3

I had this issue on Linux (CentOS 7 64 bit) with 32-bit Eclipse Neon and 32-bit JRE 8. Non of the answers here or in similar questions were helpful, so I thought it can help someone.

Equinox launcher (eclipse executable) is reading the plugins/ directory and then searches for eclipse_xxxx.so/dll in org.eclipse.equinox.launcher.<os>_<version>/. Typically, the problem is in eclipse.ini pointing to the wrong version of Equinox launcher plugin. But, if the file system uses 64-bit inodes, such as XFS and one of the files gets inode number above 4294967296, then the launcher fails reading the plugins/ directory and this error message pops up. Use ls -li <eclipse>/plugins/ to check the inode numbers.

In my case, moving to another mount with 32-bit inodes resolved the problem.

See: http://www.tcm.phy.cam.ac.uk/sw/inodes64.html

Answer 4

Restart the machine. Solve your problem. Sometimes it happens when you are trying to restart the eclipse and in-between forcefully close it.

Answer 5

Check eclipse.ini, there are two entries like:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807

For some twisted reason jars have version in their name - so if you upgrade/have two different version of eclipse( while eclipse.ini is either linked or provided as system wide conf file for eclipse ) it will cause above error.

Answer 6

I faced this problem and solved it by running Eclipse as admin.