All,
For RHEL and RedHat 9, the GLIBC versions are very similar, both 2.3.2. It
is more than likely that compatibility will not be an issue for us:
RedHat 9.0
[root@saturn root]# rpm -q glibc
glibc-2.3.2-27.9.7
RHEL
[root@venus etc]# rpm -q glibc
glibc-2.3.2-95.3
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of Mark
Taylor
Sent: 15 April 2004 18:43
To: [log in to unmask]
Subject: Re: GLIBC_2.3
On Thu, 15 Apr 2004, Alasdair Allan wrote:
> Ah, slight problem!
>
> I just did a CVS checkout and rebuilt my StarJava, ran up FROG to check
> Peter's changes, and go the following when I tried to open a file...
>
> java.lang.UnsatisfiedLinkError: couldn't load library jniast:
> /work/starlink/java/lib/i386/libjniast.so: /lib/libc.so.6: version
> `GLIBC_2.3' not found (required by
/work/starlink/java/lib/i386/libjniast.so)
>
> ...
>
> So pretty much nothing currently works for me. It's unlikely I can get my
> OS upgraded to use this new glibc in time for a freeze on Monday.
>
> Why do we require a newer version of glibc now? What's changed?
The JNIAST i386 lib in the repository hasn't changed since 22 March:
% cvs log jniast/src/lib/i386/jniast_libs.jar
RCS file: /cvs/java/source/jniast/src/lib/i386/jniast_libs.jar,v
Working file: jniast/src/lib/i386/jniast_libs.jar
head: 1.7
branch:
locks: strict
access list:
symbolic names:
jniast-V3-2-4: 1.6
keyword substitution: b
total revisions: 7; selected revisions: 7
description:
----------------------------
revision 1.7
date: 2004/03/22 16:04:00; author: mbt; state: Exp; lines: +2502 -2670
Updated to AST V3.2-8 (just involved a new method FitsChan.putCards -
bit pointless since it's only there for CFITSIO compatibility, but
kind of easier to do it than to document it as the one unimplemented
method in JNIAST).
...
so if you're seeing behaviour different now from a (deinstall, clean, build,
install) installation since then, there's something funny going on.
Otherwise, looks like you've got a system not compatible with the JNIAST
shared libraries I built, which was on RH9. You can work round this
by doing an
ant build-native
prior to the normal build, install step in JNIAST. (May need to do the
same in JNIHDS). This will write newly built custom shared libs in
jniast/src/lib/jniast_libs.jar - don't commit these back to the
repository please.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|