[GRASSLIST:5359] Errors

Pl clarify and help

Using

sh
grass-5.7.cvs-i686-pc-linux-gnu-08_01_2005-install.sh
grass-5.7.cvs-i686-pc-linux-gnu-08_01_2005.tar

1. import e00 files error still persists.

couldn't execute "v.in.v00": no such file or directory
couldn't
execute "v.in.v00": no such file or directory
    
while executing
"exec -- $cmd --tcltk"
    (procedure "execute" line 4)

    invoked from within
"execute v.in.v00
"
    invoked from within
".#menubar.#menubar
#file.#menubar#file#menu1.#menubar#file#menu1#menu2
invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tk::MenuInvoke" line 47)
    invoked from within
"tk::MenuInvoke
.#menubar.#menubar#file.#menubar#file#menu1.#menubar#file#menu1#menu2
1"
    (command bound to event)

2. NVIZ error
nviz: error while loading shared libraries:
/usr/lib/libtk.so.0:
invalid ELF header
nviz: error while loading shared libraries:
/usr/lib/libtk.so.0: invalid ELF header
    while executing

"exec -- $cmd --tcltk"
    (procedure "execute" line 4)
   
invoked from within
"execute nviz "
    invoked from within
".
#menubar.#menubar#menu2 invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tk::MenuInvoke" line 47)
    invoked from within
"tk::MenuInvoke .#menubar.#menubar#menu2 1"
    (command bound to event)

Ravi

DOUBT:
THERE IS NO rpm BY NAME libdfftw.so.2 for mandrake

is the lib 'd' fftw.so.2

just another typo error.

Iam using by issuing
ln -s libdfftw.so.2 libfftw.so.2
lconfig

to clar this hurdle earlier.

__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250

Ravi,

Your error message implies that the v.in.e00 script or tcltk GUI has a typo
(v.in.v00 instead of v.in.e00). However, I checked both a 20 Dec. version of
5.7-cvs and the current 6.0.0beta1 release of GRASS and couldn't find such a
typo. Perhaps you are using an older version???

I decided to run v.in.e00 myself to check it out. I first tried with some
USFS files I had. I got a strange error about not being able to open the
data source. Well, these are old files and so there might be a problem. So I
then tried some digital chart of the world (DCW) files I had downloaded for
Spain within the past year.

