[GRASS5] Bug tracking system ?

neteler · November 4, 2000, 9:25am

Hi developers,

as the GRASS project is growing, I am considering if we
need a bug tracking system which is able to grab
suggestions as well.

An interesting system, based on bugzilla, I have seen here:
http://www.openoffice.org/project_issues.html
"Issuezilla"

From the page:

"Issuezilla is based on Bugzilla, but has been generalized to handle all
kinds of issues, not just code-based issues. On OpenOffice.org, the
supported issue-types now include:
DEFECT, ENHANCEMENT, FEATURE, TASK and PATCH."

In fact I still prefer to have bugs fixed than to manage them (see my next
mail), but we need something more transparent for the GRASS users to
encourage them to report bugs and send suggestions.

Maybe we can set up such a bug-tracking system and see, if it meets
our needs.

Regards

Markus

--
Dipl.-Geogr. Markus Neteler * University of Hannover
Institute of Physical Geography and Landscape Ecology
Schneiderberg 50 * D-30167 Hannover * Germany
Tel: ++49-(0)511-762-4494 Fax: -3984

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

timcera · November 7, 2000, 2:23am

Markus Neteler wrote:

Hi developers,

as the GRASS project is growing, I am considering if we
need a bug tracking system which is able to grab
suggestions as well.

There was some earlier conversation about SourceForge and my guess at
the list's consensus was to use parts of SourceForge that would be
valuable to GRASS development. IMHO, Bug tracking, support (for
suggestions), surveys, etc. are things that SourceForge does well and we
should
take advantage of their system.

I don't think that the web pages, or CVS should be shifted to
SourceForge because of the reasons cited by others on the list (slow
speed, all eggs in one basket, etc.).

I am able to dedicate some time to doing any legwork if wanted. I
expect that it would hardly take any time at all and better yet, it
would be done.

take care
tim
--

timcera@earthlink.net
http://home.earthlink.net/~timcera

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Eric_Mitchell · November 7, 2000, 3:57pm

If all you gain from going to sourceforge is a bug tracker,
consider setting up Bugzilla. This is the bug tracker used
by Netscape to track bugs in their web browser. Red Hat
uses it to track problems with their Linux distributions.
The Gnome project is also in the process of switching to
Bugzilla. Details at http://www.mozilla.org/tools/bugs.

Setting it up here took about a day of wrangling with the
mysql installation and initial permissions, etc.

Tim Cera wrote:

Markus Neteler wrote:
>
> Hi developers,
>
> as the GRASS project is growing, I am considering if we
> need a bug tracking system which is able to grab
> suggestions as well.

There was some earlier conversation about SourceForge and my guess at
the list's consensus was to use parts of SourceForge that would be
valuable to GRASS development. IMHO, Bug tracking, support (for
suggestions), surveys, etc. are things that SourceForge does well and we
should
take advantage of their system.

I don't think that the web pages, or CVS should be shifted to
SourceForge because of the reasons cited by others on the list (slow
speed, all eggs in one basket, etc.).

I am able to dedicate some time to doing any legwork if wanted. I
expect that it would hardly take any time at all and better yet, it
would be done.

take care
tim
--

timcera@earthlink.net
http://home.earthlink.net/~timcera

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:emitchell@altaira.com |
| tel: (301) 809 - 3534 Altair Aerospace Corporation |
| tel: (800) 7 - ALTAIR 4201 Northview Dr. Suite 410 |
| fax: (301) 805 - 8122 Bowie, MD 20716 |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
              ,___
          /"\ / o=\ /"""---===/
         / \_/ \__/ ---===/
         | //\ || /""TT""/ //\ || ||""\
         | // \ || || // \ || ||__/
         | //--==\ |L--/ || //--==\ || || "=,
          \ ---===/
           \____---===/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 7, 2000, 4:52pm

On Tue, Nov 07, 2000 at 10:57:37AM -0500, Eric Mitchell wrote:

If all you gain from going to sourceforge is a bug tracker,
consider setting up Bugzilla. This is the bug tracker used
by Netscape to track bugs in their web browser. Red Hat
uses it to track problems with their Linux distributions.
The Gnome project is also in the process of switching to
Bugzilla. Details at http://www.mozilla.org/tools/bugs.

Setting it up here took about a day of wrangling with the
mysql installation and initial permissions, etc.

Hi all,

.. therefore I was proposing "Issuezilla" (www.openoffice.org,
see " Bugs and Issues") which was developed on top of bugzilla.
Their intention at openoffice is to provide a system catching
improvement suggestions, too. I think that's a good idea.

The only question is: Do we need that? Maybe yes. I feel we
need a "suggestions system" beside our current manually runung
bug-system.

Regards

Markus

Tim Cera wrote:
>
> Markus Neteler wrote:
> >
> > Hi developers,
> >
> > as the GRASS project is growing, I am considering if we
> > need a bug tracking system which is able to grab
> > suggestions as well.
>
> There was some earlier conversation about SourceForge and my guess at
> the list's consensus was to use parts of SourceForge that would be
> valuable to GRASS development. IMHO, Bug tracking, support (for
> suggestions), surveys, etc. are things that SourceForge does well and we
> should
> take advantage of their system.
>
> I don't think that the web pages, or CVS should be shifted to
> SourceForge because of the reasons cited by others on the list (slow
> speed, all eggs in one basket, etc.).
>
> I am able to dedicate some time to doing any legwork if wanted. I
> expect that it would hardly take any time at all and better yet, it
> would be done.
>
> take care
> tim
> --
>
> timcera@earthlink.net
> http://home.earthlink.net/~timcera
>
> ----------------------------------------
> If you want to unsubscribe from GRASS Development Team mailing list write to:
> minordomo@geog.uni-hannover.de with
> subject 'unsubscribe grass5'

--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:emitchell@altaira.com |
| tel: (301) 809 - 3534 Altair Aerospace Corporation |
| tel: (800) 7 - ALTAIR 4201 Northview Dr. Suite 410 |
| fax: (301) 805 - 8122 Bowie, MD 20716 |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
              ,___
          /"\ / o=\ /"""---===/
         / \_/ \__/ ---===/
         | //\ || /""TT""/ //\ || ||""\
         | // \ || || // \ || ||__/
         | //--==\ |L--/ || //--==\ || || "=,
          \ ---===/
           \____---===/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

--
Dipl.-Geogr. Markus Neteler * University of Hannover
Institute of Physical Geography and Landscape Ecology
Schneiderberg 50 * D-30167 Hannover * Germany
Tel: ++49-(0)511-762-4494 Fax: -3984

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Eric_Mitchell · November 7, 2000, 4:21pm

You can assign a bug severity of "enhancement" with bugzilla.
You can also query bug reports for severities of enhancement.

I haven't seen the openoffice version yet, I'll take a look.

