Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354786

Summary: On Ubuntu 11.04 (Mint 11), using 32 bit SDK, 64 bit libraries are found instead of 32 bit
Product: [Eclipse Project] Platform Reporter: David Williams <david_williams>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: RESOLVED NOT_ECLIPSE QA Contact:
Severity: normal    
Priority: P3 CC: steffen.pingel
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
syserr capture from console while starting up eclipse (and hitting a few menus, like preferences) none

Description David Williams CLA 2011-08-15 22:10:03 EDT
Created attachment 201534 [details]
syserr capture from console while starting up eclipse (and hitting a few menus, like preferences)

This may well be "not eclipse" ... but, here's the background and story. 

Using 32 bit java and eclipse works fine on Ubuntu 10x, on both 32 and 64 bit Ubuntu, and continues to on Ubuntu 11.04 32 bit, but on Ubuntu 11.04 64 bit, it seems the 64 bit libraries are "found" before the 32 bit ones and produces lots of GTK errors on syserr. (sample attached). I did not actually "see" anything wrong with the UI, except initial splash screen was too small. But figure something is off. 

I opened this Eclipse bug because I have seen an Ubuntu bug (behavior and entry) with similar error messages logged, and it was closed as "won't fix", claiming the problem was fundamentally with the "apps" being built incorrectly, and specifying architecture, where no-architecture would have been appropriate. 
(Though they acknowledged an underlaying change that caused the change ... apparently they "hacked around it" in the Ubuntu 10x versions, but didn't want to continue to). 

See
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/783155

(Note, technically, I am actually using Mint 11 ... but ... similar to Ubuntu 11.04.) 

Now, I could very easily be reading way too much into the similarities of log messages, but thought it would worth to write this down, and bring to your attention, since if it is a "build issue", now would be the time to fix it.  

Well, that, plus the idea that if anyone could "reply" to the Ubuntu bug in a meaningful way, it would be the swt team :) [I personally just half understand what they are talking about ... but the problem is a real pain when only a 32 but version of an app exists ... glad I can use 64 bit java and eclipse for real work ... but, thought I'd let you know of the issue, if you didn't know already.] 

I hope this bug report is helpful. Feel free to close as "not eclipse" if really is something quirky about Ubuntu. Well, that, or "invalid" ... I am fairly sure the intent is that 32 bit java and eclipse should work just fine on 64 bit architectures, but let me know if I have misunderstood.  

Thanks, 

P.S. the attached log comes from testing with Eclipse 4.2 M1, but saw similar messages with 4.1 release.
Comment 1 David Williams CLA 2011-10-01 13:22:46 EDT
I tried reproducing after installing the "squeeze version" of ia32 libs,

amd64/ia32-libs
amd64/ia32-libs-gtk

as mentioned in comment 21 of the bug referenced in comment #0. 
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/783155/comments/21

and there were no longer these messages in the console (and, the splash logo was the right size), 

so I think fair to conclude "not eclipse" (and not an issue of how eclipse natives compiled). 

There were, still, messages  about incorrect "linkages", similar to below, but nothing as bad as it was, 
and ... I'm guessing ... these may be due to my now "patched together" (mismatched) system. 

/usr/lib/gio/modules/libgiobamf.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgiobamf.so
Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64
(eclipse:7230): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64

So, with luck, as updates are made downstream based on squeeze versions, these issues will all disappear too (or, be different bugs).