- This topic has 18 replies, 10 voices, and was last updated 18 years, 4 months ago by
.
-
Posts
-
Hi guys,
I’m trying to install MyEclipseEnterpriseWorkbenchInstaller_5_0M1_E3_2.bin on my suse 10.1 system.
But I’ll get always:MyEclipseEnterpriseWorkbenchInstaller_5_0M1_E3_2.bin Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory /bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Launching installer... grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory /u/opt/jdk1.6.0/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directoryIt’s not 64 bit.
Same behavior with sun jdk1.4.2_11, jdk1.5.0_07 and jdk 1.6.0Any ideas?
The problem is this line in the installer:
export LD_ASSUME_KERNEL=2.2.5
If you do not run a 2.2.x kernel, you cannot start anything after this line.
Problem: The script tries to run a command afterwards to find out if the kernel is “vulnerable” to some old bug and that command can’t be run anymore…
Solution: Run these commands:
export LAX_DEBUG=1 sh -x MyEclipseEnterpriseWorkbenchInstaller_5_0M2_E3_2.binAfter dumping a whole lot of output and errors, you will see a line like this:
exec /tmp/install.dir.867/Linux/resource/jre/bin/java -Djava.compiler=NONE -Xmx268435456 -Xms67108864 com.zerog.lax.LAX /tmp/install.dir.867/temp.lax /tmp/env.properties.867 /tmp/install.dir.867/Linux/resource/jre/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directorySince the installer crashed, it won’t delete the installer files! All you have to do is to run it manually:
n=867 export CLASSPATH=/tmp/install.dir.$x/InstallerData:/tmp/install.dir.$x/InstallerData/installer.zip: /etc/alternatives/java_sdk_1.5.0/bin/java -Xmx268435456 -Xms67108864 com.zerog.lax.LAX /tmp/install.dir.$x/temp.lax /tmp/env.properties.$xReplace “867” with the number after “install.dir.” from above and /etc/alternatives/java_sdk_1.5.0/bin/java with the correct path to your Java 1.5 installation and it should work!
Franky,
I’d suggest downloading and installing 5.0 M2 that we released today. We bundled the proper JVM in it (just for the installer to use) so getting it to work should be quite simple this time.
Bundling the JVM with ME won’t help when the installer script prevents newly created processes (like awk or java) to load the necessary shared libraries from disk 🙂
Demetrio,
We’d like to get some more information on this so we can discuss the problem with ZeroG (the makers of InstallAnywhere) so if you can provide us a little more detail on “how” the installer fails, that would be very helpful. Internally, we test the installers on RHEL 4, and they work correctly there, so this issue must be local to Suse and we don’t have a test machine for that distro at the moment.
Can you set the environment variable LAX_DEBUG=1 and then retry the installer? If it fails, can you please email the log output plus a URL to this thread to us at support at myeclipseide.com. Once we have that, we can work to resolve the errors for the next build so others won’t encounter the same issue.
Hi, I did the steps digulla said and it worked…
I’m using Suse 10.1 with no strange changes to kernel or PATHs or other things….
Here the output with DEBUG:
========= Analyzing UNIX Environment ================================= Setting UNIX (linux) flavor specifics. Importing UNIX environment into LAX properties. Checking for POSIX awk. ========= Analyzing LAX ============================================== LAX found............................ OK. LAX properties read.................. OK. ========= Finding VM ================================================= Valid VM types.......................... J2 Absolute LAX_VM path.................... /tmp/install.dir.23837/Linux/resource/jre/bin/java Expanded Valid VM types................. JRE_J2 JDK_J2 * Using VM.....(lax.nl.current.vm)...... /tmp/install.dir.23837/Linux/resource/jre/bin/java checking for NPTL + JVM vulernability... NPTL detected! checking for vulnerable JVM.... awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory major : minor : patch : vendor: Vulnerable JVM detected... implementing workaround ========= Virtual Machine Options ==================================== LAX properties incorporated............. OK. classpath............................... "/tmp/install.dir.23837/InstallerData:/tmp/install.dir.23837/InstallerData/installer.zip" main class.............................. "com.zerog.ia.installer.Main" .lax file path.......................... "/tmp/install.dir.23837/temp.lax" user directory.......................... "/tmp/install.dir.23837" stdout to............................... "console" sterr to................................ "console" install directory....................... "" JIT..................................... none option (verify)......................... off option (verbosity)...................... none option (garbage collection extent)...... none option (garbage collection thread)...... none option (native stack max size).......... none option (java stack max size)............ none option (java heap max size)............. 268435456 option (java heap initial size)......... 67108864 option (lax.nl.java.option.additional).. none dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory /bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory ========= Display settings =========================================== hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory X display............................... local UI mode................................. gui Launching installer... ========= VM Command Line ============================================ options: -Djava.compiler=NONE -Xmx268435456 -Xms67108864 CLASSPATH:/tmp/install.dir.23837/InstallerData:/tmp/install.dir.23837/InstallerData/installer.zip:/tmp/install.dir.25942/InstallerData:/tmp/install.dir.25942/InstallerData/installer.zip: grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory ========= Forking JAVA ============================================= /tmp/install.dir.23837/Linux/resource/jre/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directoryAll,
Thanks for your help running this down. We’ve now opened a support ticket with Macrovision to help address the issue on SUSE Linux as soon as possible.
I’ve heard back from Macrovision. They don’t currently support Ubuntu, SUSE 10, or Fedora Core 5. They also cannot comment on when support
for those distributions will be available. RHEL 4 works great, if you’ve got that, however.I’ve made this thread sticky in the hopes others will see it. I’ll also recommend that we relabel our Linux installer to a RHEL installer to avoid
missed expecations in the future.I got the same problem on FC5. This is a typical issue with Install Anywhere. The typical solution is :
cat MyEclipseEnterpriseWorkbenchInstaller_5_0M2_E3_2.bin | sed ‘s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/g’ > install.bin
then run sh ./install.bin
works for me…. YMMV
Greg,
Can you please apply the patch from albiii to the installer? RedHat 4 is so old that you a) probably can’t find it anywhere anymore and b) if you could, you couldn’t get a java version for it which is recent enough to run Eclipse.
Regards,
Aaron,
Redhat Enterprise Linux 4 is the official reference platform for Eclipse so it forms the basis of all of our testing for MyEclipse and the installers for Linux. We run the very latest JDK on Redhat4 as well so that isn’t the issue. We do realize that for many people Redhat 4 doesn’t use the latest packages so we also test on Ubuntu 6.06 and our installer runs fine. I don’t think you will find a more up-to-date distribution thatn Ubuntu 6.06, so the problem that some people are having must be related to something else. We will investigate this patch but we must be careful not to break the install for Redhat and Ubuntu systems.