Markus Neteler wrote:

Hi all,

.. therefore I was proposing "Issuezilla" (www.openoffice.org,
see " Bugs and Issues") which was developed on top of bugzilla.
Their intention at openoffice is to provide a system catching
improvement suggestions, too. I think that's a good idea.

The only question is: Do we need that? Maybe yes. I feel we
need a "suggestions system" beside our current manually runung
bug-system.

Regards

Markus

--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:emitchell@altaira.com |
| tel: (301) 809 - 3534 Altair Aerospace Corporation |
| tel: (800) 7 - ALTAIR 4201 Northview Dr. Suite 410 |
| fax: (301) 805 - 8122 Bowie, MD 20716 |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
              ,___
          /"\ / o=\ /"""---===/
         / \_/ \__/ ---===/
         | //\ || /""TT""/ //\ || ||""\
         | // \ || || // \ || ||__/
         | //--==\ |L--/ || //--==\ || || "=,
          \ ---===/
           \____---===/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Andreas_Lange1 · November 8, 2000, 5:16pm

Hi,

if we implement a bug-tracking system i want to propose to create
something that makes use of the GRASS system without too much user
input.
Please have a look at the script "bug-report.sh" in the scripts
directory.

My main concern is that we need more information about the enviroment a
bug occurs in. I tried to reproduce some of the bugs from the BUGS file
with no success, partly because of missing knowledge about the GRASS
database and enviroment the bug occurs in (e. g. UTM/LatLon/Projection,
extension of region etc.).

This would require something on the backend and the frontend. Maybe we
can include this into tcltkgrass too.

cu,

Andreas

Eric Mitchell wrote:

You can assign a bug severity of "enhancement" with bugzilla.
You can also query bug reports for severities of enhancement.

I haven't seen the openoffice version yet, I'll take a look.

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Bernhard_Reiter · November 11, 2000, 11:47pm

On Tue, Nov 07, 2000 at 04:52:54PM +0000, Markus Neteler wrote:

On Tue, Nov 07, 2000 at 10:57:37AM -0500, Eric Mitchell wrote:

> If all you gain from going to sourceforge is a bug tracker,

.. therefore I was proposing "Issuezilla" (www.openoffice.org,
see " Bugs and Issues") which was developed on top of bugzilla.
Their intention at openoffice is to provide a system catching
improvement suggestions, too. I think that's a good idea.

The only question is: Do we need that? Maybe yes. I feel we
need a "suggestions system" beside our current manually runung
bug-system.

Well we are certainly willing to set a system up, if you feel like you
need it.

It will have some more overhead.
I am not sure were the difference is between a bug tracking system with
different types of bugs (which one type could be the suggestions)
and an issue system. Actually most bug-tracking systems are usd for
wishlists, also.

Of course it would be beter if people used the mailinglists, so they
can explain their wishes and bugs, if necessary.

A better description on how to report a bug is always a way to improve,
too.

Bernhard

neteler · November 12, 2000, 8:44am

On Sun, Nov 12, 2000 at 12:47:34AM +0100, Bernhard Reiter wrote:

On Tue, Nov 07, 2000 at 04:52:54PM +0000, Markus Neteler wrote:
> On Tue, Nov 07, 2000 at 10:57:37AM -0500, Eric Mitchell wrote:

> > If all you gain from going to sourceforge is a bug tracker,

> .. therefore I was proposing "Issuezilla" (www.openoffice.org,
> see " Bugs and Issues") which was developed on top of bugzilla.
> Their intention at openoffice is to provide a system catching
> improvement suggestions, too. I think that's a good idea.
>
> The only question is: Do we need that? Maybe yes. I feel we
> need a "suggestions system" beside our current manually runung
> bug-system.

Well we are certainly willing to set a system up, if you feel like you
need it.

It will have some more overhead.
I am not sure were the difference is between a bug tracking system with
different types of bugs (which one type could be the suggestions)
and an issue system. Actually most bug-tracking systems are usd for
wishlists, also.

Hi,

maybe I was reason for confusion. I was not aware that bugzilla
also allows to send suggestions. So there won't be a difference.

Of course it would be beter if people used the mailinglists, so they
can explain their wishes and bugs, if necessary.

A better description on how to report a bug is always a way to improve,
too.

If you have hints, please let me know!

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Jeshua_Lacock1 · November 12, 2000, 8:31am

Hoooooray!

We have binaries! (Now how do I use this thing?)

Thanks for every ones help!

In all just 27 modules failed to compile with the Grass 5 build 8 code. A list of the modules is at the bottom of this message. I tried compiling NVIZ and got one error (I entered the paths it wanted):

#################################################################
/Users/jeshua/grassb8/src/libes/ogsf
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/GS2.o
cc -g -O2 -DUSE_OGL -I/Users/jeshua/grassb8/src/include -c GS2.c
gstypes.h:8: header file ‘GL/gl.h’ not found
gstypes.h:244: undefined type, found GLfloat' GS2.c:23: header file 'GL/gl.h' not found GS2.c:2507: undefined type, found GLint’
make[1]: *** [OBJ.powerpc-apple-nextstep3/GS2.o] Error 1
make: *** [nvwish] Error 2

#################################################################

Then I tried to compile the GRID3D with one error (well 4 errors):

make[4]: *** [/usr/local/grass-5.0b/etc/bin/main/cmd/r3.mapcalc] Error 1
make[3]: *** [all] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all] Error 1
make: *** [all] Error 2

I did not try to compile PostgreSQL…

Heres the error.log:

Compilation error in module: src/display/d.colors (ignored)
Compilation error in module: src/general/g.help (ignored)
Compilation error in module: src/imagery/i.class (ignored)
Compilation error in module: src/imagery/i.ortho.photo (ignored)
Compilation error in module: src/imagery/i.points (ignored)
Compilation error in module: src/imagery/i.points3 (ignored)
Compilation error in module: src/imagery/i.vpoints (ignored)
Compilation error in module: src/mapdev/v.geom (ignored)
Compilation error in module: src/mapdev/v.in.shape (ignored)
Compilation error in module: src/mapdev/v.mkgrid (ignored)
Compilation error in module: src/mapdev/v.out.shape (ignored)
Compilation error in module: src/mapdev/v.rmdup (ignored)
Compilation error in module: src/raster/r.binfer (ignored)
Compilation error in module: src/raster/r.flowmd (ignored)
Compilation error in module: src/raster/r.in.dem (ignored)
Compilation error in module: src/raster/r.in.png (ignored)
Compilation error in module: src/raster/r.mapcalc (ignored)
Compilation error in module: src/raster/r.out.png (ignored)
Compilation error in module: src/raster/r.random (ignored)
Compilation error in module: src/raster/r.tiff (ignored)
Compilation error in module: src/raster/wildfire (ignored)
Compilation error in module: src/sites/s.kcv (ignored)
Compilation error in module: src/sites/s.rand (ignored)
Compilation error in module: src.contrib/CERL/raster/r.hydro.CASC2D (ignored)
Compilation error in module: src.contrib/SCS/misc/m.lulc.USGS (ignored)
Compilation error in module: src.contrib/SDTS (ignored)
Compilation error in module: src.garden/answers/src.answers/raster/r.fill.dir (ignored)
Sat Nov 11 23:32:47 PST 2000
DONE generating GRASS GIS binary code

