Hi
For over month I try to solve a problem with gdal 1.3.2.
I had noticed it when I tried to export from grass using gdal.
if I run gdalinfo it return "floating point exception"
with ldd and gdb I found that problem is due to tls libraries. On
mandriva 2006 I have tls 2.3.5. On newest kubuntu 6.0.6 tls 2.6. But
problem is the same. I have installed older gdal libraries 1.3.1 i
1.2.3, problem returns
The detail analising of the whole system is out of my posiblilities (and
time!), all other compiled programs works without problems exept GDAL
On the itnernet I fonud only three similar situations (unsolved)
with regards
Jarek
jarekj@amu.edu.pl wrote:
if I run gdalinfo it return "floating point exception"
with ldd and gdb I found that problem is due to tls libraries.
Are you sure it's TLS and not just some general linking problem?
I had some weird library behaviour with gdal and solved it with
echo "/usr/lib/gdal" >/etc/ld.so.conf.d/gdal-i386.conf
ldconfig
You have nothing to lose by giving it a try, adjust path and
architecture as needed first.
Z
Zenon Panoussis napisał(a):
jarekj@amu.edu.pl wrote:
if I run gdalinfo it return "floating point exception"
with ldd and gdb I found that problem is due to tls libraries.
Are you sure it's TLS and not just some general linking problem?
I had some weird library behaviour with gdal and solved it with
echo "/usr/lib/gdal" >/etc/ld.so.conf.d/gdal-i386.conf
ldconfig
You have nothing to lose by giving it a try, adjust path and
architecture as needed first.
Z
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser
I tried and failed.
Exaclty it is problem with ld-linux.so.2 during loading with static-dynamic linking:
.....
reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0xb7ef693d in _dl_allocate_static_tls (map=0xb7eed520) at dl-reloc.c:74
74 offset = GL(dl_tls_static_used) + (freebytes - n * map->l_tls_align
(gdb) bt
#0 0xb7ef693d in _dl_allocate_static_tls (map=0xb7eed520) at dl-reloc.c:74
#1 0xb7ef803a in _dl_relocate_object (l=0xb7f03ff4, scope=0xb76d9efc, lazy=1,
consider_profiling=0) at ../sysdeps/i386/dl-machine.h:512
....
I understad that a little (I'm not a linux c programmer), but I think, everbody who compiled grass, compiled gdal also, and nobody had a problem (it would be mentioned on group) - now I looking for what I do wrong
maybe it is hardware problem (AMD), I don't know...
regards
jarek
Jarek Jasiewicz wrote:
Exaclty it is problem with ld-linux.so.2 during loading with
static-dynamic linking:
.....
reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0xb7ef693d in _dl_allocate_static_tls (map=0xb7eed520) at dl-reloc.c:74
74 offset = GL(dl_tls_static_used) + (freebytes - n *
map->l_tls_align
(gdb) bt
#0 0xb7ef693d in _dl_allocate_static_tls (map=0xb7eed520) at dl-reloc.c:74
#1 0xb7ef803a in _dl_relocate_object (l=0xb7f03ff4, scope=0xb76d9efc,
lazy=1,
consider_profiling=0) at ../sysdeps/i386/dl-machine.h:512
I don't grasp any of this, can't say anything about it one way or another.
I understad that a little (I'm not a linux c programmer), but I think,
everbody who compiled grass, compiled gdal also, and nobody had a
problem (it would be mentioned on group) - now I looking for what I do
wrong
There's a kind of circular dependency, you need to build grass with
gdal and you need to build gdal with grass, so grass-gdal is a separate
package and you need it. Did you build and install everything in the
right order?
Z
There's a kind of circular dependency, you need to build grass with
gdal and you need to build gdal with grass, so grass-gdal is a separate
package and you need it. Did you build and install everything in the
right order?
Z
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser
Yes I did
I know on dependency with gdal-grass and I compiled it propertly (i did
it several times on different distros, with different args).
I have problem with gdal and QGIS which DON'T WORK. I identified
probelm as systemic and I looking for help of gdal - grass -qgis users
whom maybe has met that proplem enywhen.
I has consulted it with linux guru's as systemic problem they sed that
gdal is very rare library (in Poland grass is really used by no more
than 50 people) and sugesst to consult with user of that libraries.
I suspect that problem may be coused by: KDE (why?) or wrong instaled
OGDI but I not sure.
regards
Jarek
jarekj@amu.edu.pl wrote:
I has consulted it with linux guru's as systemic problem they sed that
gdal is very rare library (in Poland grass is really used by no more
than 50 people) and sugesst to consult with user of that libraries.
Libraries usually don't care in which country they work, unless some
odd locale settings are messing things up. LC_NUMERIC != C seems to
cause problems with gdal. You could try exporting all the LC_XYZ
variables to non-localised values (or simply an out-of-the-box
US-English common distro installation) and see what happens.
Z