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

Bug 295545

Summary: need compatibility package on build.eclipse.org
Product: Community Reporter: David Williams <david_williams>
Component: ServersAssignee: Eclipse Webmaster <webmaster>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: john.arthorne
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description David Williams CLA 2009-11-18 23:48:41 EST
For IBM's PPC VM to run on the build machine's 64 bit architecture, a "compatibility" package is required. Apparently. Currently, if I try and run a 64 bit VM, just to get the "version" then and error occurs immediately: 


david_williams@build:/shared/webtools/apps/ibm-java-ppc64-606/bin> ./java
-version

dl failure on line 739Error: failed
/opt/public/webtools/apps/ibm-java-ppc64-606/jre/lib/ppc64/j9vm/libjvm.so,
because libstdc++.so.5: cannot open shared object file: No such file or
directory 


See 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=295394#c13 
for an outline of the cure. 


I'll also point out there is an oddly named symbolic link in /shared/common. 
It is named ibm-java2-ppc64-50 
but it actually points to a 32 bit VM. 
Fine with me if that's what was intended, but didn't want anyone to be "fooled" by the name. 

I have no urgent, immediate need to run a 64 bit VM ... but, sometime I'd like to experiment with using is for certain parts of the build. Not for the increased memory allowed (just so you can relax :) but I've heard file I/O (such as for compiling) can be faster ... so, just thought I'd experiment to see ... some day, when I get some free time.
Comment 1 David Williams CLA 2010-03-04 00:51:24 EST
fixed by bug 299819. see also bug 301625.

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