Bug 174616 - Eclipse does not use native code on x86_64
Summary: Eclipse does not use native code on x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 176562
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-30 18:38 UTC by Robin Green
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-05 17:22:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robin Green 2005-11-30 18:38:31 UTC
Description of problem:
Eclipse runs fully interpreted on x86_64.

Version-Release number of selected component (if applicable):
eclipse-platform-3.1.1-1jpp_1fc.FC4.4

How reproducible:
Always

Steps to Reproduce:
1. Run eclipse
2. pmap `pidof gij`

Actual results:
No native libraries loaded apart from native libraries

Expected results:
Most of eclipse should be run natively

Additional info:
libgcj-4.0.2-8.fc4

A clue: gcj-dbtool -p says

/usr/lib/gcj-4.0.2/classmap.db

which does not exist!

Unfortunately, it's difficult to debug this with strace because doing so crashes
my machine so bad that only hitting the power button will make it wake up (and
shut down) :(

Comment 1 Robin Green 2005-11-30 18:41:31 UTC
This fixes the problem:

-Dgnu.gcj.precompiled.db.path=`gcj-dbtool -p /usr/lib64`

Comment 2 Andrew Overholt 2005-12-02 20:48:55 UTC
I thought gbenson had made a new java-gcj-compat that took care of different gcj
version numbers.  Gary?

Comment 3 Robin Green 2005-12-03 12:01:58 UTC
I don't think it's the gcj version number that's the problem. It's the fact that
the x86_64 build of libgcj is looking in /usr/lib for .db files instead of
/usr/lib64.

Comment 4 Gary Benson 2005-12-05 09:07:56 UTC
Certainly older versions of gcj were looking in /usr/lib instead of /usr/lib64,
on all multilib archs.  If it's still happening then you should file a bug
against gcc.

Comment 5 Robin Green 2006-01-05 17:22:00 UTC

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


Note You need to log in before you can comment on or make changes to this bug.