On Mon, 15 Jun 2009 04:01:11 -0700 (PDT),
Hamish <[email protected]> wrote:
> Seb wrote:
>> Checking: ,-----[ ldd /usr/lib/grass64/bin/g.region | grep 'not
>> found' ] | libgrass_vect.so => not found |
>> libgrass_dbmibase.so => not found | libgrass_gis.so => not found
> ....
>> In fact, doing this for /usr/lib/grass64/bin/* gives a pretty long
>> list (1954). Could this be the problem?
> it sure won't help! ... get that fixed first.
Ok, that turned out to be a feature if you saw my bogus Debian bug
report Bug#533191.
So I went back to bare essentials:
$ mkdir grassdata
$ ls -l
drwxr-xr-x 2 sluque sluque 4.0K 2009-06-16 21:02 grassdata
$ grass -text
# Chose to set up a "Other Projection" location in the newly created
# database, and right after typing the "one line description" for the
# location:
Please enter a one line description for location <Hudson_Bay_AEA>
> test
=====================================================
test
=====================================================
ok? (y/n) [y]
ERROR: region for current mapset is not set
run "g.region"
So now I don't think this has anything to do with the restored data, and
am very stuck wondering what is wrong, even though nothing seems wrong
outside of GRASS. Any further advice on what to look for appreciated,
particularly how to debug this problem (setting DEBUG=3 before calling
grass in the code above gave the same level of messages). Thanks.
--
Seb
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
