Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 427827 - Cannot launch Luna M5 on OSX via ./eclipse
Summary: Cannot launch Luna M5 on OSX via ./eclipse
Status: RESOLVED DUPLICATE of bug 424769
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.4   Edit
Hardware: Macintosh Mac OS X
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 12:32 EST by Max Rydahl Andersen CLA
Modified: 2014-02-13 05:47 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Max Rydahl Andersen CLA 2014-02-10 12:32:50 EST 
I download Luna M5 of OSX 64
Untar it
cd eclipse
./eclipse

Result is a dialog that shows up stating:
"The Eclipse executable launcher was unable to locate its  companion shared library."

Launching Kepler or any other previous version of eclipse works fine (tells me that it is not about a missing JDK or something similar)
Comment 1 Max Rydahl Andersen CLA 2014-02-10 12:36:39 EST 
Just noticed that I can run Luna by launching "open Eclipse.app". 

The workspace comes up blank though.
Comment 2 Max Rydahl Andersen CLA 2014-02-10 12:50:52 EST 
I have a faint recollection of reporting this similar where the cause was I hadn't enabled osx to run apps outside app store.

But I have setup to allow apps downloaded from anywhere.
Comment 3 David Williams CLA 2014-02-10 13:29:15 EST 
Can you give exact URL; and package you downloaded. 

My guess is you downloaded EPP "standard" package, in which case, this would be a dup of bug 424769. 

I've confirmed this "works for me" ... so if its not an EPP package, my second question would be "how did you untar it?"
Comment 5 David Williams CLA 2014-02-13 05:47:34 EST 
Known issue in EPP Packages

*** This bug has been marked as a duplicate of bug 424769 ***