Miha STAUT wrote:
> What was wrong in this installation on Windows XP with Cygwin on it?
> What does this mean:
> $ sh grass5_i686-pc-cygwin_install.sh
> grass5.0.0pre3_i686-pc-cygwin_bin.tar.gz
>
> GRASS GIS 5 binary package installation tool
>
> [: None: bad number
> Using gunzip decompressor...
The problem is most likely because the expression:
SIZE=`ls -l $PACKAGE_NAME | tr -s " " | cut -d" " -f5`
results in SIZE being set to "None". If so, the message will be
generated by the command:
if [ $SIZE -ne $TAR_FILE_SIZE ] ; then
as the value before "-ne" must be a number, but "None" isn't a valid
number.
As for exactly why the error occurs, I suspect that one of the Cygwin
tools (probably "ls") isn't generating output in the format which the
script is assuming.
Incidentally, pre3 is quite old; a lot has been fixed since then.
--
Glynn Clements <glynn.clements@virgin.net>
Thanks Glynn,
The binaries were downloaded days ago from http://grass.itc.it/grass5/binary/windows_cygnus/. OK I am not really an expert in cygwin installations. What you suggest to do? Reinstall the ls package (maybe a new version)?
Miha Staut
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
Miha STAUT wrote:
The binaries were downloaded days ago from
http://grass.itc.it/grass5/binary/windows_cygnus/. OK I am not really an
expert in cygwin installations. What you suggest to do? Reinstall the ls
package (maybe a new version)?
"ls" is part of the "fileutils" package; you could try upgrading that.
Alternatively, run:
ls -l grass5.0.0pre3_i686-pc-cygwin_bin.tar.gz
and note which field contains the size; then modify the line:
SIZE=`ls -l $PACKAGE_NAME | tr -s " " | cut -d" " -f5`
accordingly (change the number after "-f" to the number of the field
which contains the file's size).
--
Glynn Clements <glynn.clements@virgin.net>
Miha STAUT wrote:
>Glynn Clements <glynn.clements@virgin.net>
Thanks Glynn,
The binaries were downloaded days ago from
http://grass.itc.it/grass5/binary/windows_cygnus/. OK I am not really an
expert in cygwin installations. What you suggest to do? Reinstall the ls
package (maybe a new version)?
Miha Staut
Hi Miha, Hi Glynn,
there are two versions of the package on the server:
wingrass_generic (without X server, but IHMO not fully functional)
wingrass_xserver (requires X server, from cygwin or commercial X
server).
The xserver version is still pre3, because i got from different postings
the impression that there is no longer need for a X server version and
that the generic version will be functional very soon.
Perhaps some clarification is needed, as i think it is too much work to
support two versions.
Andreas
--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas Lange wrote:
there are two versions of the package on the server:
wingrass_generic (without X server, but IHMO not fully functional)
wingrass_xserver (requires X server, from cygwin or commercial X
server).
The xserver version is still pre3, because i got from different postings
the impression that there is no longer need for a X server version and
that the generic version will be functional very soon.
Perhaps some clarification is needed, as i think it is too much work to
support two versions.
Well, the only differences should be in XDRIVER and mon.start.
However, the wingrass_generic package (libW11 based XDRIVER) is more
likely to have bugs, as libW11 doesn't get as much testing as the
"vanilla" XDRIVER (e.g. RGB rasters don't work in 5.0.1 due to a bug
in libW11's implementation of XCreateImage())
Also, you still need an X server if you want to use tcltkgrass or
NVIZ.
Ideally we should provide a package which contains just the alternate
XDRIVER and mon.start programs, rather than two complete GRASS
distributions.
Ultimately, the libW11-based XDRIVER should be replaced with a
native[1] Win32 driver. This wouldn't be that much work (XDRIVER is
only around 2400 lines of code), and the end result should be more
reliable than libW11's Xlib-on-Win32 emulation.
[1] Native in the sense of using the Win32 GUI (drawing and event
handling) API. It would still need to use Cygwin, as Windows itself
doesn't support AF_UNIX sockets.
--
Glynn Clements <glynn.clements@virgin.net>