Jeshua Lacock
Cartographer/Owner
http://SierraMaps.com
http://3dTopoMaps.com
Telephone: (760) 935-4481

neteler · November 12, 2000, 9:53am

On Sun, Nov 12, 2000 at 12:31:10AM -0800, Jeshua Lacock wrote:

Hoooooray!

We have binaries! (Now how do I use this thing?)

Yeah! That's great.

Use them with SPEARFISH dataset (get from samples page) or
with Project ASSIST data (these come with a tutorial).

Thanks for every ones help!

In all just 27 modules failed to compile with the Grass 5 build 8
code. A list of the modules is at the bottom of this message. I
tried compiling NVIZ and got one error (I entered the paths it
wanted):

#################################################################
/Users/jeshua/grassb8/src/libes/ogsf
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/GS2.o
cc -g -O2 -DUSE_OGL -I/Users/jeshua/grassb8/src/include -c GS2.c
gstypes.h:8: header file 'GL/gl.h' not found
gstypes.h:244: undefined type, found `GLfloat'
GS2.c:23: header file 'GL/gl.h' not found
GS2.c:2507: undefined type, found `GLint'
make[1]: *** [OBJ.powerpc-apple-nextstep3/GS2.o] Error 1
make: *** [nvwish] Error 2

Here you need the "MESA" package:
/usr/include/GL/gl.h

See grass5 web page for mesa url (I think www.mesa3d.org)
THat's an openGL clone.

#################################################################

Then I tried to compile the GRID3D with one error (well 4 errors):

make[4]: *** [/usr/local/grass-5.0b/etc/bin/main/cmd/r3.mapcalc] Error 1
make[3]: *** [all] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all] Error 1
make: *** [all] Error 2

You will need "flex" and "yacc" o/ "bison" program. Also available somewhere.

I did not try to compile PostgreSQL..

Heres the error.log:

Compilation error in module: src/display/d.colors (ignored)
Compilation error in module: src/general/g.help (ignored)
Compilation error in module: src/imagery/i.class (ignored)
Compilation error in module: src/imagery/i.ortho.photo (ignored)
Compilation error in module: src/imagery/i.points (ignored)
Compilation error in module: src/imagery/i.points3 (ignored)
Compilation error in module: src/imagery/i.vpoints (ignored)
Compilation error in module: src/mapdev/v.geom (ignored)
Compilation error in module: src/mapdev/v.in.shape (ignored)
Compilation error in module: src/mapdev/v.mkgrid (ignored)
Compilation error in module: src/mapdev/v.out.shape (ignored)
Compilation error in module: src/mapdev/v.rmdup (ignored)

-> please send detailed errors

Compilation error in module: src/raster/r.binfer (ignored)

-> bison + flex

Compilation error in module: src/raster/r.flowmd (ignored)
Compilation error in module: src/raster/r.in.dem (ignored)

-> please send detailed errors

Compilation error in module: src/raster/r.in.png (ignored)

-> PNG graphic library

Compilation error in module: src/raster/r.mapcalc (ignored)

-> bison + flex

Compilation error in module: src/raster/r.out.png (ignored)

-> PNG graphic library

Compilation error in module: src/raster/r.random (ignored)

-> please send detailed errors

Compilation error in module: src/raster/r.tiff (ignored)

-> TIFF graphic library

Compilation error in module: src/raster/wildfire (ignored)
Compilation error in module: src/sites/s.kcv (ignored)

-> please send detailed errors

Compilation error in module: src/sites/s.rand (ignored)

this is now s.random (cvs update -dP will remove the old one)

Compilation error in module: src.contrib/CERL/raster/r.hydro.CASC2D (ignored)
Compilation error in module: src.contrib/SCS/misc/m.lulc.USGS (ignored)
Compilation error in module: src.contrib/SDTS (ignored)

-> please send detailed errors

Compilation error in module:
src.garden/answers/src.answers/raster/r.fill.dir (ignored)

-> f77/g77 fortran compiler required

Hope this helps. After installing these further requirements
most of the code should compile.

Regards

Markus

PS: if ready, please upload the binaries
to ftp 130.75.72.14
/incoming

make bindist
will package it for you. Please put the generated grass5install.sh script
onto the server, too.

Thanks!

Markus

--
Dipl.-Geogr. Markus Neteler * University of Hannover
Institute of Physical Geography and Landscape Ecology
Schneiderberg 50 * D-30167 Hannover * Germany
Tel: ++49-(0)511-762-4494 Fax: -3984

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Andreas_Lange1 · November 12, 2000, 4:31pm

Hi Bernhard, Hi Markus,

i looked at the bugzilla bug tracker recently and i think that a fully
fledged bug-tracking system for grass is too much work.

Such a system would require:
- setting up and maintaining the backend/server sofware (at
intevation.de?)
- checking in all known bugs into the system
- every developer maintaining the entries in the bug database etc.
- just more work for the bugfixing people that gets subtracted from the
available time.

I would propose the following:
unifing (simplifying?) of the bug report form on
http://www.geog.uni-hannover.de/grass/bugtracking/bugreport.html, the
script bug.report.sh from src/scripts/shells and other areas where this
is used;

add a menue to tcltkgrass for bug reporting (i can do that);

set up a mail alias ("grass-bugs@???") where all bug mails are sent
to;

