It's only a problem with certain tools. I have the same problem with
d.redraw for example, but not with d.erase. The difference seems to
be that d.erase is not under the scripts dir, but is instead in bin
(all under GRASS of course).
Is there some way I can add the scripts tools back in, and is this the
sign that I just screwed up the install somehow?
What I did find is that each script is under a directory by the same
name in the scripts dir. So for example, d.redraw is in:
/usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
I'm going through all of these now, and removing the dir and leaving
the script. Somewhat tedious, but the scripts appear to work.
Roger
--
On Wed, Oct 14, 2009 at 10:34 PM, Hamish <hamish_b@yahoo.com> wrote:
Roger André wrote:
I've noticed that a few tools in my GRASS 6.4 appear to be
missing, or at least missing from my path.
from the GRASS terminal, what does "echo $PATH" say?
Here is an example:
...
bash: v.db.addcol: command not found
And yet, when I look for the tool under my install dir, it
appears to be there:
What I did find is that each script is under a directory by the same
name in the scripts dir. So for example, d.redraw is in:
/usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
Wow. This is not desired of course. I am a bit surprised.
I'm going through all of these now, and removing the dir and leaving
the script. Somewhat tedious, but the scripts appear to work.
Would you mind to check if this is still valid for RC5?
> What I did find is that each script is under a directory by the same
> name in the scripts dir. So for example, d.redraw is in:
> /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
Wow. This is not desired of course. I am a bit surprised.
Maybe I don't get that right but I have grass64_release, grass640_0rc5,
grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
contains a directory for each script. In each script-directory there are
description (html) files and also README, Makefiles, etc.
Isn't this ok?
> I'm going through all of these now, and removing the dir and leaving
> the script. Somewhat tedious, but the scripts appear to work.
Would you mind to check if this is still valid for RC5?
Isn't this just a matter of file/ directory permission(s)? (shrug)
Nikos
> > What I did find is that each script is under a directory by the same
> > name in the scripts dir. So for example, d.redraw is in:
> > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
> Wow. This is not desired of course. I am a bit surprised.
On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
[Replying to myself]
Maybe I don't get that right but I have grass64_release, grass640_0rc5,
grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
contains a directory for each script. In each script-directory there are
description (html) files and also README, Makefiles, etc.
Isn't this ok?
Yes it is (for the source code :-). Under /usr/local/grass... (the
installed stuff; currently I use the 64 version) all scripts are bare
files under the scripts directory.
> > I'm going through all of these now, and removing the dir and leaving
> > the script. Somewhat tedious, but the scripts appear to work.
> Would you mind to check if this is still valid for RC5?
On Fri, 2009-10-16 at 15:01 +0200, Nikos Alexandris wrote:
> > On Thu, Oct 15, 2009 at 5:00 PM, Roger André <randre@gmail.com> wrote:
> > > My PATH while in GRASS already contains the scripts dir:
>
> > > GRASS 6.4.0RC4 (colombia):~ > echo $PATH
> > > /usr/local/grass-6.4.0RC4/bin:/usr/local/grass-6.4.0RC4/scripts:<snip>
>
> Mine too (the grass-6.4.0svn version).
>
>
> > > What I did find is that each script is under a directory by the same
> > > name in the scripts dir. So for example, d.redraw is in:
> > > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
>
> On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
> > Wow. This is not desired of course. I am a bit surprised.
On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
[Replying to myself]
> Maybe I don't get that right but I have grass64_release, grass640_0rc5,
> grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
> contains a directory for each script. In each script-directory there are
> description (html) files and also README, Makefiles, etc.
>
> Isn't this ok?
Yes it is (for the source code :-). Under /usr/local/grass... (the
installed stuff; currently I use the 64 version) all scripts are bare
files under the scripts directory.
> > > I'm going through all of these now, and removing the dir and leaving
> > > the script. Somewhat tedious, but the scripts appear to work.
>
> > Would you mind to check if this is still valid for RC5?
I've installed grass-6.4.0RC5 and there is no problem. Scripts (all of
them I suppose seem to) work fine ~ I 've tested several.
Thanks for your inquiry about this. Everything works now, after
having moved all scripts from sub-directory into $GISBASE/scripts.
I'm teaching myself how to use GRASS with your excellent book, so I am
far from being an expert at installation and configuration options.
However in response to Nikos's question, I am not sure how changing
permissions would have solved this problem. Following the defined
$PATH would only bring you to the directory, and not the script
itself. It would seem to me that part of the make process would be to
copy these scripts into the correct directory, but since they appear
to be the same place... I dunno.
Thanks,
Roger
--
On Fri, Oct 16, 2009 at 6:08 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
On Fri, 2009-10-16 at 15:01 +0200, Nikos Alexandris wrote:
> > On Thu, Oct 15, 2009 at 5:00 PM, Roger André <randre@gmail.com> wrote:
> > > My PATH while in GRASS already contains the scripts dir:
>
> > > GRASS 6.4.0RC4 (colombia):~ > echo $PATH
> > > /usr/local/grass-6.4.0RC4/bin:/usr/local/grass-6.4.0RC4/scripts:<snip>
>
> Mine too (the grass-6.4.0svn version).
>
>
> > > What I did find is that each script is under a directory by the same
> > > name in the scripts dir. So for example, d.redraw is in:
> > > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
>
> On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
> > Wow. This is not desired of course. I am a bit surprised.
On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
[Replying to myself]
> Maybe I don't get that right but I have grass64_release, grass640_0rc5,
> grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
> contains a directory for each script. In each script-directory there are
> description (html) files and also README, Makefiles, etc.
>
> Isn't this ok?
Yes it is (for the source code :-). Under /usr/local/grass... (the
installed stuff; currently I use the 64 version) all scripts are bare
files under the scripts directory.
> > > I'm going through all of these now, and removing the dir and leaving
> > > the script. Somewhat tedious, but the scripts appear to work.
>
> > Would you mind to check if this is still valid for RC5?
I've installed grass-6.4.0RC5 and there is no problem. Scripts (all of
them I suppose seem to) work fine ~ I 've tested several.
Thanks for your inquiry about this. Everything works now, after
having moved all scripts from sub-directory into $GISBASE/scripts.
I'm teaching myself how to use GRASS with your excellent book, so I am
far from being an expert at installation and configuration options.
However in response to Nikos's question, I am not sure how changing
permissions would have solved this problem.
My bad Roger. I was looking at the source code tree.
Following the defined
$PATH would only bring you to the directory, and not the script
itself. It would seem to me that part of the make process would be to
copy these scripts into the correct directory, but since they appear
to be the same place... I dunno.
How did you perform the installation, if I may ask?
Nikos
---
On Fri, Oct 16, 2009 at 6:08 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
> On Fri, 2009-10-16 at 15:01 +0200, Nikos Alexandris wrote:
>>
>> > > On Thu, Oct 15, 2009 at 5:00 PM, Roger André <randre@gmail.com> wrote:
>> > > > My PATH while in GRASS already contains the scripts dir:
>> >
>> > > > GRASS 6.4.0RC4 (colombia):~ > echo $PATH
>> > > > /usr/local/grass-6.4.0RC4/bin:/usr/local/grass-6.4.0RC4/scripts:<snip>
>> >
>> > Mine too (the grass-6.4.0svn version).
>> >
>> >
>> > > > What I did find is that each script is under a directory by the same
>> > > > name in the scripts dir. So for example, d.redraw is in:
>> > > > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
>> >
>> > On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
>> > > Wow. This is not desired of course. I am a bit surprised.
>>
>> On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
>>
>> [Replying to myself]
>>
>> > Maybe I don't get that right but I have grass64_release, grass640_0rc5,
>> > grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
>> > contains a directory for each script. In each script-directory there are
>> > description (html) files and also README, Makefiles, etc.
>> >
>> > Isn't this ok?
>>
>> Yes it is (for the source code :-). Under /usr/local/grass... (the
>> installed stuff; currently I use the 64 version) all scripts are bare
>> files under the scripts directory.
>>
>>
>> > > > I'm going through all of these now, and removing the dir and leaving
>> > > > the script. Somewhat tedious, but the scripts appear to work.
>> >
>> > > Would you mind to check if this is still valid for RC5?
>
> I've installed grass-6.4.0RC5 and there is no problem. Scripts (all of
> them I suppose seem to) work fine ~ I 've tested several.
>
> Nikos
>
>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
On Fri, Oct 16, 2009 at 11:05 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
Roger André wrote:
Hi Markus,
Thanks for your inquiry about this. Everything works now, after
having moved all scripts from sub-directory into $GISBASE/scripts.
I'm teaching myself how to use GRASS with your excellent book, so I am
far from being an expert at installation and configuration options.
However in response to Nikos's question, I am not sure how changing
permissions would have solved this problem.
My bad Roger. I was looking at the source code tree.
Following the defined
$PATH would only bring you to the directory, and not the script
itself. It would seem to me that part of the make process would be to
copy these scripts into the correct directory, but since they appear
to be the same place... I dunno.
How did you perform the installation, if I may ask?
Nikos
---
On Fri, Oct 16, 2009 at 6:08 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
> On Fri, 2009-10-16 at 15:01 +0200, Nikos Alexandris wrote:
>>
>> > > On Thu, Oct 15, 2009 at 5:00 PM, Roger André <randre@gmail.com> wrote:
>> > > > My PATH while in GRASS already contains the scripts dir:
>> >
>> > > > GRASS 6.4.0RC4 (colombia):~ > echo $PATH
>> > > > /usr/local/grass-6.4.0RC4/bin:/usr/local/grass-6.4.0RC4/scripts:<snip>
>> >
>> > Mine too (the grass-6.4.0svn version).
>> >
>> >
>> > > > What I did find is that each script is under a directory by the same
>> > > > name in the scripts dir. So for example, d.redraw is in:
>> > > > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
>> >
>> > On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
>> > > Wow. This is not desired of course. I am a bit surprised.
>>
>> On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
>>
>> [Replying to myself]
>>
>> > Maybe I don't get that right but I have grass64_release, grass640_0rc5,
>> > grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
>> > contains a directory for each script. In each script-directory there are
>> > description (html) files and also README, Makefiles, etc.
>> >
>> > Isn't this ok?
>>
>> Yes it is (for the source code :-). Under /usr/local/grass... (the
>> installed stuff; currently I use the 64 version) all scripts are bare
>> files under the scripts directory.
>>
>>
>> > > > I'm going through all of these now, and removing the dir and leaving
>> > > > the script. Somewhat tedious, but the scripts appear to work.
>> >
>> > > Would you mind to check if this is still valid for RC5?
>
> I've installed grass-6.4.0RC5 and there is no problem. Scripts (all of
> them I suppose seem to) work fine ~ I 've tested several.
>
> Nikos
>
>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Hi Nikos,
I downloaded the source, grass-6.4.0RC4.tar.gz, unpacked it into
/usr/local,
hmm?
If you have a tarred source named "grass-6.4.0RC4.tar.gz" after
unpacking it you get a directory called grass-6.4.0RC4. The installation
process installs over it at "/usr/local/grass-6.4.0RC4/" as I can see in
your first post, then this should be the root of the problem.
Perhaps its better to move the source tree somewhere else
(e.g. /usr/local/src).
On Fri, Oct 16, 2009 at 11:54 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
Roger André:
Hi Nikos,
I downloaded the source, grass-6.4.0RC4.tar.gz, unpacked it into
/usr/local,
hmm?
If you have a tarred source named "grass-6.4.0RC4.tar.gz" after
unpacking it you get a directory called grass-6.4.0RC4. The installation
process installs over it at "/usr/local/grass-6.4.0RC4/" as I can see in
your first post, then this should be the root of the problem.
Perhaps its better to move the source tree somewhere else
(e.g. /usr/local/src).
