Hi With suse 7.3 I used to run Splus 6.1 with GUI without problem. Now with suse 9.2 I have received this error message: " nogueira@harvey:~> Splus -g Error occurred during initialization of VM. Unable to load native library: /home/nogueira/splus61/java/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference" I have glibc version 2.3.3-118.i586 installed and I found libc.so.6 in 3 locations: " harvey:~ # find / -name "libc.so.6" -print /lib/tls/libc.so.6 /lib/i686/libc.so.6 /lib/libc.so.6 " Thanks for your help Eduardo -- Prof. Eduardo A Nogueira Professor Associado Laboratório de Cateterismo Cardíaco Disciplina de Cardiologia Departamento de Clínica Médica Faculdade de Ciências Médicas Universidade de Campinas
On Tuesday 12 April 2005 3:50 pm, Eduardo A Nogueira wrote:
Hi
With suse 7.3 I used to run Splus 6.1 with GUI without problem. Now with suse 9.2 I have received this error message: " nogueira@harvey:~> Splus -g Error occurred during initialization of VM. Unable to load native library: /home/nogueira/splus61/java/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference"
I have glibc version 2.3.3-118.i586 installed and I found libc.so.6 in 3 locations: " harvey:~ # find / -name "libc.so.6" -print /lib/tls/libc.so.6 /lib/i686/libc.so.6 /lib/libc.so.6 " My thoughts is that there is a backwards compatibility issue with the version of the jre supplied with Splus6.1. You might check Insightful's support database. http://www.insightful.com/insightful_faq/search.asp
--
Jerry Feldman
On Tue, Apr 12, 2005 at 04:50:50PM -0300, Eduardo A Nogueira wrote:
Hi
With suse 7.3 I used to run Splus 6.1 with GUI without problem. Now with suse 9.2 I have received this error message: " nogueira@harvey:~> Splus -g Error occurred during initialization of VM. Unable to load native library: /home/nogueira/splus61/java/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference"
I have glibc version 2.3.3-118.i586 installed and I found libc.so.6 in 3 locations: " harvey:~ # find / -name "libc.so.6" -print /lib/tls/libc.so.6 /lib/i686/libc.so.6 /lib/libc.so.6 "
The workaround is documented in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109388
(and with errors in http://www.novell.com/coolsolutions/feature/11775.html,
which I reported to Novell, but they haven't fixed the page)
To make the long story short, run the following in your shell:
gcc -O2 -shared -o ~/libcwait.so -fpic -xc - <
Kastus
To make the long story short, run the following in your shell:
gcc -O2 -shared -o ~/libcwait.so -fpic -xc - <
#include #include #include pid_t [...] Then use LD_ASSUME_KERNEL=2.4.19 LD_PRELOAD=~/libcwait.so to start buggy JDK.
Or, much better yet, use a newer JDK which doesn't use internal library symbols which aren't visible to the outside anymore. Philipp
On Wed, Apr 13, 2005 at 12:53:12AM +0200, Philipp Thomas wrote:
Then use LD_ASSUME_KERNEL=2.4.19 LD_PRELOAD=~/libcwait.so to start buggy JDK.
Or, much better yet, use a newer JDK which doesn't use internal library symbols which aren't visible to the outside anymore.
I see your point and totally agree with it but sometimes we are locked by vendors, e.g. Veritas, to use the JDK from the vendor, or otherwise the application (e.g. jnbSA) does not work. -Kastus
Kastus
but sometimes we are locked by vendors, e.g. Veritas, to use the JDK from the vendor, or otherwise the application (e.g. jnbSA) does not work.
What was that slogan for Java? Write once, run everywhere? Doesn't necessarily seem to be the case :) Philipp
Philipp, On Wednesday 13 April 2005 01:54, Philipp Thomas wrote:
Kastus
[Tue, 12 Apr 2005 15:58:36 -0700]: but sometimes we are locked by vendors, e.g. Veritas, to use the JDK from the vendor, or otherwise the application (e.g. jnbSA) does not work.
What was that slogan for Java? Write once, run everywhere? Doesn't necessarily seem to be the case :)
We (Java developers) haven't heard or uttered that slogan in quite a while. Not even Sun is saying it any more. That said, Java has far more portability than C/C++. You'll not find any "configure" stage in building a Java package nor will you find any #if ... #endif in the source code (since there is no pre-processor in Java, though some few projects have adopted the use of a non-standard one). MacOS X and Linux users actually have it pretty good (the Mac especially, since the user needn't even opt to install the Java runtime--it's a stock part of the platform) whereas Windows people need to go and procur a separate installer to be able to run Java software. Because of this, some programs are available with a bundled Java runtime.
Philipp
Randall Schulz
participants (5)
-
Eduardo A Nogueira
-
Jerry Feldman
-
Kastus
-
Philipp Thomas
-
Randall R Schulz