this tells the library (DSO) which libc.so.6 version is required,
it's not hard linked ..
this detail is produced while compiling the DSO,
and hence a compilation generated detail.
in our case this simply depends on the machine setup we use to
produce the DSO's .. hence it could be possible that one day we ask for
a higher libc.so.6 .. so we should keep an eye on such compatibilities.
> This problem does not happen with JogAmp. Is it statically linked to glibc?
> Otherwise, how does it use glibc?
On Tuesday, August 02, 2011 04:02:21 PM gouessej [via jogamp] wrote:
> Will you be able to go on using a quite "low" version of glibc to avoid
> exclude some distros? Does it require a particular effort?
dunno .. since we would need a list for distros / libc versions, etc.
to define what is low ..
IMHO 2.2.5 like in ubuntu intel, is a quite low requirement already,
the armv7 requirement might be a glitch - however, ubuntu natty arm
is quite the 1st well usable here anyways.
sure .. willing to cooperate if we have more data
I can compile JOGL on an old Debian or Mandriva Linux 2006 if necessary.
I'm not an expert in C, I only wrote a simulator of processes with this language some years ago. I assume it is possible to install several versions of glibc on the same machine and use the lowest available, by using symbolic links for example, am I wrong?