[GRASS-dev] Secret to compiling GRASS 7 on Ubuntu 9.10?
Glynn Clements
glynn at gclements.plus.com
Mon Dec 14 18:02:12 EST 2009
Isaac Ullah wrote:
> I've been trying to compile and install GRASS 7 on Ubuntu 9.10. I am
> using the same methodology that has been successful for me with previous
> version of Ubuntu. I have been able to successfully make binaries with no
> errors, but I consistently get gdal/proj errors when I launch the gui. I
> have tried with the precompiled ubuntu binaries of GDAL/PROJ as well as
> building them from latest source (no errors). i've even tried the old
> "compile GDAL first without GRASS support, then compile GRASS, then redo
> GDAL with GRASS support" trick, and this does not work either. Here are the
> errors:
>
> Welcome to GRASS 7.0.svn (2009)
> GRASS homepage: http://grass.osgeo.org/
> This version running through: Bash Shell (/bin/bash)
> Help is available with the command: g.manual -i
> See the licence terms with: g.version -c
> If required, restart the GUI with: g.gui wxpython
> When ready to quit enter: exit
>
> To run a command as administrator (user "root"), use "sudo <command>".
> See "man sudo_root" for details.
>
> GRASS 7.0.svn (jordan_wgs84):~/grass_7_source/grass_trunk > g.gui wxpython
>
> WARNING: Vector digitizer is not available (No module named
> grass7_wxvdigit).
>
> Note that vector digitizer is currently not working under MS Windows
> (hopefully will be fixed soon). Please try more recent version of GRASS.
> g.list: error while loading shared libraries: libgdal.so.1: cannot open
> shared object file: No such file or directory
> GRASS 7.0.svn (jordan_wgs84):~/grass_7_source/grass_trunk > whereis libgdal.so.1
> libgdal.so: /usr/lib/libgdal.so.1 /usr/lib64/libgdal.so.1
> /usr/local/lib/libgdal.so /usr/local/lib/libgdal.so.1
> GRASS 7.0.svn (jordan_wgs84):~/grass_7_source/grass_trunk > g.region -p
> g.region: error while loading shared libraries: libproj.so.0: cannot open
> shared object file: No such file or directory
> GRASS 7.0.svn (jordan_wgs84):~/grass_7_source/grass_trunk > whereis libproj.so.0
> libproj.so: /usr/lib/libproj.so.0 /usr/lib/libproj.so
> /usr/lib64/libproj.so.0 /usr/lib64/libproj.so
>
> Clearly you can see that I have both libgdal.so.1 and libproj.so.0 installed
> in standard locations, and they are in the PATH.
This is kind of clutching at straws, but:
1. Is /usr/lib64 listed in /etc/ld.so.conf?
2. Has "ldconfig" been run since the libraries were installed?
The loader doesn't scan the system directories looking for libraries;
it uses /etc/ld.so.cache, which is generated by ldconfig. If
ld.so.cache isn't up to date, libraries may not be found.
If you have "strace" installed, try:
strace g.region -p
This will show all of the system calls which are being made, including
the loading of shared libraries. It may provide some clues as to what
is going wrong.
--
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-dev
mailing list