[GRASS5] Win32 compile with cygnus ...

GRASS GRASS developer
1

Hi 2 all,

i will answer all the recent mails on this topic in one mail, i am in a
hurry today.

- netpbm:
I tried to recompile the netpbm 9.8 source with cygnus. Does not work.
The makefile target does not build the libraries and headers, only the
binaries, so that it is of no value for the build of r.in.png/r.out.png.
The binary tarball i found on the net does _not_ contain the header
files.
So no luck to compile this on Win32.
To put this right: the r.in.png/r.out.png do _not_ use the
code/binaries/libraries from the netpbm utils as far as i could see (can
Alex Shevlakov please comment on this?). They only need the header file,
so that we could check this file(s) in to src/include if there are no
licensing issues. There is no using of the common format approach James
Cameron describes in his mail, so no dependency on netpbm tools. But i
think that if you do graphics with script programming you should have
the netpbm tools installed.

- Perl/g.html2man (to Michel Wuerz)
The cygwin setup consists of nearly all the GNU tools (bash, sed, gawk,
m4 etc etc.), because the autotools (automake, autoconfig, autoheader
etc.) depend on them. I think that perl is not installed by default
because of size limits. On NT i have installed a NT Perl build, because
it is integrated with Win (registry manipulation etc.). I personally
have no problem with perl as a prerequisite, but i think that only the
man page generation does not justify that. The man program is included
in cygwin. Perhaps there is a Perl2c converter? I only know of awk2perl
and sed2perl converters.
The other option i described was that the html2man conversion is done
centrally and the man files checked in to the CVS repository. The
generation/compiling mechanism makes sense IMHO only if you prepare
something that is taylored to the target architecture and / or changed
so frequently that is must be rebuild locally. Both is not the case with
the man pages.

- float.h header file
I fear i mixed this up with something else. float.h should be ok.
Is there any solution to the problem of the missing values.h file ?
I think that manually creation of this file is no viable solution.

- configure.in
I tried to add the XDR/rpclib seek that Mike Thomas advised and some
other things to configure.in, but i can't build the configure script
(autoconf 2.13 installed).
If someone hacked something directly into configure this is very bad.
The following should be added to configure.in:
AC_PROG_YACC, and replace bison -y with @YACC@ in the header file.
XDR: this library is named librpclib on win -> rpclib to add.
some checks for sys/ipc.h and sys/msg.h for the IPC message queue
system.
more library checks.
And the library and include directives in the header file should be
standardized somehow. Some LIBNAME = do not mean the library, but the
library path. Very confusing.
Perhaps someone more autoconf-savy can do this.

- G_* functions.
Sorry, i did not check which functions are available.
But generally i think that using functions from the gis library will
enhance portablility. But this is not much an issue today, with c
standards. The whole thing came IMHO from the pre-ansi time when the
string functions on BSD and SYS V have been very different.
I did not look at the implementation of the functions and some functions
may be unnecessary at all. One advantage of the implementation of string
functions with the gis library is that you don't need to bother about
including the header files.
Before we decide anything on those functions we should look where they
are used.

I changed the problematic re-definition of malloc and realloc in one of
the libraries, should compile now.

- some more problems with the cygwin build:

One program in the src/fonts/for_grass directory (splitfont, but the
problem could be with font_2_bin that writes font.bin) does not work on
Win32, i suspect that it is a problem with text/binary mode difference
on windows. But the program uses open/creat/write, not fopen/fwrite, so
i don't know how to fix this for windows.

The cygnus system lacks "more", so that nearly all programs that use
system("more") to display something do not work. Creating a link (ln -s
/bin/less /bin/more) does not help much, because you have to press "q"
to exit.

The ipc.h and msg.h files are in local/include, so some include
directive must be set on cygwin.

I want to underline that i started the cygwin compile thing only because
i had the impression that we need to solve the windows problems before
we publish the stable version. Otherwise Windwos users will curse on
GRASS and on Unix software generally. I hope to get the X11R6 for
Windows on CD to compile the X windows part.
The windows port still needs a lot of user land testing.

