Hello everyone
Source code for the release candidate for GRASS 5.4.0 is now available for testing at ftp://ftp.qub.ac.uk/pub/users/paulk/grass/grass-5.4.0pre1.tar.bz2
Please try it with your usual compile options etc. and check that everything is working. Report problems to the mailing list.
If all minor bugs have been fixed after one week, next week we can release 5.4.0 final (stable).
Hello everyone
Source code for the release candidate for GRASS 5.4.0 is now available for
testing at ftp://ftp.qub.ac.uk/pub/users/paulk/grass/grass-5.4.0pre1.tar.bz2
Please try it with your usual compile options etc. and check that
everything is working. Report problems to the mailing list.
Hello everyone
Source code for the release candidate for GRASS 5.4.0 is now available for
testing at ftp://ftp.qub.ac.uk/pub/users/paulk/grass/grass-5.4.0pre1.tar.bz2
Please try it with your usual compile options etc. and check that
everything is working. Report problems to the mailing list.
I tried downloading and installing grass-5.4.0pre1 on a new Solaris 9 box.
I first installed the following packages from sunfreeware:
bison-1.875d-sol9-sparc-local.gz
flex-2.5.31-sol9-sparc-local.gz
freetype-2.1.7-sol9-sparc-local.gz
gcc-3.4.2-sol9-sparc-local.gz
libiconv-1.8-sol9-sparc-local.gz
libpng-1.2.7-sol9-sparc-local.gz
make-3.80-sol9-sparc-local.gz
mesa-6.0-sol9-sparc-local.gz
tcl-8.4.6-sol9-sparc-local.gz
tk-8.4.6-sol9-sparc-local.gz
zlib-1.2.1-sol9-sparc-local.gz
Then I tried to configure and got:
$ ./configure
checking host system type... sparc-sun-solaris2.9
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for full floating-point support... yes
checking for pwd... /usr/bin/pwd
checking for source directory... /data1/homes/neptune/grass-5.4.0pre1
checking for build directory... /data1/homes/neptune/grass-5.4.0pre1
checking for Build Mechanism to be used... Alternate
configure: error: *** Build directory should not be the same as source
directory for the alternate build mechanism. Create a separate build
directory and run again, e.g. mkdir ~/grass-build; cd ~/grass-build; /usr/
src/grass/configure ... (see mk/README)
Any idea why it has chosen the Alternate build mechanism?
> Any idea why it has chosen the Alternate build mechanism?
5.4 was changed to do this, as shared libraries should work on all
(most) platforms now.
from INSTALL:
The intent of the install method is to have the following sequence
of commands work to install GRASS on any platform.
./configure
make
make install
from error:
configure: error: *** Build directory should not be the same as source
directory for the alternate build mechanism. Create a separate build
directory and run again, e.g. mkdir ~/grass-build; cd ~/grass-build; /usr/
src/grass/configure ... (see mk/README)
Am I missing something, or is the build process a lot harder than it should
be?
(I'm looking at it as a pre-release for a stable version, not as a development
version, so I'm being fussier than normal)
The intent of the install method is to have the following sequence
of commands work to install GRASS on any platform.
./configure
make
make install
from error:
configure: error: *** Build directory should not be the same as
source directory for the alternate build mechanism. Create a separate
build directory and run again, e.g. mkdir ~/grass-build; cd
~/grass-build; /usr/ src/grass/configure ... (see mk/README)
I guess that should read:
mkdir build
cd build
../configure --with-this --without-that
make
make install
I tried downloading and installing grass-5.4.0pre1 on a new Solaris 9 box.
Then I tried to configure and got:
$ ./configure
checking for Build Mechanism to be used... Alternate
configure: error: *** Build directory should not be the same as source
directory for the alternate build mechanism. Create a separate build
directory and run again, e.g. mkdir ~/grass-build; cd ~/grass-build; /usr/
src/grass/configure ... (see mk/README)
Any idea why it has chosen the Alternate build mechanism?
That is the default now. You need to either:
a) use --enable-gmake to use the old gmake5 mechanism, or
b) create a separate build directory, i.e.
$ mkdir build
$ cd build
$ ../configure ...
Option b) has the advantage that you can keep multiple builds around;
however, the alternate build mechanism requires GNU make, or at least
something which is reasonably compatible (include, ifeq, $(subst...)).
I had a quick look in the html directory in the 5.4 source and it seems most of the new commands that have html pages are already listed, r.in.mat, r.out.mat, d.nviz are the ones I checked. r.series and r.grow2 don't have html pages so I'll leave them out of the index.