Bug 321201 - Eclipse fails to launch on x86_64 (wrong ELF class)
Summary: Eclipse fails to launch on x86_64 (wrong ELF class)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-06 08:10 UTC by Eric LANDES
Modified: 2007-11-30 22:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-18 18:24:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Eclipse log file (2.44 KB, text/plain)
2007-10-06 08:10 UTC, Eric LANDES 		no flags Details
View All

Description Eric LANDES 2007-10-06 08:10:38 UTC 
Description of problem:
Eclipse fails to launch on x86_64

Version-Release number of selected component (if applicable):
$ rpm -q eclipse-jdt
eclipse-jdt-3.2.2-15.fc7

How reproducible:
Always

Steps to Reproduce:
1. yum install eclipse-jdt.x86_64
2. Launch Eclipse through the main menu or with /usr/bin/eclipse

Actual results:
It shows a message box : An error has occured. See the log file
/home/user/workspace/.metadata/.log

Log file indicates java.lang.UnsatisfiedLinkError for libswt-pi-gtk-3236.so
(wrong ELF class: ELFCLASS64)

Additional info:
$ uname -a
Linux pc-linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux

See attached file for a complete log
Comment 1 Eric LANDES 2007-10-06 08:10:38 UTC 
Created attachment 218301 [details]
Eclipse log file
Comment 2 Andrew Overholt 2007-10-18 13:28:49 UTC 
Sorry I didn't comment on this sooner.  It appears you've got a 32-bit JVM and
64-bit eclipse.
Comment 3 Eric LANDES 2007-10-18 17:48:33 UTC 
Ok, it's right. I had to install a 32-bit jvm for a software I installed
manually and which requires such a jvm. 
So the bug is invalid.
Comment 4 Andrew Overholt 2007-10-18 18:24:31 UTC 
Cool.
Note You need to log in before you can comment on or make changes to this bug.