cu,

Andreas

--
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'

2

Hi all.

I want to underline that i started the cygwin compile thing only because
i had the impression that we need to solve the windows problems before
we publish the stable version. Otherwise Windwos users will curse on
GRASS and on Unix software generally. I hope to get the X11R6 for
Windows on CD to compile the X windows part.
The windows port still needs a lot of user land testing.

Thanks for the support Andreas.

Here's another problem with a clean cvs updated and ./configured grass
source directory - gmake5.0 is not found even though it is there (maybe a
Cygwin problem?):

mike@SNOWPEA //f/source/cvsroot/grass
$ make install
test -d /usr/local/grass-5.0b || mkdir -p -m 755 /usr/local/grass-5.0b
test -d src/CMD/next_step || mkdir -p src/CMD/next_step
test ! -f src/CMD/head/head || mv src/CMD/head/head
src/CMD/head/head.i586-pc-cy
gwin
UNIX_BIN=/usr/local/bin SRC=//f/source/cvsroot/grass MAKE=make NAME_VER=`cat
src
/CMD/VERSION | head -1 | sed 's/\..*//'` GISBASE=/usr/local/grass-5.0b
MACHINENA
ME=`uname -n` /bin/sh src/CMD/generic/CREATE_GMAKE.sh i586-pc-cygwin
/bin/sh //f/source/cvsroot/grass/src/CMD/generic/is64bit.sh i586-pc-cygwin
Now proceed with make install
GRASSSRC=//f/source/cvsroot/grass/src
GMAKE=//f/source/cvsroot/grass/src/CMD/gma
ke5.0 HEADER=head.i586-pc-cygwin MAKE=make /bin/sh src/CMD/generic/GISGEN.sh
//f/source/cvsroot/grass/src/CMD/gmake5.0: not found
//f/source/cvsroot/grass/src/CMD/gmake5.0: not found
make: *** [do-install] Error 1

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

3

Hi Mike

Mike Thomas wrote:

Here's another problem with a clean cvs updated and ./configured
grass source directory - gmake5.0 is not found even though it is there
(maybe a Cygwin problem?):

This may be caused by the Makefile since gmake5.0 should be named
gmake5. This change was done a few months ago but I don't see why the
file name is gmake5.0 instead of gmake5. Perhaps there is something
wrong with the VERSION or NAME_VER definition in the Makefile?

I'm sorry it's not much help but it is a starting point.

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand

People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!

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

4

Hi Justin.

> Here's another problem with a clean cvs updated and ./configured
> grass source directory - gmake5.0 is not found even though it is there
> (maybe a Cygwin problem?):

This may be caused by the Makefile since gmake5.0 should be named
gmake5. This change was done a few months ago but I don't see why the
file name is gmake5.0 instead of gmake5. Perhaps there is something
wrong with the VERSION or NAME_VER definition in the Makefile?

I checked these variables and they seem OK.

There is a gmake5 script in /usr/local/bin:
---------------------------------------
:
SRC=//f/source/cvsroot/grass/src
CMD=//f/source/cvsroot/grass/src/CMD
HEADER=head.i586-pc-cygwin
HASX=yes
HASMotif=no
MAKE=make
. //f/source/cvsroot/grass/src/CMD/generic/gmake.sh
---------------------------------------

and a gmake5.0 in src/CMD
---------------------------------------
:
SRC=${GRASSSRC}
CMD=${SRC}/CMD
HEADER=${HEADER}
. $CMD/generic/gmake.sh
---------------------------------------

The Makefile sets GMAKE = ${SRCDIR}/src/CMD/gmake5.0 and then calls gmake5.0
via src/CMD/generic/GISGEN.sh which contains early on:

---------------------------------------
# GMAKE must be set outside this script, by CMD/GISGEN

: ${GMAKE?}
$GMAKE -sh
eval `$GMAKE -sh` || exit 1
: ${GISBASE?} ${SRC?} ${CMD?}
---------------------------------------

And it is the middle two lines which cause the problem claiming that the
script is missing twice:
---------------------------------------
$GMAKE -sh
eval `$GMAKE -sh` || exit 1
---------------------------------------

I am no Bash expert, but it seems that not only do these two lines try to
execute the same thing twice, but that under Cygwin they fail because the
script can't be found, even though it is there. (I also tried substituting
the gmake 5 script and got the same problem.

My conclusion is that Cygwin Bash has a bug here.

Never-the-less:

1. Why does BASH seem to execute the same line twice?
2. Why do we need both gmake5 and gmake5.0 and why are the names so
confusing?

Cheers

Mike Thomas.

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

5

Hi Mike, Hi Justin,

sorry that i can not give any useful advice on this.
But i can not confirm this a cygwin bug.
With my cygwin setup (last updated one week ago) ./configure, make, make
install and gmake5 work.

So you could try the following: update cygwin, do a make distclean and
./configure && make && make install again. And/or do a cvs update -dP
before starting the new build.

cu,

Andreas

Mike Thomas wrote:

Hi Justin.

> > Here's another problem with a clean cvs updated and ./configured
> > grass source directory - gmake5.0 is not found even though it is there
> > (maybe a Cygwin problem?):
>
> This may be caused by the Makefile since gmake5.0 should be named
> gmake5. This change was done a few months ago but I don't see why the
> file name is gmake5.0 instead of gmake5. Perhaps there is something
> wrong with the VERSION or NAME_VER definition in the Makefile?

I checked these variables and they seem OK.

There is a gmake5 script in /usr/local/bin:
---------------------------------------
:
SRC=//f/source/cvsroot/grass/src
CMD=//f/source/cvsroot/grass/src/CMD
HEADER=head.i586-pc-cygwin
HASX=yes
HASMotif=no
MAKE=make
. //f/source/cvsroot/grass/src/CMD/generic/gmake.sh
---------------------------------------

and a gmake5.0 in src/CMD
---------------------------------------
:
SRC=${GRASSSRC}
CMD=${SRC}/CMD
HEADER=${HEADER}
. $CMD/generic/gmake.sh
---------------------------------------

The Makefile sets GMAKE = ${SRCDIR}/src/CMD/gmake5.0 and then calls gmake5.0
via src/CMD/generic/GISGEN.sh which contains early on:

---------------------------------------
# GMAKE must be set outside this script, by CMD/GISGEN

: ${GMAKE?}
$GMAKE -sh
eval `$GMAKE -sh` || exit 1
: ${GISBASE?} ${SRC?} ${CMD?}
---------------------------------------

And it is the middle two lines which cause the problem claiming that the
script is missing twice:
---------------------------------------
$GMAKE -sh
eval `$GMAKE -sh` || exit 1
---------------------------------------

I am no Bash expert, but it seems that not only do these two lines try to
execute the same thing twice, but that under Cygwin they fail because the
script can't be found, even though it is there. (I also tried substituting
the gmake 5 script and got the same problem.

My conclusion is that Cygwin Bash has a bug here.

Never-the-less:

1. Why does BASH seem to execute the same line twice?
2. Why do we need both gmake5 and gmake5.0 and why are the names so
confusing?

Cheers

Mike Thomas.

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

--
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'

6

Hello Mike

Mike Thomas wrote:

There is a gmake5 script in /usr/local/bin:
---------------------------------------
:
SRC=//f/source/cvsroot/grass/src
CMD=//f/source/cvsroot/grass/src/CMD
HEADER=head.i586-pc-cygwin
HASX=yes
HASMotif=no
MAKE=make
. //f/source/cvsroot/grass/src/CMD/generic/gmake.sh

    ^^

I think I may have found the problem. It depends on your setup and
cygwin, but these two slashes on a windows machine may be interpreted
(such as in Tcl) as a network file where f would be the machine name. I
assume that f is not a machine name, thus, cygwin may be trying to find
the file on a machine named f instead of the directory f. Thus, you are
getting the error you mentioned in your previous mail (it has the same
//).

Unfortunately, I have no idea where the double slash is coming from. It
appears to be coming from the interpretation of environment variables,
but I'm not sure, I've never used cygwin.

---------------------------------------
# GMAKE must be set outside this script, by CMD/GISGEN

: ${GMAKE?}
$GMAKE -sh
eval `$GMAKE -sh` || exit 1
: ${GISBASE?} ${SRC?} ${CMD?}
---------------------------------------

<skip>

Never-the-less:

1. Why does BASH seem to execute the same line twice?
2. Why do we need both gmake5 and gmake5.0 and why are the names so
confusing?

Good questions.

Markus,

Is the only reason for these two GMAKE lines in GISGEN is to get the
environment variables? These lines don't make very much sense to me. In
fact, there is no Gmakefile to make since a couple of lines before this
there is a "cd /tmp". So, why do we run gmake?

I would suggest we change gmake5.0 to just gmake or maybe grassGmake to
avoid confusion with GNU gmake. What do you think?

Also, why are we accessing CMD/generic/gmake5.0 instead of
UNIX_BIN/gmake5 which was made in the pre-install target? I think we
should change the Makefile to use the UNIX_BIN/gmake5 script instead.

Sorry I couldn't be of much help Mike.

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand

People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!

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

7

Hi Justin.

> . //f/source/cvsroot/grass/src/CMD/generic/gmake.sh
    ^^

I think I may have found the problem. It depends on your setup and
cygwin, but these two slashes on a windows machine may be interpreted
(such as in Tcl) as a network file where f would be the machine name. I
assume that f is not a machine name, thus, cygwin may be trying to find
the file on a machine named f instead of the directory f. Thus, you are
getting the error you mentioned in your previous mail (it has the same
//).

Unfortunately, I have no idea where the double slash is coming from. It
appears to be coming from the interpretation of environment variables,
but I'm not sure, I've never used cygwin.

The // is the Cygwin shortcut for Windows drive letters in Unix like paths.
My email program keeps inserting the "file:" infront of the // because it
thinks it is a network file name as you mentioned.

However, it may be that Cygwin itself is getting confused about the // at
some level!

Sorry I couldn't be of much help Mike.

I learnt something and your time is much appreciated thanks.

Regards

Mike Thomas

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

8

However, it may be that Cygwin itself is getting confused about the // at
some level!

It isn't this - I've reported a bug to GNU for Cygwin BASH anyway.

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

9

Hi guys.

I found the problem. I swapped the Cygwin sh.exe (by default they use
ash.exe) to bash.exe and the problem went away.

Unfortunately the entire OS crashes not long after starting now!

I'm using Win 98 with 64M of RAM and a spare gig of disk to build.

Are you using NT4, NT2000 or W98? My experience is that Cygwin is usually
more stable under NT.

But i can not confirm this a cygwin bug.
With my cygwin setup (last updated one week ago) ./configure, make, make
install and gmake5 work.

I've been updating regularly over that period and got the same problem all
the time.

So you could try the following: update cygwin, do a make distclean and
./configure && make && make install again. And/or do a cvs update -dP
before starting the new build.

I have been using a completely fresh cvs copy each time.

Cheers

Mike Thomas

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

10

On Fri, Nov 24, 2000 at 06:37:40AM +1000, Mike Thomas wrote:

Hi guys.

I found the problem. I swapped the Cygwin sh.exe (by default they use
ash.exe) to bash.exe and the problem went away.

ash should be 100% Bourne Shell compatible. If bash.exe makes the
problem go away, then there must be a "bash-ism" that needs to be
changed.

Unfortunately the entire OS crashes not long after starting now!

That's no good.

--
Eric G. Miller <egm2@jps.net>

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

11

ash should be 100% Bourne Shell compatible. If bash.exe makes the
problem go away, then there must be a "bash-ism" that needs to be
changed.

Could be the underlying Cygwin system too.

> Unfortunately the entire OS crashes not long after starting now!

That's no good.

But unfortunately typical! They recently released a new version of GCC, so
that may be the trouble.

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

12

Hi Mike,

i don't dare to say, but for my first try with cygnus on Win i used an
old computer with Win 95 installed. I exported my local copy of the CVS
tree with samba from a linux machine and mounted it within the cygnus
shell. The multi-OS build of GRASS from a single directory tree works
really.

Now that i know that it generally works i use NT 4.0 SP5 on a computer
with 128 MB RAM. I think that Win 9x is generally not stable enough for
serious work. And i see no chance to get the X11 thing working on Win
9x.

cu,

Andreas

Mike Thomas wrote:

Hi guys.

I found the problem. I swapped the Cygwin sh.exe (by default they use
ash.exe) to bash.exe and the problem went away.

Unfortunately the entire OS crashes not long after starting now!

I'm using Win 98 with 64M of RAM and a spare gig of disk to build.

Are you using NT4, NT2000 or W98? My experience is that Cygwin is usually
more stable under NT.

> But i can not confirm this a cygwin bug.
> With my cygwin setup (last updated one week ago) ./configure, make, make
> install and gmake5 work.

I've been updating regularly over that period and got the same problem all
the time.

> So you could try the following: update cygwin, do a make distclean and
> ./configure && make && make install again. And/or do a cvs update -dP
> before starting the new build.

I have been using a completely fresh cvs copy each time.

Cheers

Mike Thomas

--
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'

13

i don't dare to say, but for my first try with cygnus on Win i used an
old computer with Win 95 installed. I exported my local copy of the CVS
tree with samba from a linux machine and mounted it within the cygnus
shell. The multi-OS build of GRASS from a single directory tree works
really.

Yes I have built OK in the past (a couple of months ago) several times. I
think things are out of whack at the moment with the latest Cygwin on W98.

Thanks to all for the help anyway.

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

14

Markus (Grass list)

I updated my cygwin to the latest, completely removed all grass
code from my drive, checked out grass5, and rebuilt grass5
with only one hitch. The src/cmd/head file still is not right.
More details later, I uploaded the binary tar.gz to the incoming
directory.

http://www.geog.uni-hannover.de/grass/grass5/binary/windows_cygnus/

I see the email about the w98. Clearly, the cygwin code has
disclaimers about using it under Windows 98. I used B20.1
of Cygwin when I used w98. All the grass5 compiled nicely
with it. The B20.1 uses the cygwin32 convention though, and
the config.guess must be adapted to ensure

For those who have NT or Win2000, the install of Cygwin is
more robust than ever, does not conflict with Windows, allows
a Unix environment for windows users. See the URL
http://sources.redhat.com/cygwin/ and download the setup.exe
Execute it from windows explorer or the CMD line, not
from bash. click Next-> first.

Next, it will prompt you to
o) download from the internet
o) install from internet
o) install from local

If you want the binaries (and sources) local, click the first
If you have limited space, click the second
If you have already downloaded from the internet, do the third

I download from the internet to my F: drive first
and then run setup a second time and install on
either my C: or D: drive. The default is the C:\cygwin
which makes the root "/" equal to C:\cygwin. I personally
do not like that since I cannot get at my C: files from /
so I override it with "C:\". It warns me but goes
on.

Finally, the best part is that all the tcl/tk, png,tiff,
and other items required to build grass5 are included
with one exception, the libcygipc.a archive.

So, I am attaching the head file for your use. Some
changes are yacc to bison -y, adding -lcygipc after
XDRLIB. Rename cygwin.txt to the head file as
head.i686-pc-cygwin

Let me know if you need more assistance,

John Huddleston

----- Original Message -----
From: "Mike Thomas" <mthomas@gil.com.au>
To: "grass5" <grass5@geog.uni-hannover.de>
Sent: Friday, November 24, 2000 6:51 AM
Subject: Re: [GRASS5] Win32 compile with cygnus ...

> i don't dare to say, but for my first try with cygnus on Win i used an
> old computer with Win 95 installed. I exported my local copy of the CVS
> tree with samba from a linux machine and mounted it within the cygnus
> shell. The multi-OS build of GRASS from a single directory tree works
> really.

Yes I have built OK in the past (a couple of months ago) several times. I
think things are out of whack at the moment with the latest Cygwin on W98.

Thanks to all for the help anyway.

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

(attachments)

cygwin.txt (2.26 KB)

15

On Fri, Nov 24, 2000 at 08:43:32AM -0700, John Huddleston wrote:

Markus (Grass list)

I updated my cygwin to the latest, completely removed all grass
code from my drive, checked out grass5, and rebuilt grass5
with only one hitch. The src/cmd/head file still is not right.
More details later, I uploaded the binary tar.gz to the incoming
directory.

Bereich Geographie – Naturwissenschaftliche Fakultät – Leibniz Universität Hannover

John,

thanks. It's in place now.

Markus

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

16

Hi John, Hi Markus, Hi Grasslist,

i finished a compile with the latest cygwin setup on NT 4.0 SP 5 in this
minute.
I can now compile all modules from the standard GRASS list file
(including r.in.png and r.out.png).
I'll check in my changes to the CVS in the next days. I'll check in my
head file too.

I have now a running X11R6.4 installation, but can not start grass5 in
the xterm. But i managed somehow to start xwin from the grass shell
prompt.

_But_ the problem still remains that there is no graphical output yet.

After some code modifications i can now even compile the new IPC message
queue setup, but this still requires a lot of work to be done.

I would vote for dropping support for Windows 95/98 because the new
X11R6.4 port for windows with the cygnus tools will not work with Win9x.
The X11 programs are linked dynamically to the X11R6 libraries, so that
there is no chance to get this to work with the commercial X Servers
(e.g. MI/X), as they are based on X11R5. The usage of the X11 port for
the B20 version of the cygnus tools under the current V1.1 is not
supported.

From my initial testing i can say that there are waiting some nasty

surprises, so that i would not recommend the download of the GRASS
binaries for cygwin to people who are not of the adventurous nature. And
the missing graphical output (the CELL and HTMLMAP driver depend on the
missing fifos!) and the mangled bash setup makes it a pain to work with.
Just as a warning, so that no false expectations arise.

How can we get graphical output and tcltkgrass running under this setup?
I can still not say if i can get the X monitor to work and if tcltkgrass
will work under the X11 Window Setup. I have the initial impression that
the X11 Setup is not for real work (it is a beta!).

If someone has ideas how we can get a windows port with graphical
output, please tell!

cu,

Andreas

John Huddleston wrote:

Markus (Grass list)

I updated my cygwin to the latest, completely removed all grass
code from my drive, checked out grass5, and rebuilt grass5
with only one hitch. The src/cmd/head file still is not right.
More details later, I uploaded the binary tar.gz to the incoming
directory.

http://www.geog.uni-hannover.de/grass/grass5/binary/windows_cygnus/

I see the email about the w98. Clearly, the cygwin code has
disclaimers about using it under Windows 98. I used B20.1
of Cygwin when I used w98. All the grass5 compiled nicely
with it. The B20.1 uses the cygwin32 convention though, and
the config.guess must be adapted to ensure

For those who have NT or Win2000, the install of Cygwin is
more robust than ever, does not conflict with Windows, allows
a Unix environment for windows users. See the URL
http://sources.redhat.com/cygwin/ and download the setup.exe
Execute it from windows explorer or the CMD line, not
from bash. click Next-> first.

Next, it will prompt you to
o) download from the internet
o) install from internet
o) install from local

If you want the binaries (and sources) local, click the first
If you have limited space, click the second
If you have already downloaded from the internet, do the third

I download from the internet to my F: drive first
and then run setup a second time and install on
either my C: or D: drive. The default is the C:\cygwin
which makes the root "/" equal to C:\cygwin. I personally
do not like that since I cannot get at my C: files from /
so I override it with "C:\". It warns me but goes
on.

Finally, the best part is that all the tcl/tk, png,tiff,
and other items required to build grass5 are included
with one exception, the libcygipc.a archive.

So, I am attaching the head file for your use. Some
changes are yacc to bison -y, adding -lcygipc after
XDRLIB. Rename cygwin.txt to the head file as
head.i686-pc-cygwin

Let me know if you need more assistance,

John Huddleston

--
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'

17

Hi Andreas,

----- Original Message -----
From: "Andreas Lange" <Andreas.Lange@Rhein-Main.de>
To: <grass5@geog.uni-hannover.de>
Sent: Friday, November 24, 2000 10:32 AM
Subject: Re: [GRASS5] Win32 compile with cygnus ...

Hi John, Hi Markus, Hi Grasslist,

i finished a compile with the latest cygwin setup on NT 4.0 SP 5 in this
minute.
I can now compile all modules from the standard GRASS list file
(including r.in.png and r.out.png).
I'll check in my changes to the CVS in the next days. I'll check in my
head file too.

I have now a running X11R6.4 installation, but can not start grass5 in
the xterm. But i managed somehow to start xwin from the grass shell
prompt.

I have been using Starnet X-win http://www.starnet.com/ for some time
now. Using it with the X11R6.4 libes has allowed me to compile my X11
code. They have a trial version which runs for two hours. See the lycos
http://ftpsearch.lycos.com/ and search for xwin41.

_But_ the problem still remains that there is no graphical output yet.

After some code modifications i can now even compile the new IPC message
queue setup, but this still requires a lot of work to be done.

Do you want me to add the cygipc code to the grass5 cvs? Markus?

I would vote for dropping support for Windows 95/98 because the new
X11R6.4 port for windows with the cygnus tools will not work with Win9x.
The X11 programs are linked dynamically to the X11R6 libraries, so that
there is no chance to get this to work with the commercial X Servers
(e.g. MI/X), as they are based on X11R5. The usage of the X11 port for
the B20 version of the cygnus tools under the current V1.1 is not
supported.

Yes, I migrated to Win2000 for that reason; plus, both NT and 2000 have
better support for display. I have not tried windows ME with it, perhaps
that is one upgrade path for 98 users. I still would recommend Win2000.

>From my initial testing i can say that there are waiting some nasty
surprises, so that i would not recommend the download of the GRASS
binaries for cygwin to people who are not of the adventurous nature. And
the missing graphical output (the CELL and HTMLMAP driver depend on the
missing fifos!) and the mangled bash setup makes it a pain to work with.
Just as a warning, so that no false expectations arise.

How can we get graphical output and tcltkgrass running under this setup?
I can still not say if i can get the X monitor to work and if tcltkgrass
will work under the X11 Window Setup. I have the initial impression that
the X11 Setup is not for real work (it is a beta!).

This is one of those cases, where if we had money to travel, I would say
let's get together for two to three days and make it work.

John Huddleston

If someone has ideas how we can get a windows port with graphical
output, please tell!

cu,

Andreas

John Huddleston wrote:
>
> Markus (Grass list)
>
> I updated my cygwin to the latest, completely removed all grass
> code from my drive, checked out grass5, and rebuilt grass5
> with only one hitch. The src/cmd/head file still is not right.
> More details later, I uploaded the binary tar.gz to the incoming
> directory.
>
> http://www.geog.uni-hannover.de/grass/grass5/binary/windows_cygnus/
>
> I see the email about the w98. Clearly, the cygwin code has
> disclaimers about using it under Windows 98. I used B20.1
> of Cygwin when I used w98. All the grass5 compiled nicely
> with it. The B20.1 uses the cygwin32 convention though, and
> the config.guess must be adapted to ensure
>
> For those who have NT or Win2000, the install of Cygwin is
> more robust than ever, does not conflict with Windows, allows
> a Unix environment for windows users. See the URL
> http://sources.redhat.com/cygwin/ and download the setup.exe
> Execute it from windows explorer or the CMD line, not
> from bash. click Next-> first.
>
> Next, it will prompt you to
> o) download from the internet
> o) install from internet
> o) install from local
>
> If you want the binaries (and sources) local, click the first
> If you have limited space, click the second
> If you have already downloaded from the internet, do the third
>
> I download from the internet to my F: drive first
> and then run setup a second time and install on
> either my C: or D: drive. The default is the C:\cygwin
> which makes the root "/" equal to C:\cygwin. I personally
> do not like that since I cannot get at my C: files from /
> so I override it with "C:\". It warns me but goes
> on.
>
> Finally, the best part is that all the tcl/tk, png,tiff,
> and other items required to build grass5 are included
> with one exception, the libcygipc.a archive.
>
> So, I am attaching the head file for your use. Some
> changes are yacc to bison -y, adding -lcygipc after
> XDRLIB. Rename cygwin.txt to the head file as
> head.i686-pc-cygwin
>
> Let me know if you need more assistance,
>
> John Huddleston

--
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'

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

18

On Sat, Nov 25, 2000 at 07:10:41AM -0700, John Huddleston wrote:

Hi Andreas,
Sent: Friday, November 24, 2000 10:32 AM
> Hi John, Hi Markus, Hi Grasslist,
> i finished a compile with the latest cygwin setup on NT 4.0 SP 5 in this
> minute.
> I can now compile all modules from the standard GRASS list file
> (including r.in.png and r.out.png).
> I'll check in my changes to the CVS in the next days. I'll check in my
> head file too.
>
> I have now a running X11R6.4 installation, but can not start grass5 in
> the xterm. But i managed somehow to start xwin from the grass shell
> prompt.

I have been using Starnet X-win http://www.starnet.com/ for some time
now. Using it with the X11R6.4 libes has allowed me to compile my X11
code. They have a trial version which runs for two hours. See the lycos
http://ftpsearch.lycos.com/ and search for xwin41.

> _But_ the problem still remains that there is no graphical output yet.
>
> After some code modifications i can now even compile the new IPC message
> queue setup, but this still requires a lot of work to be done.

Do you want me to add the cygipc code to the grass5 cvs? Markus?

Hi John,

if this code is required and simplifies life to compile the GRASS on
Windows, please go ahead.

This is one of those cases, where if we had money to travel, I would say
let's get together for two to three days and make it work.

John Huddleston

I wish we would have money to sponsor such meetings!! Any ideas where
to apply for it? GRASS on Windows would be really a step forward
in GRASS reputation...

Markus

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

19

The translation of the cygwin filename,

  //f/source/cvsroot/grass/src/CMD/generic/gmake.sh

into windows-speak is,

  f:\source\cvsroot\grass\src\CMD\generic\gmake.sh

It is indeed a cygwinification of the windows environment.

Justin Hickey wrote:

Hello Mike

Mike Thomas wrote:
> There is a gmake5 script in /usr/local/bin:
> ---------------------------------------
> :
> SRC=//f/source/cvsroot/grass/src
> CMD=//f/source/cvsroot/grass/src/CMD
> HEADER=head.i586-pc-cygwin
> HASX=yes
> HASMotif=no
> MAKE=make
> . //f/source/cvsroot/grass/src/CMD/generic/gmake.sh
    ^^

I think I may have found the problem. It depends on your setup and
cygwin, but these two slashes on a windows machine may be interpreted
(such as in Tcl) as a network file where f would be the machine name. I
assume that f is not a machine name, thus, cygwin may be trying to find
the file on a machine named f instead of the directory f. Thus, you are
getting the error you mentioned in your previous mail (it has the same
//).

--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| 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'