Package Details: grass 7.8.4-1

Git Clone URL: (read-only, click to copy)
Package Base: grass
Description: Geospatial data management and analysis, image processing, graphics/maps production, spatial modeling and visualization
Upstream URL:
Licenses: GPL
Submitter: Scimmia
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 34
Popularity: 0.018629
First Submitted: 2015-09-06 15:10
Last Updated: 2020-10-14 14:35

Dependencies (27)

Required by (3)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

kokkytos commented on 2016-12-06 15:11

I'm using community/gdal 2.1.1-3

Scimmia commented on 2016-11-23 01:46

@kokkytos, are you using the gdal package from the Extra repo?

kokkytos commented on 2016-11-20 20:47

I get the following error:

checking whether to use GDAL... yes
checking for gdal-config... /usr/bin/gdal-config
configure: error: *** Unable to locate GDAL library.
==> ERROR: A failure occurred in build().

Scimmia commented on 2016-08-17 13:21

@scummos, no. Read the AUR wiki page.

scummos commented on 2016-08-17 09:17

This needs to additionally depend on
or the build will fail.

kikislater commented on 2016-06-04 09:08

Another PKGBUILD here (from official grass gis website) :

Better options according to common GIS usage with Grass

SmokeyD commented on 2016-05-20 01:48

I had the build problems as well like all previous commenters with GCC6. I also tried using GCC5 and GCC4.something from AUR, but it didn't want to build. Today I just tried installing again form AUR without any modifications and it just built and installed fine without trouble. I assume @Scimmia did something in the PKGBUILD to make it compile correctly with GCC6. If so, it worked like a charm for me. Thanks a lot!

Scimmia commented on 2016-05-16 00:43

Got it. GCC6 defaults to C++14 now, and GRASS can't handle that. Forcing it back to C++98 lets everything build fine again. I didn't bump the pkgrel, as there's no need to rebuilt it if you already successfully built it earlier.

Having different compilers in core and testing set us back a bit on this. Thanks for your patience.

Scimmia commented on 2016-05-16 00:28

Alright, I can reproduce it now. I think these are GCC6 issues.

beej commented on 2016-05-15 23:00

Detail on the iostream build error. Looks like it might be an upstream issue.