It looks like the oracle installer is using a JVM compiled with a really old version of GLIBC. Is there any way to make the installer use a different JVM, something like the 1.4.2 that's compiled for RHL 9 ? If the installer uses the "installshield" class, you can use the parameters "-is:javahome /path/to/jdk" Obviously you will have to first download an appropriate jdk. However, if the Oracle installer doesn't use InstallShild, that won't help. Also, is there a compat-glibc to provide backwards compatibility in Severn? The package list shows a compat-libstdc++ but I can't seem to find a compat-glibc... hmm. --Jeremy On Thu, 2003-07-24 at 07:40, Igor Gorbounov wrote: > There was a workaround to handle the Oracle obsoleteness for install under > RH9.0: > LD_ASSUME_KERNEL=2.2.5;./runInstaller > but it doesn't work any more in RH 9.093: > Initializing Java Virtual Machine from > /tmp/OraInstall2003-07-24_03-17-12PM/jre/bin/java. Please wait... > Error occurred during initialization of VM > Unable to load native library: > /tmp/OraInstall2003-07-24_03-17-12PM/jre/lib/i386/libjava.so: symbol > __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link > time reference > > So anybody has perhaps found some way out of this situation? > Hopefully, > Igor Gorbounov > > > > -- > Rhl-beta-list mailing list > Rhl-beta-list redhat com > http://www.redhat.com/mailman/listinfo/rhl-beta-list -- /---------------------------------------------------------------------\ | Jeremy Portzer jeremyp pobox com trilug.org/~jeremy | | GPG Fingerprint: 712D 77C7 AB2D 2130 989F E135 6F9F F7BC CC1A 7B92 | \---------------------------------------------------------------------/
Attachment:
signature.asc
Description: This is a digitally signed message part