[GRASS-user] Installing r.basin With GEM

   The instructions in the GEM manual do not fit the files downloaded for
r.basin (Makefile description.html r.basin/ r.basin.py r.basin1.gif
r.basin2.gif). What must I do to make r.basin available for use with data in
-6.5svn?

Rich

why not using g.extension?

http://grass.osgeo.org/grass64/manuals/html64_user/g.extension.html

Helmut

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/Installing-r-basin-With-GEM-tp4687329p4687336.html
Sent from the Grass - Users mailing list archive at Nabble.com.

On Wed, 4 Apr 2012, Helmut Kudrnovsky wrote:

why not using g.extension?
http://grass.osgeo.org/grass64/manuals/html64_user/g.extension.html

Helmut,

   Now that I'm aware of it, I will.

Thanks,

Rich

On Wed, Apr 4, 2012 at 8:56 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

On Wed, 4 Apr 2012, Helmut Kudrnovsky wrote:

why not using g.extension?
http://grass.osgeo.org/grass64/manuals/html64_user/g.extension.html

Now that I'm aware of it, I will.

Were should we remove pointers to the moreover outdated GEM?

Markus

On Wed, 4 Apr 2012, Markus Neteler wrote:

Were should we remove pointers to the moreover outdated GEM?

Markus,

   The wiki? Or, remove that page and links to it.

Rich

On Wed, Apr 4, 2012 at 9:04 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

On Wed, 4 Apr 2012, Markus Neteler wrote:

Were should we remove pointers to the moreover outdated GEM?

Markus,

Rich,

The wiki? Or, remove that page and links to it.

I am managing some 10+ servers with some 1000+ pages :slight_smile:
Please be specific, say, which URL(s)?

thanks
Markus

On Wed, 4 Apr 2012, Rich Shepard wrote:

why not using g.extension?

   The manual page does not explain from which directory it should be run.
The module needs to run within GRASS, but if I let GRASS pick the location
and mapset the build fails for an inability to find the Makefile.

   I think it should be run from the GRASS source code directory, but what
command should be used to start GRASS so the module is properly built and
installed?

   Errors:

mkdir -p
/home/rshepard/grassdata/Washington-Kinross/buckhorn/.tmp/salmo/4500.0/dist.i486-slackware-linux-gnu/fonts
make: *** No rule to make target .basin', needed by
/home/rshepard/grassdata/Washington-Kinross/buckhorn/.tmp/salmo/4500.0/dist.i486-slackware-linux-gnu/scripts/r.basin'. Stop.
ERROR: Compilation failed, sorry. Please check above error messages.

Rich

On Wed, 4 Apr 2012, Markus Neteler wrote:

I am managing some 10+ servers with some 1000+ pages :slight_smile: Please be
specific, say, which URL(s)?

Markus,

   Main page:
<http://grass.osgeo.org/grass65/manuals/html65_user/gem/index.html&gt;

Rich

On Wed, Apr 4, 2012 at 9:11 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

On Wed, 4 Apr 2012, Rich Shepard wrote:

why not using g.extension?

The manual page does not explain from which directory it should be run.

It can be run from anywhere in the GRASS session.

...

Errors:

mkdir -p
/home/rshepard/grassdata/Washington-Kinross/buckhorn/.tmp/salmo/4500.0/dist.i486-slackware-linux-gnu/fonts
make: *** No rule to make target .basin', needed by
/home/rshepard/grassdata/Washington-Kinross/buckhorn/.tmp/salmo/4500.0/dist.i486-slackware-linux-gnu/scripts/r.basin'.
Stop.
ERROR: Compilation failed, sorry. Please check above error messages.

The Makefile was simply broken. Fixed in r51262.

Please retry

g.extension r.basin

For me it works now.

Markus

On Wed, Apr 4, 2012 at 9:12 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
...

Main page:
<http://grass.osgeo.org/grass65/manuals/html65_user/gem/index.html&gt;

@devs: perhaps add a prominent note on top that g.extension is recommended?

Markus

On Wed, 4 Apr 2012, Markus Neteler wrote:

The Makefile was simply broken. Fixed in r51262.

   Huh! I ran svn up and rebuilt the system before starting today's session.
Will do so again.

Please retry
g.extension r.basin
For me it works now.

   Will do ... and report the results.

Thanks,

Rich

On Wed, 4 Apr 2012, Rich Shepard wrote:

Will do ... and report the results.

   Interesting. I am at revision 51262. However, the third try worked. Very
strange.

Thanks,

Rich