[GRASS-user] Any Gentoo/Funtoo grass-gis users?

GRASS GRASS user
1

Hi!

I recently had the luck to be able to obtain a new system. I am doing various
trials (speak OSes) on it to make the switch from K-Ubuntu to something that
will be more fun to work with.

I've tried Scientific Linux 6 which I find nice, clean, but I dislike the old
KDE (4.3). I can't live without KDE's Kontact goodies. Also, myself being a
specialist in messing up normal running systems, I managed to quickly mix up
some of the repositories that don't go well along ;-p. I didn't read the
"signs" I guess...

I am running currently on openSUSE 12.3 which offers a fantastic installation
experience and appears to me to be very stable, even with latest KDE 4.10.
Indeed, the experience was brought with the least of tweaking actions I needed
to do so far, among various Linux distros I have tried (K-Ubuntu, Slax, Fedora
once, Gentoo once, Debian some years ago). I think, anyhow, that zypper (the
cli package manager) isn't that good as apt-get (yes, apt-get has some
functionalities which make life easy when hunting dependencies for example --
me thinks at least).

The third on the row is Funtoo. I managed to install quickly the base
following the official tutorial, had to fight a bit to install Xorg (since I
didn't understand quite some stuff), wait hours for KDE to "emerge". Yet, it
feels it's worth the time spent! It seems that portage is quite an advanced
tool and offers everything and even more (?) apt-get has to offer. It'll take
some time I guess till I gain a good understanding of the advantages and how
to use'm properly. But it feels like once set-up, you never look back.

Herewith, I kindly ask you to share your experiences on-list. In particular,
are there Gentoo/Funtoo users out there who regularly build grass_trunk and
the rest? GRASS-Wiki looks "empty" in this direction.

Also, relates in a way, there is this
<http://wiki.osgeo.org/wiki/GIS_workstation_setup_tips&gt; page which deserves an
update since Technology advances rapidly into new areas.

Best, Nikos

2

Hi,

I’m a Gentoo user, and don’t remember something specific about GRASS installation …

You can either use the standard install with latest stable ebuild (6.4.2), or follow the standard compilation procedure (http://grasswiki.osgeo.org/wiki/Compile_and_Install#Generic_Compilation_and_installation_procedure)
On my system, I installed both the official grass gentoo ebuild + 6.4.3_rc3 and 7 from svn. I put them in /opt/grass-xx

I join a small script I wrote to get an automated update. You just need to install all dependencies, uncomment the first line for the first launch + to make a new ‘/opt/grass7’ directory … it’s basically just a collection of commands for the standard compilation procedure and is not system dependant …

cheers,

Sylvain

(attachments)

build_7.sh (921 Bytes)

···

2013/7/6 Nikos Alexandris <nik@nikosalexandris.net>

Hi!

I recently had the luck to be able to obtain a new system. I am doing various
trials (speak OSes) on it to make the switch from K-Ubuntu to something that
will be more fun to work with.

I’ve tried Scientific Linux 6 which I find nice, clean, but I dislike the old
KDE (4.3). I can’t live without KDE’s Kontact goodies. Also, myself being a
specialist in messing up normal running systems, I managed to quickly mix up
some of the repositories that don’t go well along ;-p. I didn’t read the
“signs” I guess…

I am running currently on openSUSE 12.3 which offers a fantastic installation
experience and appears to me to be very stable, even with latest KDE 4.10.
Indeed, the experience was brought with the least of tweaking actions I needed
to do so far, among various Linux distros I have tried (K-Ubuntu, Slax, Fedora
once, Gentoo once, Debian some years ago). I think, anyhow, that zypper (the
cli package manager) isn’t that good as apt-get (yes, apt-get has some
functionalities which make life easy when hunting dependencies for example –
me thinks at least).

The third on the row is Funtoo. I managed to install quickly the base
following the official tutorial, had to fight a bit to install Xorg (since I
didn’t understand quite some stuff), wait hours for KDE to “emerge”. Yet, it
feels it’s worth the time spent! It seems that portage is quite an advanced
tool and offers everything and even more (?) apt-get has to offer. It’ll take
some time I guess till I gain a good understanding of the advantages and how
to use’m properly. But it feels like once set-up, you never look back.

Herewith, I kindly ask you to share your experiences on-list. In particular,
are there Gentoo/Funtoo users out there who regularly build grass_trunk and
the rest? GRASS-Wiki looks “empty” in this direction.

Also, relates in a way, there is this
<http://wiki.osgeo.org/wiki/GIS_workstation_setup_tips> page which deserves an
update since Technology advances rapidly into new areas.

Best, Nikos

grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

3

Sylvain Maillard wrote:

Hi,

Hi Sylvain,

I'm a Gentoo user, and don't remember something specific about GRASS
installation ...

Nice :-). I do fail however to emerge grass :-(. But, anyway, it is 6.4.2 so
I don't really need it. Maybe check the logs another day to see what's
mising.

If you have more Gentoo-tips (reg. OSGeo stuff) and the time to share, please,
do so :smiley:

You can either use the standard install with latest stable ebuild (6.4.2),
or follow the standard compilation procedure
(http://grasswiki.osgeo.org/wiki/Compile_and_Install#Generic_Compilation_an
d_installation_procedure)

Yes, everything works fine after I mounted the partition I am workin on
sans "noexec". It was either the "auto" or the "user" option in fstab. Don't
know which & why does hurt here.

On my system, I installed both the official grass
gentoo ebuild + 6.4.3_rc3 and 7 from svn. I put them in /opt/grass-xx

As others do, I don't isntall too, I do run from inside the "bin." directory.

I join a small script I wrote to get an automated update. You just need to
install all dependencies, uncomment the first line for the first launch +
to make a new '/opt/grass7' directory

Something minor: I think the --enable-64it doesn't hurt but isn't required in
grass7_trunk.

In addition, there is no --with-python option in grass7_trunk: "./configure --
help | grep py" returns nothing.

It does exist in grass6:

/osgeo/src/grass64_release $ ./configure --help | grep py

  --with-python[=path/python-config]
                          (python-config with path, e.g.
                          '--with-python=/usr/bin/python2.5-config'

I bombed in this error while trying to configure grass7_trunk. I had to
"eselect python list" and then set to python 2.7 by executing "sudo eselect
python set 1".

... it's basically just a collection
of commands for the standard compilation procedure and is not system
dependant ...

I have a very similar script (with info stolen from the ML), copy-pasted below
just for the records. Maybe I should direct some info in the wiki -- it would
certainly help me, for example, if I have seen some info in the wiki.

Thank you, Nikos
---

# clean
time make distclean

# update
time svn up

# taken from <http://lists.osgeo.org/pipermail/grass-user/2013-May/068229.html&gt;
renice +17 -p $$

# configure
CFLAGS="-ggdb -march=native -Wall -Werror-implicit-function-declaration" \
./configure \
--with-cxx \
--with-proj \
--with-geos \
--with-motif \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-wxwidgets \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-odbc=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" --with-mysql-
libs=/usr/lib/mysql \
--with-sqlite=yes \
--with-postgres=yes --with-postgresql=yes --with-postgres-
includes="/usr/lib64/postgresql" \
--with-opencl --with-openmp --with-pthread \
--with-readline \
--with-nls \
--enable-largefile=yes \
--with-netcdf \
2>&1 | tee config_log.txt

# make
time make -j13

4

Sylvain Maillard wrote:
..

> I join a small script I wrote to get an automated update. You just need to
> install all dependencies, uncomment the first line for the first launch +
> to make a new '/opt/grass7' directory

As well,

--with-tcltk \

does not exist in/for grass7_trunk.

I will try to merge yours and mine script, will post here.

Thanks, N

5

On Sunday 07 of July 2013 15:10:25 Nikos Alexandris wrote:

Sylvain Maillard wrote:
..

> > I join a small script I wrote to get an automated update. You just need
> > to
> > install all dependencies, uncomment the first line for the first launch
> > +
> > to make a new '/opt/grass7' directory

As well,

--with-tcltk \

does not exist in/for grass7_trunk.

I will try to merge yours and mine script, will post here.

So, I merged some of your isntructions and modified a the configuration as
follows (just for completeness, let's say, althoug many stuff get auto-detected
and there is no need to specify them):

CFLAGS="-ggdb -march=native -Wall -Werror-implicit-function-declaration" \
./configure \
--with-cxx \
--with-includes=/usr/include/ --with-libs=/usr/lib64/ \
--with-proj \
--with-proj-includes=/usr/include/ \
--with-proj-libs=/usr/lib64/ \
--with-proj-share=/usr/share/proj/ \
--with-geos \
--with-geos=/usr/bin/geos-config \
--with-gdal=/usr/bin/gdal-config \
--with-x \
--with-motif \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--without-ffmpeg \
--with-python=yes --with-python=/usr/bin/python2.7-config \
--with-wxwidgets \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-odbc=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" --with-mysql-
libs=/usr/lib/mysql \
--with-sqlite=yes \
--with-postgres=yes --with-postgresql=yes --with-postgres-
includes="/usr/include/postgresql" \
--with-opencl --with-openmp --with-pthread \
--with-lapack \
--with-fftw \
--with-readline \
--with-regex \
--with-nls \
--enable-largefile=yes \
--with-jpeg \
--with-tiff \
--with-png \
--with-netcdf \
--without-opendwg \
2>&1 | tee config_log.txt

Best regards, Nikos

6

[all deleted]

Just for the records, in Funtoo, the absolute minimum "requirement", let's
say, to configure grass7, is to point where "freetypes" are located. It then
works...

# configure
./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

[..]

GRASS is now configured for: x86_64-unknown-linux-gnu

  Source directory: /osgeo/src/grass7_trunk
  Build directory: /osgeo/src/grass7_trunk
  Installation directory: ${prefix}/grass-7.0.svn
  Startup script in directory:${exec_prefix}/bin
  C compiler: gcc -g -O2
  C++ compiler: c++ -g -O2
  Building shared libraries: yes
  OpenGL platform: X11

  MacOSX application: no
  MacOSX architectures:
  MacOSX SDK:

  BLAS support: no
  C++ support: yes
  Cairo support: yes
  DWG support: no
  FFMPEG support: no
  FFTW support: yes
  FreeType support: yes
  GDAL support: yes
  GEOS support: no
  LAPACK support: no
  Large File support (LFS): yes
  libLAS support: no
  MySQL support: no
  NetCDF support: no
  NLS support: no
  ODBC support: no
  OGR support: yes
  OpenCL support: no
  OpenGL support: yes
  OpenMP support: no
  PNG support: yes
  POSIX thread support: no
  PostgreSQL support: no
  Readline support: no
  Regex support: yes
  SQLite support: no
  TIFF support: yes
  wxWidgets support: no
  X11 support: yes

Nikos

7

On Sunday 07 of July 2013 12:08:43 Sylvain Maillard wrote:
..

I join a small script I wrote to get an automated update. You just need to
install all dependencies, uncomment the first line for the first launch +
to make a new '/opt/grass7' directory ... it's basically just a collection
of commands for the standard compilation procedure and is not system
dependant ...

Hi Sylvain!

Returning on this: if you install grass after compilation (as it is
instructed in the script you attached), how do you remove later grass? Is it
safe to do so? In Ubuntu it always took to search manually and remove all the
relevant bits.

I am hesitant to install and have a future plan to study ebuilds to do it the
right way. In case you have a nice working solution, would you mind sharing
it as well?

Thanks a lot, Nikos