Eclipse Executable Cannot Find Companion Shared Library Error (Solution) [message #648867] |
Fri, 14 January 2011 18:56 |
No real name Messages: 1 Registered: January 2011 |
Junior Member |
|
|
I installed Eclipse for the first time and couldn't launch because of an error that says something like: "Eclipse launch executable could not find shared companion library."
I did a Google search for solutions and found many user complaints about the same problem, but no satisfactory solution.
People advised new users to do things like redownload the archive, re-extract the archive, re install JRE, change account permissions etc.
None of these actually solved the problem, and I found it didn't solve the problem for many of the users who had posted on various forums either.
After investigating for an hour or so I found that the problem occurs if you change the default name that the .zip archive extracts to. I believe the default name will be something like "eclipse-javascript-helios-SR1-win32-x86_64" or something analogous based on your specific platform. If you install into a directory with another name, like "eclipse", a default path somewhere in the installation breaks. Preserving the directory name gets rid of the problem.
I'm sure there is a configuration setting somewhere which you can probably change to fix this problem, but if you would rather not spend the time investigating, then renaming the directory is a shortcut that works.
|
|
|
Re: Eclipse Executable Cannot Find Companion Shared Library Error (Solution) [message #649753 is a reply to message #648867] |
Thu, 20 January 2011 14:23 |
Eric Rizzo Messages: 3070 Registered: July 2009 |
Senior Member |
|
|
On 1/14/11 1:56 PM, SpasticWilliams@gmail.com wrote:
> I installed Eclipse for the first time and couldn't launch because of an
> error that says something like: "Eclipse launch executable could not
> find shared companion library."
>
> I did a Google search for solutions and found many user complaints about
> the same problem, but no satisfactory solution.
>
> People advised new users to do things like redownload the archive,
> re-extract the archive, re install JRE, change account permissions etc.
>
> None of these actually solved the problem, and I found it didn't solve
> the problem for many of the users who had posted on various forums either.
>
> After investigating for an hour or so I found that the problem occurs if
> you change the default name that the .zip archive extracts to. I believe
> the default name will be something like
> "eclipse-javascript-helios-SR1-win32-x86_64" or something analogous
> based on your specific platform. If you install into a directory with
> another name, like "eclipse", a default path somewhere in the
> installation breaks. Preserving the directory name gets rid of the problem.
>
> I'm sure there is a configuration setting somewhere which you can
> probably change to fix this problem, but if you would rather not spend
> the time investigating, then renaming the directory is a shortcut that
> works.
While I appreciate your efforts to give back to this community by
providing information, I have to point out that your conclusion is
simply not correct. I ALWAYS install Eclipse into a custom-named
directory from the zip files, on both Windows and Mac OS X. Unless I've
misunderstood your "solution" I think something else must have changed
during your trials, because the zip file name has nothing to do with
Eclipse running.
The only thing I can think of from your description is that when you
extracted the zip previously, you did not preserve the directory
structure from the zip file (not the zip file name, but rather the
directories that are contained within it); doing that would definitely
cause things to break.
Eric
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06818 seconds