Again I got some strange errors that I initially blamed on a directory
structure that had a directory name with a space in it (from when I was a
carefree Mac person that didn't think about unix naming conventions). Fixed
that. Now I still get an error, but this is something that can be worked
with. Here it is and below I'll recount what is happening. It is probably
pretty easy to fix.

[using 6.0.0 beta1 on Mac OSX]

v.in.e00
file=/Users/Shared/projects/spain/Regional_maps/DCW/new_e00/dnnet.e00
type=line vect=spain_drainages -v
E00 ASCII found and converted to Arc Coverage in current directory
Importing...

Cannot open data source
An error occurred. Stop.

V.in.e00 converts the DCW file to an Arc Coverage (as the output says
above). But there is something off with the v.in.ogr part of the script and
it bombs. However, when I used v.in.ogr to read in the Arc Coverage created
by v.in.e00 it does so with no problem.

I'll see about testing it if I have a bit of time over the weekend. My guess
is that it is something in how the E00NAME variable gets parsed in the
script and read into v.in.ogr. Maybe Marcus will know right away. I've tried
it with and without using the *.e00 extension and had similar results.

Michael

On 1/14/05 3:48 AM, "RAVI KUMAR" <ravivundavalli@yahoo.com> wrote:

Pl clarify and help

Using

sh
grass-5.7.cvs-i686-pc-linux-gnu-08_01_2005-install.sh
grass-5.7.cvs-i686-pc-linux-gnu-08_01_2005.tar

1. import e00 files error still persists.

couldn't execute "v.in.v00": no such file or directory
couldn't
execute "v.in.v00": no such file or directory
    
while executing
"exec -- $cmd --tcltk"
    (procedure "execute" line 4)

    invoked from within
"execute v.in.v00
"
    invoked from within
".#menubar.#menubar
#file.#menubar#file#menu1.#menubar#file#menu1#menu2
invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tk::MenuInvoke" line 47)
    invoked from within
"tk::MenuInvoke
.#menubar.#menubar#file.#menubar#file#menu1.#menubar#file#menu1#menu2
1"
    (command bound to event)

2. NVIZ error
nviz: error while loading shared libraries:
/usr/lib/libtk.so.0:
invalid ELF header
nviz: error while loading shared libraries:
/usr/lib/libtk.so.0: invalid ELF header
    while executing

"exec -- $cmd --tcltk"
    (procedure "execute" line 4)
   
invoked from within
"execute nviz "
    invoked from within
".
#menubar.#menubar#menu2 invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tk::MenuInvoke" line 47)
    invoked from within
"tk::MenuInvoke .#menubar.#menubar#menu2 1"
    (command bound to event)

Ravi

DOUBT:
THERE IS NO rpm BY NAME libdfftw.so.2 for mandrake

is the lib 'd' fftw.so.2

just another typo error.

Iam using by issuing
ln -s libdfftw.so.2 libfftw.so.2
lconfig

to clar this hurdle earlier.

__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250

____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

On Sat, Jan 15, 2005 at 10:04:28AM -0700, Michael Barton wrote:

Ravi,

Your error message implies that the v.in.e00 script or tcltk GUI has a typo
(v.in.v00 instead of v.in.e00). However, I checked both a 20 Dec. version of
5.7-cvs and the current 6.0.0beta1 release of GRASS and couldn't find such a
typo.

I fixed that in CVS after receiving Ravi note.

cvs2cl.pl menu.tcl
2005-01-11 08:52 markus
        * menu.tcl: v.in.v00 -> v.in.e00

Perhaps you are using an older version???

As suggested earlier, a user can simply fix 'menu.tcl' with
a text editor (or, better, get 6.0.0beta1).

I decided to run v.in.e00 myself to check it out. I first tried with some
USFS files I had. I got a strange error about not being able to open the
data source. Well, these are old files and so there might be a problem. So I
then tried some digital chart of the world (DCW) files I had downloaded for
Spain within the past year.

Again I got some strange errors that I initially blamed on a directory
structure that had a directory name with a space in it (from when I was a
carefree Mac person that didn't think about unix naming conventions). Fixed
that. Now I still get an error, but this is something that can be worked
with. Here it is and below I'll recount what is happening. It is probably
pretty easy to fix.

At least it's easy to debug :slight_smile:

Open the v.in.e00 file, add ' -x' to the first #/bin/sh line and run again.
It will then report every line. If you don't see anything wrong,
please send the output to me for inspection.

So, for debugging, use:
#!/bin/sh -x
[...]

Markus

Michael,

On Mon, January 17, 2005 10:57, Markus Neteler said:

On Sat, Jan 15, 2005 at 10:04:28AM -0700, Michael Barton wrote:

Again I got some strange errors that I initially blamed on a directory
structure that had a directory name with a space in it (from when I was a
carefree Mac person that didn't think about unix naming conventions). Fixed
that. Now I still get an error, but this is something that can be worked
with. Here it is and below I'll recount what is happening. It is probably
pretty easy to fix.

At least it's easy to debug :slight_smile:

Open the v.in.e00 file, add ' -x' to the first #/bin/sh line and run again.
It will then report every line. If you don't see anything wrong,
please send the output to me for inspection.

So, for debugging, use:
#!/bin/sh -x
[...]

I'm not sure about this, but if I understand the script correctly E00NAME is
only the basename without extension, but doesn't v.in.ogr's "dsn" need the
extension ?

Moritz

On Mon, Jan 17, 2005 at 11:58:17AM +0100, Moritz Lennert wrote:

Michael,

On Mon, January 17, 2005 10:57, Markus Neteler said:
> On Sat, Jan 15, 2005 at 10:04:28AM -0700, Michael Barton wrote:
>>
>> Again I got some strange errors that I initially blamed on a directory
>> structure that had a directory name with a space in it (from when I was a
>> carefree Mac person that didn't think about unix naming conventions). Fixed
>> that. Now I still get an error, but this is something that can be worked
>> with. Here it is and below I'll recount what is happening. It is probably
>> pretty easy to fix.
>
> At least it's easy to debug :slight_smile:
>
> Open the v.in.e00 file, add ' -x' to the first #/bin/sh line and run again.
> It will then report every line. If you don't see anything wrong,
> please send the output to me for inspection.
>
> So, for debugging, use:
> #!/bin/sh -x
> [...]
>

I'm not sure about this, but if I understand the script correctly E00NAME is
only the basename without extension, but doesn't v.in.ogr's "dsn" need the
extension ?

No. v.in.ogr takes the output of avcimport which is a directory with
identical name to the e00 file(s).

Markus

> Perhaps you are using an older version???

As suggested earlier, a user can simply fix 'menu.tcl' with
a text editor (or, better, get 6.0.0beta1).

Note the v.in.e00 script in 6beta1 is missing the "(null)" update, which
may be causing problems. Try updating from cvs:

http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass51/scripts/v.in.e00/v.in.e00?rev=HEAD&content-type=text/plain

Hamish