[Gvsig_english] BUG??? gvSIG 2.0 devel (and gvSIG 1.9 alpha) will not work correctly with "older" linux versions!

[Benjamin Ducke]

All subversions of a major libc/stdc version should have full ABI
backward compatibility. A later glibc should work fine for
executables linked to an earlier version (they use individual
symbol versioning, which means that all objects defined in e.g.
libc 2.3 will have the same version in libc 2.6).

So you should be able to link the native libs on Linux to an old
libc, say 2.3.2 and things should work fine on e.g. a recent Ubuntu.

As an alternative, all necessary system libs could be bundled in
the installation directory and the startup script just needs to
point LD_LIBRARY_PATH to the location of those bundled libraries.

Ben

Cesar Martinez Izquierdo wrote:
> Hello Wolfrang,
> the problem is that different versions of Linux usually include 
> different version of the C and C++ libraries (libc and libstdc++).
> 
> When you compile a library using a version of libc, it may not correctly 
> run on another machine with a different version of libc. That's why 
> Linux distributions compile all the packages using its own libc version.
> 
> Compiling the native code using an older version of libc may improve 
> compatibility (with older and newer systems), but it might also make 
> gvSIG not compatible with newer distributions. We are not experts C/C++ 
> compilation, any help is welcome.
> 
> A possible solution may be to define a set of target Linux distributions 
> and versions, and ensure that gvSIG works for these set of versions 
> (either by releasing different version of gvSIG for each distribution, 
> or making gvSIG compatible with all these distributions, if possible).
> 
> However, I don't know when will we have the resources to define this set 
> of distributions, to test each version on them, and to correct the 
> compilations when they produce problems on the defined set.
> 
> For the moment, it might be helpful if you provide the output of 
> following commands:
> 
> $ ls -l /lib/libc.so*
> (to guess libc version)
> 
> $ ls -l /usr/lib/libstdc*
> (to guess libstc++ version)
> 
> Regards,
> 
> 
> Wolfgang Qual escribió:
>> Hi list,
>> as written before, I thought that the latest prerelease of gvSIG would 
>> not allow georeferencing at all. Well, this is not true - the dialogue 
>> was just moved to another place (thanks, Ben).
>> However, I still was not able to do the georeferencing on my machine 
>> (which is a debian machine; cat /proc/version gives Linux version 
>> 2.6.17-1-686 (Debian 2.6.17-5lhm7) (jan-marek.glogowski at muenchen.de) 
>> (gcc-Version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Tue Oct 9 11:17:35 CEST 
>> 2007)
>> There, the georeferencing *just does not show up*.
>> However, when starting the same gvSIG-version on an other linux 
>> machine (ubuntu 7.10, cat /proc/version
>> Linux version 2.6.22-15-generic (buildd at terranova) (gcc version 4.1.3 
>> 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Jun 10 
>> 09:21:34 UTC 2008)
>> The georefercing dialogue is displayed.
>>
>> I consider this as a *very* serious problem: the first linux distro 
>> described above will be the standard for our office (City of Munich, 
>> Department of Health and Environment). This distro is called LIMUX and 
>> it is especially designed for the administration's purposes. Updating 
>> this distro always takes much longer than compared to ubuntu. 
>> Therefore, we will *never* be up to date. And I think that gvSIG 
>> should really also run not on the latest releases. Especially 
>> administration is not as flexible as smaller companies or private 
>> users. Please, please check this issue soon!
>>
>> Best,
>> Wolfgang
>>
>>
> 
> 


-- 
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeology Ltd
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke at oxfordarch.co.uk




------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.