these mails should be archived somewhere where the developers can read
them and could be automatically forwarded to grass5. The report form
should be changed so that name and email can be anonymized (is this a
concern? i don't know.).

Perhaps we should make a distinction between "compiling bugs" and
"functionality bugs/module errors". One problem with the latter is that
information on the grass database is needed to inspect them.

cu,

Andreas

Bernhard Reiter wrote:

On Tue, Nov 07, 2000 at 04:52:54PM +0000, Markus Neteler wrote:
> On Tue, Nov 07, 2000 at 10:57:37AM -0500, Eric Mitchell wrote:

> > If all you gain from going to sourceforge is a bug tracker,

> .. therefore I was proposing "Issuezilla" (www.openoffice.org,
> see " Bugs and Issues") which was developed on top of bugzilla.
> Their intention at openoffice is to provide a system catching
> improvement suggestions, too. I think that's a good idea.
>
> The only question is: Do we need that? Maybe yes. I feel we
> need a "suggestions system" beside our current manually runung
> bug-system.

Well we are certainly willing to set a system up, if you feel like you
need it.

It will have some more overhead.
I am not sure were the difference is between a bug tracking system with
different types of bugs (which one type could be the suggestions)
and an issue system. Actually most bug-tracking systems are usd for
wishlists, also.

Of course it would be beter if people used the mailinglists, so they
can explain their wishes and bugs, if necessary.

A better description on how to report a bug is always a way to improve,
too.

Bernhard

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Jeshua_Lacock1 · November 12, 2000, 11:14pm

On Sun, Nov 12, 2000 at 12:31:10AM -0800, Jeshua Lacock wrote:
> Hoooooray!

> ###############################################################
> /Users/jeshua/grassb8/src/libes/ogsf
> make -f OBJ.powerpc-apple-nextstep3/make.rules

Here you need the "MESA" package:
/usr/include/GL/gl.h

See grass5 web page for mesa url (I think www.mesa3d.org)
THat's an openGL clone.

I've downloaded it and will soon try...

> ###############################################################
>

Then I tried to compile the GRID3D with one error (well 4 errors):

make[4]: *** [/usr/local/grass-5.0b/etc/bin/main/cmd/r3.mapcalc] Error 1
make[3]: *** [all] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all] Error 1
make: *** [all] Error 2

You will need "flex" and "yacc" o/ "bison" program. Also available somewhere.

I have GNU bison, I'll try installing and building it...

Here is the output copied from the terminal window for the modules that you (Markus) requested. Some modules did not have any (helpful) error information - in these cases, I've copied the full logs versus just the error...

THANKS ALL!! I can't wait to start using this super-powerful package!

** warning long list follows **
______________________________________________________________

