[GRASS5] Re: installation/compiling instruction for GRASS on cygwin

[John Huddleston]

Andreas, (Cc to Grass5 list)

Markus and I received an email from someone who could not make
the Cygwin build of grass5 work.  I asked for their configuration via

cygcheck -s -v -r

It turned out there were two issues.  One is what Andreas writes
about below, the Win95/98 operation.  I moved off the Win98
because the Cygwin people do not support it.  While I prefer
Win2000 over WinNT, they both work well.  So, yes, I support
the Win32 of Grass5 for NT/2000

The other issue is more obscure.   If you take the default location
for the cygwin install of C:\Cygwin then the default mount for root
is that same directory.  All files under "/" are "seen" as under
C:\Cygwin.   You can still access files under C: using //c
However, the /usr/local/grass5 must be installed under the "root"
as known by the system.   In all cases, a "cd /" will work.  Some
users may not put it there though if using WinZIP and not
familiar with the Cygwin operation.  Unmounting and remounting
root is an easy process within Cygwin for users with some
rudimentary Unix knowledge, which does not always come with
Windows experience.

To start Grass, set the PATH and DISPLAY variables, start the
ipc-daemon, and start the xterm.  My lines are:

PATH=/usr/local/grass5/bin:/usr/local/bin:/usr/X11R6/bin:$PATH
export PATH
DISPLAY=127.0.0.1:0.0
export DISPLAY

ps | grep ipc
if [ $? = 1 ] ; then
        /usr/local/bin/ipc-daemon &
fi

xterm -sl 1000 -sb -ms red -fg yellow -bg black -font 10x20 -e bash &

Next run grass from within the xterm window.

As to the B20 version...those were built for Win95/98.  Initial builds of
Grass5 under Cygwin were done using this system.  I agree with
removing the binaries because we do not support it.

John Huddleston


----- Original Message -----
From: "Andreas Lange" <Andreas.Lange at Rhein-Main.de>
To: <neteler at geog.uni-hannover.de>; <jhickey at hpcc.nectec.or.th>;
<jhudd at lamar.colostate.edu>; <mblue at nb.sympatico.ca>; <mthomas at gil.com.au>;
<Howard.L.Tan at jpl.nasa.gov>
Sent: Friday, March 23, 2001 5:20 AM
Subject: installation/compiling instruction for GRASS on cygwin


> Hi,
>
> i'll try to write a new cygwin compiling and installation instruction in
> the next days. The files on the server need updating, much of the
> information is not up to date.
>
> I'd ask John to send me the StartGrass.bat file, as i have it not
> available.
>
> I'll write one instruction on compiling and another on installing the
> binary distribution. (and a README.html for the ftp server).
>
> I have a machine around without an cygwin installation so i can test all
> prerequisites. I plan to check the new html files directly into the CVS,
> so Markus can copy them over to the web server without my intervention.
> Please check the files in CVS or send me a mail if i should send it to
> you by mail for corrections.
>
> The grass5install.sh does not work on cygwin (which missing), but i
> managed to create a rpm-package on cygwin that installs and runs.
> This would add another prerequisite (red hat package manager rpm), but
> would make installation much simpler. Do you like this idea? The rpm
> file is 30 MB big.
>
> I managed to write a gunzip check without which, but the script dies
> with errors creating the fifos (mkfifo missing), which is completely
> unneccessary, as the fifos are no longer used.
>
> Could someone implement that the mkfifo call is ommitted with the
> --with-sockets option to configure, so we can use the grass5install.sh
> script for binary installation? One possibility would be to use one
> script for fifo/socket/ipc initialization or copy the appropriate script
> to one name by the configure script.
>
> I would propose to only support Windows NT 4.0 and Windows 2000.
> Any objections?
> The grass port will definitely not work on Windows 95 (as the X Server
> does not work there). Same with Windows 98. I have no knowledge of
> Windows ME, so if someone knows, please tell me.
> I expect also problems with FAT file systems (those problems with the
> upper/lower case things described lately on grasslist could be from
> this). There may be additional quirks with the windows POSIX environment
> enabled/disabled.
>
> Of course we have to solve the problems with the interactive versions of
> the programs (currently crashing with signal 11). I found that only the
> interactive version crashes, if i give all parameters on command line it
> works fine. Some string/pointer problem?
>
> The old cygwin B20 stuff on the baylor server should be removed. There
> is no need to keep this outdated tools around, it is confusing and i
> think the space could be used better for other things.
>
> Please assist me with the above questions.
>
> cu,
>
> Andreas
>
> --
> Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
> Andreas.Lange at Rhein-Main.de - A.C.Lange at GMX.net


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