Compilation error in module: src/display/d.colors (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/main/cmd/d.colors OBJ.powerpc-apple-nextstep3/curses.o OBJ.powerpc-apple-nextstep3/sigint.o OBJ.powerpc-apple-nextstep3/set_sigs.o OBJ.powerpc-apple-nextstep3/get_info.o OBJ.powerpc-apple-nextstep3/interact.o OBJ.powerpc-apple-nextstep3/tbl_toggle.o OBJ.powerpc-apple-nextstep3/tty.o OBJ.powerpc-apple-nextstep3/main.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/display/d.colors

______________________________________________________________

Compilation error in module: src/general/g.help (ignored):

GISGEN: src/general/g.help - Sun Nov 12 02:19:31 PST 2000

###############################################################
/Users/jeshua/grassb8/src/general/g.help
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
mv main.o OBJ.powerpc-apple-nextstep3/main.o
rm -f OBJ.powerpc-apple-nextstep3/do_leave.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c do_leave.c
mv do_leave.o OBJ.powerpc-apple-nextstep3/do_leave.o
rm -f OBJ.powerpc-apple-nextstep3/tty.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c tty.c
mv tty.o OBJ.powerpc-apple-nextstep3/tty.o
rm -f OBJ.powerpc-apple-nextstep3/menu.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c menu.c
GISGEN failure at STEP: src/general/g.help

______________________________________________________________

Compilation error in module: src/imagery/i.class (ignored):

cc -o /usr/local/grass-5.0b/etc/bin/main/inter/i.class OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/add_point.o OBJ.powerpc-apple-nextstep3/analyze_sig.o OBJ.powerpc-apple-nextstep3/ask_files.o OBJ.powerpc-apple-nextstep3/band_files.o OBJ.powerpc-apple-nextstep3/cellhd.o OBJ.powerpc-apple-nextstep3/complete_reg.o OBJ.powerpc-apple-nextstep3/conv.o OBJ.powerpc-apple-nextstep3/curses.o OBJ.powerpc-apple-nextstep3/define_reg.o OBJ.powerpc-apple-nextstep3/del_point.o OBJ.powerpc-apple-nextstep3/draw_reg.o OBJ.powerpc-apple-nextstep3/draw_cell.o OBJ.powerpc-apple-nextstep3/driver.o OBJ.powerpc-apple-nextstep3/edge.o OBJ.powerpc-apple-nextstep3/edge_order.o OBJ.powerpc-apple-nextstep3/edge_point.o OBJ.powerpc-apple-nextstep3/erase_reg.o OBJ.powerpc-apple-nextstep3/g_init.o OBJ.powerpc-apple-nextstep3/graphics.o OBJ.powerpc-apple-nextstep3/histograms.o OBJ.powerpc-apple-nextstep3/init_reg.o OBJ.powerpc-apple-nextstep3/input.o OBJ.powerpc-apple-nextstep3/input_color.o OBJ.powerpc-apple-nextstep3/input_std.o OBJ.powerpc-apple-nextstep3/mouse.o OBJ.powerpc-apple-nextstep3/outline.o OBJ.powerpc-apple-nextstep3/readbands.o OBJ.powerpc-apple-nextstep3/redisplay.o OBJ.powerpc-apple-nextstep3/remove_mask.o OBJ.powerpc-apple-nextstep3/restore_reg.o OBJ.powerpc-apple-nextstep3/save_reg.o OBJ.powerpc-apple-nextstep3/set_signals.o OBJ.powerpc-apple-nextstep3/sigalarm.o OBJ.powerpc-apple-nextstep3/sigint.o OBJ.powerpc-apple-nextstep3/signature.o OBJ.powerpc-apple-nextstep3/title.o OBJ.powerpc-apple-nextstep3/tty.o OBJ.powerpc-apple-nextstep3/view.o OBJ.powerpc-apple-nextstep3/zoom_box.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libI.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libD.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvask.a /usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/imagery/i.class

______________________________________________________________

Compilation error in module: src/imagery/i.ortho.photo/photo.2image (ignored):

cc -I../libes -o /usr/local/grass-5.0b/etc/imagery/photo.2image OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/ask.o OBJ.powerpc-apple-nextstep3/ask_mag.o OBJ.powerpc-apple-nextstep3/analyze.o OBJ.powerpc-apple-nextstep3/call.o OBJ.powerpc-apple-nextstep3/cell.o OBJ.powerpc-apple-nextstep3/cellhd.o OBJ.powerpc-apple-nextstep3/colors.o OBJ.powerpc-apple-nextstep3/conv.o OBJ.powerpc-apple-nextstep3/curses.o OBJ.powerpc-apple-nextstep3/dot.o OBJ.powerpc-apple-nextstep3/drawcell.o OBJ.powerpc-apple-nextstep3/drawcam.o OBJ.powerpc-apple-nextstep3/driver.o OBJ.powerpc-apple-nextstep3/equ.o OBJ.powerpc-apple-nextstep3/find.o OBJ.powerpc-apple-nextstep3/graphics.o OBJ.powerpc-apple-nextstep3/group.o OBJ.powerpc-apple-nextstep3/input.o OBJ.powerpc-apple-nextstep3/mark.o OBJ.powerpc-apple-nextstep3/mouse.o OBJ.powerpc-apple-nextstep3/points.o OBJ.powerpc-apple-nextstep3/target.o OBJ.powerpc-apple-nextstep3/title.o OBJ.powerpc-apple-nextstep3/tty.o OBJ.powerpc-apple-nextstep3/view.o OBJ.powerpc-apple-nextstep3/where.o OBJ.powerpc-apple-nextstep3/zoom.o OBJ.powerpc-apple-nextstep3/zoom_box.o OBJ.powerpc-apple-nextstep3/zoom_pnt.o OBJ.powerpc-apple-nextstep3/use_camera.o ./libes/LIB.powerpc-apple-nextstep3/libortho.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libI.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libD.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvask.a /usr/bin/ld: warning table of contents of library: ./libes/LIB.powerpc-apple-nextstep3/libortho.a not sorted slower link editing will result (use the ranlib(1) -s option)
/usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/imagery/i.ortho.photo

______________________________________________________________

Compilation error in module: src/imagery/i.points (ignored):

cc -o /usr/local/grass-5.0b/etc/bin/main/inter/i.points OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/ask.o OBJ.powerpc-apple-nextstep3/ask_mag.o OBJ.powerpc-apple-nextstep3/analyze.o OBJ.powerpc-apple-nextstep3/call.o OBJ.powerpc-apple-nextstep3/cell.o OBJ.powerpc-apple-nextstep3/cellhd.o OBJ.powerpc-apple-nextstep3/conv.o OBJ.powerpc-apple-nextstep3/colors.o OBJ.powerpc-apple-nextstep3/curses.o OBJ.powerpc-apple-nextstep3/debug.o OBJ.powerpc-apple-nextstep3/digit.o OBJ.powerpc-apple-nextstep3/dot.o OBJ.powerpc-apple-nextstep3/drawcell.o OBJ.powerpc-apple-nextstep3/driver.o OBJ.powerpc-apple-nextstep3/equ.o OBJ.powerpc-apple-nextstep3/find.o OBJ.powerpc-apple-nextstep3/graphics.o OBJ.powerpc-apple-nextstep3/group.o OBJ.powerpc-apple-nextstep3/input.o OBJ.powerpc-apple-nextstep3/mark.o OBJ.powerpc-apple-nextstep3/mouse.o OBJ.powerpc-apple-nextstep3/points.o OBJ.powerpc-apple-nextstep3/target.o OBJ.powerpc-apple-nextstep3/title.o OBJ.powerpc-apple-nextstep3/tty.o OBJ.powerpc-apple-nextstep3/view.o OBJ.powerpc-apple-nextstep3/where.o OBJ.powerpc-apple-nextstep3/zoom.o OBJ.powerpc-apple-nextstep3/zoom_box.o OBJ.powerpc-apple-nextstep3/zoom_pnt.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libI.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libD.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/imagery/i.points

______________________________________________________________

Compilation error in module: src/imagery/i.points3/inter (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/main/inter/i.points3 OBJ.powerpc-apple-nextstep3/anal_fid.o OBJ.powerpc-apple-nextstep3/anal_control.o OBJ.powerpc-apple-nextstep3/camera.o OBJ.powerpc-apple-nextstep3/camera_mod.o OBJ.powerpc-apple-nextstep3/digit.o OBJ.powerpc-apple-nextstep3/draw_cell.o OBJ.powerpc-apple-nextstep3/draw_grid.o OBJ.powerpc-apple-nextstep3/draw_vect.o OBJ.powerpc-apple-nextstep3/driver.o OBJ.powerpc-apple-nextstep3/expose_mod.o OBJ.powerpc-apple-nextstep3/graph_ask.o OBJ.powerpc-apple-nextstep3/graph_askmag.o OBJ.powerpc-apple-nextstep3/graph_dot.o OBJ.powerpc-apple-nextstep3/graph_init.o OBJ.powerpc-apple-nextstep3/graph_title.o OBJ.powerpc-apple-nextstep3/input.o OBJ.powerpc-apple-nextstep3/list_colors.o OBJ.powerpc-apple-nextstep3/list_group.o OBJ.powerpc-apple-nextstep3/list_target.o OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/mark_fid.o OBJ.powerpc-apple-nextstep3/mark_control.o OBJ.powerpc-apple-nextstep3/mouse.o OBJ.powerpc-apple-nextstep3/overlay.o OBJ.powerpc-apple-nextstep3/plot.o OBJ.powerpc-apple-nextstep3/plot_cell.o OBJ.powerpc-apple-nextstep3/plot_grid.o OBJ.powerpc-apple-nextstep3/plot_vect.o OBJ.powerpc-apple-nextstep3/read_elev.o OBJ.powerpc-apple-nextstep3/target.o OBJ.powerpc-apple-nextstep3/text_tty.o OBJ.powerpc-apple-nextstep3/transform.o OBJ.powerpc-apple-nextstep3/view_config.o OBJ.powerpc-apple-nextstep3/view_clear.o OBJ.powerpc-apple-nextstep3/view_colors.o OBJ.powerpc-apple-nextstep3/view_conv.o OBJ.powerpc-apple-nextstep3/view_outline.o OBJ.powerpc-apple-nextstep3/view_points.o OBJ.powerpc-apple-nextstep3/view_refresh.o OBJ.powerpc-apple-nextstep3/view_where.o OBJ.powerpc-apple-nextstep3/zoom_box.o OBJ.powerpc-apple-nextstep3/zoom_pnt.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libI.a /Users/jeshua/grassb8/src/libes/image3/LIB.powerpc-apple-nextstep3/libimage_sup.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libD.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvect.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdig2.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libproj.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvask.a /usr/bin/ld: warning table of contents of library: /Users/jeshua/grassb8/src/libes/image3/LIB.powerpc-apple-nextstep3/libimage_sup.a not sorted slower link editing will result (use the ranlib(1) -s option)
/usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/imagery/i.points3

______________________________________________________________

Compilation error in module: src/imagery/i.vpoints (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/main/inter/i.vpoints OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/ask.o OBJ.powerpc-apple-nextstep3/ask_mag.o OBJ.powerpc-apple-nextstep3/analyze.o OBJ.powerpc-apple-nextstep3/call.o OBJ.powerpc-apple-nextstep3/cell.o OBJ.powerpc-apple-nextstep3/cellhd.o OBJ.powerpc-apple-nextstep3/conv.o OBJ.powerpc-apple-nextstep3/colors.o OBJ.powerpc-apple-nextstep3/curses.o OBJ.powerpc-apple-nextstep3/crs.o OBJ.powerpc-apple-nextstep3/debug.o OBJ.powerpc-apple-nextstep3/digit.o OBJ.powerpc-apple-nextstep3/dot.o OBJ.powerpc-apple-nextstep3/drawcell.o OBJ.powerpc-apple-nextstep3/drawvect.o OBJ.powerpc-apple-nextstep3/driver.o OBJ.powerpc-apple-nextstep3/equ.o OBJ.powerpc-apple-nextstep3/find.o OBJ.powerpc-apple-nextstep3/graphics.o OBJ.powerpc-apple-nextstep3/group.o OBJ.powerpc-apple-nextstep3/input.o OBJ.powerpc-apple-nextstep3/mark.o OBJ.powerpc-apple-nextstep3/mouse.o OBJ.powerpc-apple-nextstep3/plot1.o OBJ.powerpc-apple-nextstep3/plot2.o OBJ.powerpc-apple-nextstep3/points.o OBJ.powerpc-apple-nextstep3/setup.o OBJ.powerpc-apple-nextstep3/target.o OBJ.powerpc-apple-nextstep3/title.o OBJ.powerpc-apple-nextstep3/tty.o OBJ.powerpc-apple-nextstep3/use_plot1.o OBJ.powerpc-apple-nextstep3/view.o OBJ.powerpc-apple-nextstep3/where.o OBJ.powerpc-apple-nextstep3/zoom.o OBJ.powerpc-apple-nextstep3/zoom_box.o OBJ.powerpc-apple-nextstep3/zoom_pnt.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libI.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libD.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdisplay.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libraster.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvect.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdig2.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /usr/bin/ld: Undefined symbols:
_gtty
_stty
GISGEN failure at STEP: src/imagery/i.vpoints

______________________________________________________________

Compilation error in module: src/mapdev/v.geom/sos (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/contrib/cmd/v.geom OBJ.powerpc-apple-nextstep3/main.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libvect.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdig2.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdig_atts.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/liboptri.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libsos.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/liblia.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libbasic.a /usr/bin/ld: Undefined symbols:
_GLOBAL_INTERRUPT_ALGORITHM
_gcvt
GISGEN failure at STEP: src/mapdev/v.geom

______________________________________________________________

Compilation error in module: src/mapdev/v.in.shape (ignored)

GISGEN: src/mapdev/v.in.shape - Sun Nov 12 02:44:41 PST 2000

#############################################################
/Users/jeshua/grassb8/src/mapdev/v.in.shape
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
mv main.o OBJ.powerpc-apple-nextstep3/main.o
rm -f OBJ.powerpc-apple-nextstep3/shpopen.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c shpopen.c
mv shpopen.o OBJ.powerpc-apple-nextstep3/shpopen.o
rm -f OBJ.powerpc-apple-nextstep3/dbfopen.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c dbfopen.c
mv dbfopen.o OBJ.powerpc-apple-nextstep3/dbfopen.o
rm -f OBJ.powerpc-apple-nextstep3/dbutils.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c dbutils.c
mv dbutils.o OBJ.powerpc-apple-nextstep3/dbutils.o
rm -f OBJ.powerpc-apple-nextstep3/shp2dig.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c shp2dig.c
GISGEN failure at STEP: src/mapdev/v.in.shape

______________________________________________________________

Compilation error in module: src/mapdev/v.mkgrid (ignored)

GISGEN: src/mapdev/v.mkgrid - Sun Nov 12 02:45:35 PST 2000

###############################################################
/Users/jeshua/grassb8/src/mapdev/v.mkgrid
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/mkgrid_cmd.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c mkgrid_cmd.c
mv mkgrid_cmd.o OBJ.powerpc-apple-nextstep3/mkgrid_cmd.o
rm -f OBJ.powerpc-apple-nextstep3/init_head.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c init_head.c
mv init_head.o OBJ.powerpc-apple-nextstep3/init_head.o
rm -f OBJ.powerpc-apple-nextstep3/write_grid.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c write_grid.c
mv write_grid.o OBJ.powerpc-apple-nextstep3/write_grid.o
rm -f OBJ.powerpc-apple-nextstep3/rotate.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c rotate.c
mv rotate.o OBJ.powerpc-apple-nextstep3/rotate.o
rm -f OBJ.powerpc-apple-nextstep3/grid_atts.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c grid_atts.c
GISGEN failure at STEP: src/mapdev/v.mkgrid

______________________________________________________________

Compilation error in module: src/mapdev/v.out.shape (ignored)

GISGEN: src/mapdev/v.out.shape - Sun Nov 12 02:46:48 PST 2000

###############################################################
/Users/jeshua/grassb8/src/mapdev/v.out.shape
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/extract.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c extract.c
GISGEN failure at STEP: src/mapdev/v.out.shape

______________________________________________________________

Compilation error in module: src/mapdev/v.rmdup (ignored)

GISGEN: src/mapdev/v.rmdup - Sun Nov 12 02:47:30 PST 2000

###############################################################
/Users/jeshua/grassb8/src/mapdev/v.rmdup
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

/Users/jeshua/grassb8/src/CMD/gmake5.0 cmd
###############################################################
/Users/jeshua/grassb8/src/mapdev/v.rmdup/cmd
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/rmdup.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c rmdup.c
GISGEN failure at STEP: src/mapdev/v.rmdup

______________________________________________________________

Compilation error in module: src/raster/r.flowmd (ignored)

GISGEN: src/raster/r.flowmd - Sun Nov 12 03:03:42 PST 2000

###############################################################
/Users/jeshua/grassb8/src/raster/r.flowmd
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/rflow5f_1.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c rflow5f_1.c
GISGEN failure at STEP: src/raster/r.flowmd

______________________________________________________________

Compilation error in module: src/raster/r.in.dem (ignored)

GISGEN: src/raster/r.in.dem - Sun Nov 12 03:04:04 PST 2000

###############################################################
/Users/jeshua/grassb8/src/raster/r.in.dem
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
mv main.o OBJ.powerpc-apple-nextstep3/main.o
rm -f OBJ.powerpc-apple-nextstep3/dem_read.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c dem_read.c
GISGEN failure at STEP: src/raster/r.in.dem

______________________________________________________________

Compilation error in module: src/raster/r.random/cmd (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/main/cmd/r.random OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/count.o OBJ.powerpc-apple-nextstep3/creat_rand.o OBJ.powerpc-apple-nextstep3/random.o OBJ.powerpc-apple-nextstep3/support.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdatetime.a /usr/bin/ld: Undefined symbols:
_lrand48
_srand48
GISGEN failure at STEP: src/raster/r.random

______________________________________________________________

Compilation error in module: src/raster/wildfire (ignored)

GISGEN: src/raster/wildfire - Sun Nov 12 03:14:27 PST 2000

###############################################################
/Users/jeshua/grassb8/src/raster/wildfire
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

/Users/jeshua/grassb8/src/CMD/gmake5.0 src
###############################################################
/Users/jeshua/grassb8/src/raster/wildfire/src
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

/Users/jeshua/grassb8/src/CMD/gmake5.0 -all
###############################################################
/Users/jeshua/grassb8/src/raster/wildfire/src/r.ros
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
mv main.o OBJ.powerpc-apple-nextstep3/main.o
rm -f OBJ.powerpc-apple-nextstep3/spot_dist.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c spot_dist.c
mv spot_dist.o OBJ.powerpc-apple-nextstep3/spot_dist.o
cc -o /usr/local/grass-5.0b/etc/bin/main/cmd/r.ros OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/spot_dist.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdatetime.a
###############################################################
/Users/jeshua/grassb8/src/raster/wildfire/src/r.spread
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
mv main.o OBJ.powerpc-apple-nextstep3/main.o
rm -f OBJ.powerpc-apple-nextstep3/collect_ori.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c collect_ori.c
mv collect_ori.o OBJ.powerpc-apple-nextstep3/collect_ori.o
rm -f OBJ.powerpc-apple-nextstep3/display.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c display.c
mv display.o OBJ.powerpc-apple-nextstep3/display.o
rm -f OBJ.powerpc-apple-nextstep3/insertHa.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c insertHa.c
mv insertHa.o OBJ.powerpc-apple-nextstep3/insertHa.o
rm -f OBJ.powerpc-apple-nextstep3/spread.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c spread.c
mv spread.o OBJ.powerpc-apple-nextstep3/spread.o
rm -f OBJ.powerpc-apple-nextstep3/deleteHa.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c deleteHa.c
mv deleteHa.o OBJ.powerpc-apple-nextstep3/deleteHa.o
rm -f OBJ.powerpc-apple-nextstep3/insert2Ha.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c insert2Ha.c
mv insert2Ha.o OBJ.powerpc-apple-nextstep3/insert2Ha.o
rm -f OBJ.powerpc-apple-nextstep3/replaceHa.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c replaceHa.c
mv replaceHa.o OBJ.powerpc-apple-nextstep3/replaceHa.o
rm -f OBJ.powerpc-apple-nextstep3/get_minHa.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c get_minHa.c
mv get_minHa.o OBJ.powerpc-apple-nextstep3/get_minHa.o
rm -f OBJ.powerpc-apple-nextstep3/fixHa.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c fixHa.c
mv fixHa.o OBJ.powerpc-apple-nextstep3/fixHa.o
rm -f OBJ.powerpc-apple-nextstep3/ram2out.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c ram2out.c
mv ram2out.o OBJ.powerpc-apple-nextstep3/ram2out.o
rm -f OBJ.powerpc-apple-nextstep3/select_linksB.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c select_linksB.c
mv select_linksB.o OBJ.powerpc-apple-nextstep3/select_linksB.o
rm -f OBJ.powerpc-apple-nextstep3/spot.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c spot.c
mv spot.o OBJ.powerpc-apple-nextstep3/spot.o
rm -f OBJ.powerpc-apple-nextstep3/pick_dist.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c pick_dist.c
GISGEN failure at STEP: src/raster/wildfire

______________________________________________________________

Compilation error in module: src/sites/s.kcv (ignored)

cc -o /usr/local/grass-5.0b/etc/bin/contrib/cmd/s.kcv OBJ.powerpc-apple-nextstep3/main.o OBJ.powerpc-apple-nextstep3/dreset.o OBJ.powerpc-apple-nextstep3/readsite.o OBJ.powerpc-apple-nextstep3/histo.o OBJ.powerpc-apple-nextstep3/utils.o /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libgis.a /Users/jeshua/grassb8/src/libes/LIB.powerpc-apple-nextstep3/libdatetime.a /usr/bin/ld: Undefined symbols:
_drand48
_srand48
GISGEN failure at STEP: src/sites/s.kcv

______________________________________________________________

Compilation error in module: src.contrib/CERL/raster/r.hydro.CASC2D (ignored)

GISGEN: src.contrib/CERL/raster/r.hydro.CASC2D - Sun Nov 12 03:22:21 PST 2000

###############################################################
/Users/jeshua/grassb8/src.contrib/CERL/raster/r.hydro.CASC2D
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/CASC2D.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c CASC2D.c
GISGEN failure at STEP: src.contrib/CERL/raster/r.hydro.CASC2D

________________________________________________________________

Compilation error in module: src.contrib/SCS/misc/m.lulc.USGS (ignored)

GISGEN: src.contrib/SCS/misc/m.lulc.USGS - Sun Nov 12 03:27:24 PST 2000

###############################################################
/Users/jeshua/grassb8/src.contrib/SCS/misc/m.lulc.USGS
mkdir OBJ.powerpc-apple-nextstep3
make -f OBJ.powerpc-apple-nextstep3/make.rules

rm -f OBJ.powerpc-apple-nextstep3/main.o
cc -g -O2 -I/Users/jeshua/grassb8/src/include -c main.c
GISGEN failure at STEP: src.contrib/SCS/misc/m.lulc.USGS

______________________________________________________________

Compilation error in module: src.contrib/SDTS (ignored)

(omitted full logs due to length - no errors other then:)

GISGEN failure at STEP: src.contrib/SDTS

______________________________________________________________
--
Jeshua Lacock
Cartographer/Owner
http://SierraMaps.com
http://3dTopoMaps.com
Telephone: (760) 935-4481

---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 13, 2000, 10:24am

Hi all,

to get the bug report form independent of me, I have created a
new mailing-list: grass-bugs with *archive*.

The report form and the archive can be accessed here:
http://www.geog.uni-hannover.de/grass/bugtracking/bugreport.html
(it will cc to me)

Shall I cc to the grass5 as well?

Regards

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Eric_Mitchell · November 13, 2000, 4:21pm

Andreas Lange wrote:

i looked at the bugzilla bug tracker recently and i think that a fully
fledged bug-tracking system for grass is too much work.

A properly used defect tracking system is a critical part
of any successful long-term software project. This system
may be manual, in fact I've used a quite successful system
that consisted of one page report forms, filled out by hand,
and stored in a binder. Developers pick a report from the
binder, fix the problem (add the requested feature), staple
a correction report to it, and file it in a "fixed" binder.

Bugzilla is quite a capable system, as evidenced by its
heavy use (and abuse) by the mozilla project.

Such a system would require:
- setting up and maintaining the backend/server sofware (at
intevation.de?)

Once bugzilla is up and running, it needs no more maintenance
than any other network resource. It took me about a day to
set up and initially configure the system, including reading
about mySQL permissions, and adding a few extra permissions
to the webserver.

- checking in all known bugs into the system

Scripts can help with this, and tasks like this are a *great*
way for volunteers with more time than programming experience
to help the project.

- every developer maintaining the entries in the bug database etc.

When a bug gets fixed, that occurrence *must* be noted
somehow, somewhere. Otherwise, you'll get developers trying
to fix bugs more than once, and getting frustrated that the
bug they're trying to track down is already fixed. I remember
hearing a lot about a problem that required an extra compiler
option (-fwritable-strings) on this very project. I went to
investigate the matter only to discover no such problem existed.
Had the bug fix been properly documented, I wouldn't have ever
spent the time trying to fix it. This is also a step that only
has to occur once.

- just more work for the bugfixing people that gets subtracted from the
available time.

Quality software development is not just a matter of hacking
source code. There is a lot of extraneous bits that need to
be worked on as well. Tracking defects is but a small part
of that.

I would propose the following:
unifing (simplifying?) of the bug report form on
http://www.geog.uni-hannover.de/grass/bugtracking/bugreport.html, the
script bug.report.sh from src/scripts/shells and other areas where this
is used;

add a menue to tcltkgrass for bug reporting (i can do that);

set up a mail alias ("grass-bugs@???") where all bug mails are sent
to;

these mails should be archived somewhere where the developers can read
them and could be automatically forwarded to grass5. The report form
should be changed so that name and email can be anonymized (is this a
concern? i don't know.).

I believe that bugzilla has a feature by which properly
formatted mail messages can be imported as bug reports.
If not, someone with a spare day or two could implement
the feature. Bug report summaries could be sent to the
mailing list every day/week or so.

Perhaps we should make a distinction between "compiling bugs" and
"functionality bugs/module errors". One problem with the latter is that
information on the grass database is needed to inspect them.

cu,

Andreas

Not that I think bugzilla is the perfect bug tracking system,
but it works well for several large open development efforts.
I'm not familiar with the current bug reporting features used
by GRASS, either.

I think it would be constructive for someone to set up bugzilla
in a "sandbox" in which the developers could play with it, and
get a feel for the system in general.

-- ebm
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:emitchell@altaira.com |
| tel: (301) 809 - 3534 Altair Aerospace Corporation |
| tel: (800) 7 - ALTAIR 4201 Northview Dr. Suite 410 |
| fax: (301) 805 - 8122 Bowie, MD 20716 |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
              ,___
          /"\ / o=\ /"""---===/
         / \_/ \__/ ---===/
         | //\ || /""TT""/ //\ || ||""\
         | // \ || || // \ || ||__/
         | //--==\ |L--/ || //--==\ || || "=,
          \ ---===/
           \____---===/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 13, 2000, 5:53pm

On Mon, Nov 13, 2000 at 11:21:11AM -0500, Eric Mitchell wrote:
[...]

When a bug gets fixed, that occurrence *must* be noted
somehow, somewhere. Otherwise, you'll get developers trying
to fix bugs more than once, and getting frustrated that the
bug they're trying to track down is already fixed. I remember
hearing a lot about a problem that required an extra compiler
option (-fwritable-strings) on this very project. I went to
investigate the matter only to discover no such problem existed.
Had the bug fix been properly documented, I wouldn't have ever
spent the time trying to fix it. This is also a step that only
has to occur once.

Hi Eric, hi all,

I will send another mail on the bugtracking issue later.

Looking at your comment:
Is the -fwritable-strings bug gone? That's great. Then I will
remove this hint from

BUGS and
src/CMD/generic/POST_INSTALL.sh

Thanks

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 13, 2000, 6:07pm

Hi all,

thanks for yll your useful comments!
Current status:

- bug report form:
  Bereich Geographie – Naturwissenschaftliche Fakultät – Leibniz Universität Hannover
-> this form is generating a mail to grass-bugs@geog.uni-hannover.de
    and neteler@geog.uni-hannover.de (cc)
  since today.

- grass-bugs archive:
http://www.geog.uni-hannover.de/cgi-bin/minorweb.pl?A=LIST&L=grass-bugs

That's the "trivial" approach.

Bernhard and Frank Warmerdam have offered to set up bugzilla,
either at intevation.de or www.remotesensing.org.

bugzilla offers beside bug reports a form for suggestions as well.

It seems most of the experienced (professional) programmers tend
to start a grass-bugzilla.

IMHO such a system, which is independent from a person (like our current
simple system is since today), is quite valuable. Question is how much
we have to learn to manage bugzilla. At least me I am unexperienced with
that, but even learned CVS a while ago (and love it!)

Currently we have numerous bugs listed in BUGS. I am rather sure
that at least 3-5 bugs are listed, but already fixed. I am willing
to participate in "bug-uploading". But we should only migrate
bugs which can be reproduced.

Concerning the bug.report.sh script:
Perhaps it could post directly to bugzilla. But most people are offline,
so they cannot make to much use of it. I guess, we need it heavily modified
to be real help.

Conclusion: From my side we should try the bugzilla-experiment. Then
it is less dependent from my person (currently I am obviously beside
Andreas the only person modifying BUGS). With increasing numbers of
programmers in this project, more people may take over the "bugs
management".

If the others agree, perhaps Bernhard and Frank W. may discuss who would
set up grass-bugzilla.

Regards

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 14, 2000, 3:43pm

Hi Bernhard,

On Tue, Nov 14, 2000 at 03:37:30PM +0100, Bernhard Reiter wrote:
[...]

We will set a bugtracking system up at intevation, because this is close
to the cvs server. For the last hour I was looking at several bug
tracking systems. My criteria are:
  - usable WWW interface
  - can be controled by email
  - (free software)
  - maintainable source code (I perfer python )

At least jitterbug, bugzilla, gnats, debian bug tracking system
need to be considered. I will probably do this within a week.
Is this fast enough?

..of course!

My preference is on "simplicity". If the users don't understand how
to report a bug, they won't do. Issezilla looks too complex.
Another problem: If "create an account" is required before you
can report, this is preventing many users to report, too.

A straight-forward approach is here:
http://r-bugs.biostat.ku.dk/cgi-bin/R
(the "R" statistical language system, I think based on jitterbug).

It's easy to use, even for newbies.

Thank you very much for setting up such a system,

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · November 17, 2000, 2:16pm

Hi all,

unless a new bugtracking system is not yet running, I have
the grass-bugs mailing list available.

If you want to subscribe, go here:
http://www.geog.uni-hannover.de/grass/grassdevel.html#todo

There is a new form for easy [un]subscription.

Regards

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

neteler · December 17, 2000, 5:16pm

Hi Bernhard, Hi Frank W.,

once we had this thread on a bug tracking system for GRASS.
I am not sure if you will set up such a system or not (and
whom). Please report a short status...

The mailing list based report system is quite unused, so it
doesn't seem to be a widely accepted tool.

Thanks

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'