Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
On Mon, Feb 26, 2018 at 4:51 PM, Pierre Roudier wrote: > > * I ran make MODULE_TOPDIR=/usr/local/src/grass7_trunk/ in the geoPAT > directory > > Unfortunately still the same issue running it in grass75: > > GRASS 7.5.svn (modis_lst_2015):/usr/local/src/grass7_trunk > p.sig.grid > --help > ERROR: Module built against version $Revision: 70617 $ but trying to use >version $Revision: 72230 $. You need to rebuild GRASS GIS or >untangle multiple installations. > > Any idea what I might have missed? > Sorry, I suspected that will be the case, perhaps I was not clear enough about that. I think you need to 1) look at the compilation output from make specifically the compiler commands which are executed and the libraries linked there, 2) do `make MODULE_TOPDIR=/usr/local/src/grass7_trunk/ clean` and delete all p.si* files in /usr/local/... including the library (.so and .so.*) before you run the actual make, and 3) probably run `make MODULE_TOPDIR=/usr/local/src/grass7_trunk/ install` with `sudo` as well since you have the code in the system (but I don't do this, so I don't have procedure in my head). ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Dear Vaclav, Here's what I ended up doing: * I updated my GRASS trunk and compiled (./configure, make, then make install) * I applied your patch to geoPAT * I ran make MODULE_TOPDIR=/usr/local/src/grass7_trunk/ in the geoPAT directory Unfortunately still the same issue running it in grass75: GRASS 7.5.svn (modis_lst_2015):/usr/local/src/grass7_trunk > p.sig.grid --help ERROR: Module built against version $Revision: 70617 $ but trying to use version $Revision: 72230 $. You need to rebuild GRASS GIS or untangle multiple installations. Any idea what I might have missed? Cheers, Pierre On 26 February 2018 at 16:53, Vaclav Petras wrote: > > > On Sun, Feb 25, 2018 at 10:41 PM, Pierre Roudier > wrote: > >> Hi Vaclav, and thank you so much for your help, >> > > You are welcome. > > >> >> Do I understand correctly that I should compile a version of GRASS to use >> your patch? >> > > The patch is for geoPAT, but I tested the subsequent compilation of geoPAT > only against compiled GRASS (which is not `make install`ed). > > >> >> Cheers, >> >> P >> >> On 25 February 2018 at 15:52, Vaclav Petras wrote: >> >>> Dear all, >>> >>> this may not address this specific problem with multiple installations, >>> but it may help overall with debugging such problems because it is more >>> direct. I'm attaching a geoPAT patch which deals with the names of the >>> libraries and removes the need to modify GRASS source code before the >>> compilation happens. >>> >>> The following command executed in the directory with the source code >>> should be sufficient to compile modules with a self-compiled GRASS which is >>> not in system: >>> >>> make MODULE_TOPDIR=~/.../trunk/ GRASS_VERSION_NUMBER=7.5.svn >>> >>> Path to the GRASS GIS installation/code/dev files and the version needs >>> to be provided. This was tested with the current trunk in a home directory >>> and not with GRASS installed (`make install`-ed) in the system. >>> Nevertheless this removes the need to modify the source code and thus >>> increasing compatibility with different GRASS versions (which change the >>> copied and modified file). >>> >>> Besides the limited testing, there are three other issues: >>> >>> 1) g.extension is not able to install the code from a directory (or ZIP, >>> ...) because no system for C addon modules with libraries is in place (same >>> issue as with r.pi.* suite). When GRASS_VERSION_NUMBER is added to >>> g.extension code and HTML for the main directory is resolved/or ignored in >>> g.extension, modules at least compile, but nothing is installed (added) to >>> the local addons directory. >>> >>> 2) I don't understand why GRASS_VERSION_NUMBER isn't already defined. >>> >>> 3) I don't know how to contribute to the geoPAT repository. >>> >>> Best, >>> Vaclav >>> >>> >>> >>> On Fri, Feb 23, 2018 at 6:22 PM, Dylan Beaudette < >>> dylan.beaude...@gmail.com> wrote: >>> How about your GRASS "development" files: installed via package manager? Same version as the binaries? D On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier wrote: > Thanks Dylan, > > I did install using `sudo sh install.sh grass72` -- then `sudo sh install.sh > grass74` after my Grass version got updated to 7.4 > > Cheers, > > P > > On 23 February 2018 at 18:41, Dylan Beaudette < dylan.beaude...@gmail.com> > wrote: >> >> Howdy Pierre! >> >> In my experience, the GeoPat modules need to know where several things >> are located, including (I think) parts of the GRASS source code. Have >> a look through the install.sh code: >> >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh >> >> I was able to get these modules up and running by invoking install.sh like >> this: >> >> sh install.sh grass75 >> >> ... where "grass75" is the binary compiled from grass_trunk. The >> install.sh code seemed to find the source code it needed and worked >> without issue. >> >> How did you install / upgrade the Geopat modules? Could it be that >> install.sh is "finding" the old source code / headers? Is there a >> package for both GRASS binaries and development files? >> >> Dylan >> >> >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier >> wrote: >> > Hi, >> > >> > I've been compiling the geoPAT extensions for GRASS from >> > http://sil.uc.edu/gitlist/geoPAT/ >> > >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS >> > repository, but since this repo updated to GRASS 7.4, I have the >> > following >> > issue: >> > >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help >> > ERROR: Module built against version $Revision: 70617 $ but trying to use >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or >> >untangle mu
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
On Sun, Feb 25, 2018 at 10:41 PM, Pierre Roudier wrote: > Hi Vaclav, and thank you so much for your help, > You are welcome. > > Do I understand correctly that I should compile a version of GRASS to use > your patch? > The patch is for geoPAT, but I tested the subsequent compilation of geoPAT only against compiled GRASS (which is not `make install`ed). > > Cheers, > > P > > On 25 February 2018 at 15:52, Vaclav Petras wrote: > >> Dear all, >> >> this may not address this specific problem with multiple installations, >> but it may help overall with debugging such problems because it is more >> direct. I'm attaching a geoPAT patch which deals with the names of the >> libraries and removes the need to modify GRASS source code before the >> compilation happens. >> >> The following command executed in the directory with the source code >> should be sufficient to compile modules with a self-compiled GRASS which is >> not in system: >> >> make MODULE_TOPDIR=~/.../trunk/ GRASS_VERSION_NUMBER=7.5.svn >> >> Path to the GRASS GIS installation/code/dev files and the version needs >> to be provided. This was tested with the current trunk in a home directory >> and not with GRASS installed (`make install`-ed) in the system. >> Nevertheless this removes the need to modify the source code and thus >> increasing compatibility with different GRASS versions (which change the >> copied and modified file). >> >> Besides the limited testing, there are three other issues: >> >> 1) g.extension is not able to install the code from a directory (or ZIP, >> ...) because no system for C addon modules with libraries is in place (same >> issue as with r.pi.* suite). When GRASS_VERSION_NUMBER is added to >> g.extension code and HTML for the main directory is resolved/or ignored in >> g.extension, modules at least compile, but nothing is installed (added) to >> the local addons directory. >> >> 2) I don't understand why GRASS_VERSION_NUMBER isn't already defined. >> >> 3) I don't know how to contribute to the geoPAT repository. >> >> Best, >> Vaclav >> >> >> >> On Fri, Feb 23, 2018 at 6:22 PM, Dylan Beaudette < >> dylan.beaude...@gmail.com> wrote: >> >>> How about your GRASS "development" files: installed via package >>> manager? Same version as the binaries? >>> >>> D >>> >>> On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier >>> wrote: >>> > Thanks Dylan, >>> > >>> > I did install using `sudo sh install.sh grass72` -- then `sudo sh >>> install.sh >>> > grass74` after my Grass version got updated to 7.4 >>> > >>> > Cheers, >>> > >>> > P >>> > >>> > On 23 February 2018 at 18:41, Dylan Beaudette < >>> dylan.beaude...@gmail.com> >>> > wrote: >>> >> >>> >> Howdy Pierre! >>> >> >>> >> In my experience, the GeoPat modules need to know where several things >>> >> are located, including (I think) parts of the GRASS source code. Have >>> >> a look through the install.sh code: >>> >> >>> >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh >>> >> >>> >> I was able to get these modules up and running by invoking install.sh >>> like >>> >> this: >>> >> >>> >> sh install.sh grass75 >>> >> >>> >> ... where "grass75" is the binary compiled from grass_trunk. The >>> >> install.sh code seemed to find the source code it needed and worked >>> >> without issue. >>> >> >>> >> How did you install / upgrade the Geopat modules? Could it be that >>> >> install.sh is "finding" the old source code / headers? Is there a >>> >> package for both GRASS binaries and development files? >>> >> >>> >> Dylan >>> >> >>> >> >>> >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > I've been compiling the geoPAT extensions for GRASS from >>> >> > http://sil.uc.edu/gitlist/geoPAT/ >>> >> > >>> >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS >>> >> > repository, but since this repo updated to GRASS 7.4, I have the >>> >> > following >>> >> > issue: >>> >> > >>> >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help >>> >> > ERROR: Module built against version $Revision: 70617 $ but trying >>> to use >>> >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or >>> >> >untangle multiple installations. >>> >> > [Raster MASK present] >>> >> > >>> >> > Any pointers about how to resolve the version tangling? I've tried >>> >> > recompiling geoPAT, but that didn't work. >>> >> > >>> >> > Cheers, >>> >> > >>> >> > Pierre >>> >> > >>> >> > ___ >>> >> > grass-dev mailing list >>> >> > grass-dev@lists.osgeo.org >>> >> > https://lists.osgeo.org/mailman/listinfo/grass-dev >>> > >>> > >>> ___ >>> grass-dev mailing list >>> grass-dev@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/grass-dev >>> >> >> > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Hi Vaclav, and thank you so much for your help, Do I understand correctly that I should compile a version of GRASS to use your patch? Cheers, P On 25 February 2018 at 15:52, Vaclav Petras wrote: > Dear all, > > this may not address this specific problem with multiple installations, > but it may help overall with debugging such problems because it is more > direct. I'm attaching a geoPAT patch which deals with the names of the > libraries and removes the need to modify GRASS source code before the > compilation happens. > > The following command executed in the directory with the source code > should be sufficient to compile modules with a self-compiled GRASS which is > not in system: > > make MODULE_TOPDIR=~/.../trunk/ GRASS_VERSION_NUMBER=7.5.svn > > Path to the GRASS GIS installation/code/dev files and the version needs to > be provided. This was tested with the current trunk in a home directory and > not with GRASS installed (`make install`-ed) in the system. Nevertheless > this removes the need to modify the source code and thus increasing > compatibility with different GRASS versions (which change the copied and > modified file). > > Besides the limited testing, there are three other issues: > > 1) g.extension is not able to install the code from a directory (or ZIP, > ...) because no system for C addon modules with libraries is in place (same > issue as with r.pi.* suite). When GRASS_VERSION_NUMBER is added to > g.extension code and HTML for the main directory is resolved/or ignored in > g.extension, modules at least compile, but nothing is installed (added) to > the local addons directory. > > 2) I don't understand why GRASS_VERSION_NUMBER isn't already defined. > > 3) I don't know how to contribute to the geoPAT repository. > > Best, > Vaclav > > > > On Fri, Feb 23, 2018 at 6:22 PM, Dylan Beaudette < > dylan.beaude...@gmail.com> wrote: > >> How about your GRASS "development" files: installed via package >> manager? Same version as the binaries? >> >> D >> >> On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier >> wrote: >> > Thanks Dylan, >> > >> > I did install using `sudo sh install.sh grass72` -- then `sudo sh >> install.sh >> > grass74` after my Grass version got updated to 7.4 >> > >> > Cheers, >> > >> > P >> > >> > On 23 February 2018 at 18:41, Dylan Beaudette < >> dylan.beaude...@gmail.com> >> > wrote: >> >> >> >> Howdy Pierre! >> >> >> >> In my experience, the GeoPat modules need to know where several things >> >> are located, including (I think) parts of the GRASS source code. Have >> >> a look through the install.sh code: >> >> >> >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh >> >> >> >> I was able to get these modules up and running by invoking install.sh >> like >> >> this: >> >> >> >> sh install.sh grass75 >> >> >> >> ... where "grass75" is the binary compiled from grass_trunk. The >> >> install.sh code seemed to find the source code it needed and worked >> >> without issue. >> >> >> >> How did you install / upgrade the Geopat modules? Could it be that >> >> install.sh is "finding" the old source code / headers? Is there a >> >> package for both GRASS binaries and development files? >> >> >> >> Dylan >> >> >> >> >> >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier >> >> wrote: >> >> > Hi, >> >> > >> >> > I've been compiling the geoPAT extensions for GRASS from >> >> > http://sil.uc.edu/gitlist/geoPAT/ >> >> > >> >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS >> >> > repository, but since this repo updated to GRASS 7.4, I have the >> >> > following >> >> > issue: >> >> > >> >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help >> >> > ERROR: Module built against version $Revision: 70617 $ but trying to >> use >> >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or >> >> >untangle multiple installations. >> >> > [Raster MASK present] >> >> > >> >> > Any pointers about how to resolve the version tangling? I've tried >> >> > recompiling geoPAT, but that didn't work. >> >> > >> >> > Cheers, >> >> > >> >> > Pierre >> >> > >> >> > ___ >> >> > grass-dev mailing list >> >> > grass-dev@lists.osgeo.org >> >> > https://lists.osgeo.org/mailman/listinfo/grass-dev >> > >> > >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-dev >> > > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Hey Dylan, Yes, these were installed using the grass-dev package in the UnbuntuGIS repo, Cheers, P On 24 February 2018 at 12:22, Dylan Beaudette wrote: > How about your GRASS "development" files: installed via package > manager? Same version as the binaries? > > D > > On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier > wrote: > > Thanks Dylan, > > > > I did install using `sudo sh install.sh grass72` -- then `sudo sh > install.sh > > grass74` after my Grass version got updated to 7.4 > > > > Cheers, > > > > P > > > > On 23 February 2018 at 18:41, Dylan Beaudette > > > wrote: > >> > >> Howdy Pierre! > >> > >> In my experience, the GeoPat modules need to know where several things > >> are located, including (I think) parts of the GRASS source code. Have > >> a look through the install.sh code: > >> > >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh > >> > >> I was able to get these modules up and running by invoking install.sh > like > >> this: > >> > >> sh install.sh grass75 > >> > >> ... where "grass75" is the binary compiled from grass_trunk. The > >> install.sh code seemed to find the source code it needed and worked > >> without issue. > >> > >> How did you install / upgrade the Geopat modules? Could it be that > >> install.sh is "finding" the old source code / headers? Is there a > >> package for both GRASS binaries and development files? > >> > >> Dylan > >> > >> > >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier > >> wrote: > >> > Hi, > >> > > >> > I've been compiling the geoPAT extensions for GRASS from > >> > http://sil.uc.edu/gitlist/geoPAT/ > >> > > >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS > >> > repository, but since this repo updated to GRASS 7.4, I have the > >> > following > >> > issue: > >> > > >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help > >> > ERROR: Module built against version $Revision: 70617 $ but trying to > use > >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or > >> >untangle multiple installations. > >> > [Raster MASK present] > >> > > >> > Any pointers about how to resolve the version tangling? I've tried > >> > recompiling geoPAT, but that didn't work. > >> > > >> > Cheers, > >> > > >> > Pierre > >> > > >> > ___ > >> > grass-dev mailing list > >> > grass-dev@lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/grass-dev > > > > > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Dear all, this may not address this specific problem with multiple installations, but it may help overall with debugging such problems because it is more direct. I'm attaching a geoPAT patch which deals with the names of the libraries and removes the need to modify GRASS source code before the compilation happens. The following command executed in the directory with the source code should be sufficient to compile modules with a self-compiled GRASS which is not in system: make MODULE_TOPDIR=~/.../trunk/ GRASS_VERSION_NUMBER=7.5.svn Path to the GRASS GIS installation/code/dev files and the version needs to be provided. This was tested with the current trunk in a home directory and not with GRASS installed (`make install`-ed) in the system. Nevertheless this removes the need to modify the source code and thus increasing compatibility with different GRASS versions (which change the copied and modified file). Besides the limited testing, there are three other issues: 1) g.extension is not able to install the code from a directory (or ZIP, ...) because no system for C addon modules with libraries is in place (same issue as with r.pi.* suite). When GRASS_VERSION_NUMBER is added to g.extension code and HTML for the main directory is resolved/or ignored in g.extension, modules at least compile, but nothing is installed (added) to the local addons directory. 2) I don't understand why GRASS_VERSION_NUMBER isn't already defined. 3) I don't know how to contribute to the geoPAT repository. Best, Vaclav On Fri, Feb 23, 2018 at 6:22 PM, Dylan Beaudette wrote: > How about your GRASS "development" files: installed via package > manager? Same version as the binaries? > > D > > On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier > wrote: > > Thanks Dylan, > > > > I did install using `sudo sh install.sh grass72` -- then `sudo sh > install.sh > > grass74` after my Grass version got updated to 7.4 > > > > Cheers, > > > > P > > > > On 23 February 2018 at 18:41, Dylan Beaudette > > > wrote: > >> > >> Howdy Pierre! > >> > >> In my experience, the GeoPat modules need to know where several things > >> are located, including (I think) parts of the GRASS source code. Have > >> a look through the install.sh code: > >> > >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh > >> > >> I was able to get these modules up and running by invoking install.sh > like > >> this: > >> > >> sh install.sh grass75 > >> > >> ... where "grass75" is the binary compiled from grass_trunk. The > >> install.sh code seemed to find the source code it needed and worked > >> without issue. > >> > >> How did you install / upgrade the Geopat modules? Could it be that > >> install.sh is "finding" the old source code / headers? Is there a > >> package for both GRASS binaries and development files? > >> > >> Dylan > >> > >> > >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier > >> wrote: > >> > Hi, > >> > > >> > I've been compiling the geoPAT extensions for GRASS from > >> > http://sil.uc.edu/gitlist/geoPAT/ > >> > > >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS > >> > repository, but since this repo updated to GRASS 7.4, I have the > >> > following > >> > issue: > >> > > >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help > >> > ERROR: Module built against version $Revision: 70617 $ but trying to > use > >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or > >> >untangle multiple installations. > >> > [Raster MASK present] > >> > > >> > Any pointers about how to resolve the version tangling? I've tried > >> > recompiling geoPAT, but that didn't work. > >> > > >> > Cheers, > >> > > >> > Pierre > >> > > >> > ___ > >> > grass-dev mailing list > >> > grass-dev@lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/grass-dev > > > > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > diff -urN geoPAT-3a75addf/p.sig.grid/Makefile geoPAT/p.sig.grid/Makefile --- geoPAT-3a75addf/p.sig.grid/Makefile 2016-03-05 01:15:31.0 -0500 +++ geoPAT/p.sig.grid/Makefile 2018-02-24 20:16:32.576234715 -0500 @@ -2,6 +2,8 @@ PGM=p.sig.grid +include ../similarlib/Similar.make + LIBES = $(SIMILARLIB) $(GPROJLIB) $(RASTERLIB) $(GISLIB) $(MATHLIB) DEPENDENCIES = $(SIMILARDEP) $(GPROJDEP) $(RASTERDEP) $(GISDEP) EXTRA_INC = $(PROJINC) diff -urN geoPAT-3a75addf/p.sig.points/Makefile geoPAT/p.sig.points/Makefile --- geoPAT-3a75addf/p.sig.points/Makefile 2016-03-05 01:15:31.0 -0500 +++ geoPAT/p.sig.points/Makefile2018-02-24 20:16:27.336234588 -0500 @@ -2,6 +2,8 @@ PGM = p.sig.points +include ../similarlib/Similar.make + LIBES = $(SIMILARLIB) $(RASTERLIB) $(GISLIB) $(MATHLIB) $(VECTORLIB) $(DBMILIB) DEPENDENCIES = $(SIMILARDEP) $(RASTERDEP) $(GISDEP) $(VECTORDEP) $(DBMIDEP) EXTRA_CFLAGS= -I ../similarlib $(VECT_CFLAG
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
How about your GRASS "development" files: installed via package manager? Same version as the binaries? D On Fri, Feb 23, 2018 at 1:10 PM, Pierre Roudier wrote: > Thanks Dylan, > > I did install using `sudo sh install.sh grass72` -- then `sudo sh install.sh > grass74` after my Grass version got updated to 7.4 > > Cheers, > > P > > On 23 February 2018 at 18:41, Dylan Beaudette > wrote: >> >> Howdy Pierre! >> >> In my experience, the GeoPat modules need to know where several things >> are located, including (I think) parts of the GRASS source code. Have >> a look through the install.sh code: >> >> http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh >> >> I was able to get these modules up and running by invoking install.sh like >> this: >> >> sh install.sh grass75 >> >> ... where "grass75" is the binary compiled from grass_trunk. The >> install.sh code seemed to find the source code it needed and worked >> without issue. >> >> How did you install / upgrade the Geopat modules? Could it be that >> install.sh is "finding" the old source code / headers? Is there a >> package for both GRASS binaries and development files? >> >> Dylan >> >> >> On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier >> wrote: >> > Hi, >> > >> > I've been compiling the geoPAT extensions for GRASS from >> > http://sil.uc.edu/gitlist/geoPAT/ >> > >> > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS >> > repository, but since this repo updated to GRASS 7.4, I have the >> > following >> > issue: >> > >> > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help >> > ERROR: Module built against version $Revision: 70617 $ but trying to use >> >version $Revision: 70829 $. You need to rebuild GRASS GIS or >> >untangle multiple installations. >> > [Raster MASK present] >> > >> > Any pointers about how to resolve the version tangling? I've tried >> > recompiling geoPAT, but that didn't work. >> > >> > Cheers, >> > >> > Pierre >> > >> > ___ >> > grass-dev mailing list >> > grass-dev@lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Thanks Dylan, I did install using `sudo sh install.sh grass72` -- then `sudo sh install.sh grass74` after my Grass version got updated to 7.4 Cheers, P On 23 February 2018 at 18:41, Dylan Beaudette wrote: > Howdy Pierre! > > In my experience, the GeoPat modules need to know where several things > are located, including (I think) parts of the GRASS source code. Have > a look through the install.sh code: > > http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh > > I was able to get these modules up and running by invoking install.sh like > this: > > sh install.sh grass75 > > ... where "grass75" is the binary compiled from grass_trunk. The > install.sh code seemed to find the source code it needed and worked > without issue. > > How did you install / upgrade the Geopat modules? Could it be that > install.sh is "finding" the old source code / headers? Is there a > package for both GRASS binaries and development files? > > Dylan > > > On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier > wrote: > > Hi, > > > > I've been compiling the geoPAT extensions for GRASS from > > http://sil.uc.edu/gitlist/geoPAT/ > > > > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS > > repository, but since this repo updated to GRASS 7.4, I have the > following > > issue: > > > > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help > > ERROR: Module built against version $Revision: 70617 $ but trying to use > >version $Revision: 70829 $. You need to rebuild GRASS GIS or > >untangle multiple installations. > > [Raster MASK present] > > > > Any pointers about how to resolve the version tangling? I've tried > > recompiling geoPAT, but that didn't work. > > > > Cheers, > > > > Pierre > > > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Untangling geoPAT installation when updating GRASS version
Howdy Pierre! In my experience, the GeoPat modules need to know where several things are located, including (I think) parts of the GRASS source code. Have a look through the install.sh code: http://sil.uc.edu/gitlist/geoPAT/blob/stable/install.sh I was able to get these modules up and running by invoking install.sh like this: sh install.sh grass75 ... where "grass75" is the binary compiled from grass_trunk. The install.sh code seemed to find the source code it needed and worked without issue. How did you install / upgrade the Geopat modules? Could it be that install.sh is "finding" the old source code / headers? Is there a package for both GRASS binaries and development files? Dylan On Thu, Feb 22, 2018 at 7:28 PM, Pierre Roudier wrote: > Hi, > > I've been compiling the geoPAT extensions for GRASS from > http://sil.uc.edu/gitlist/geoPAT/ > > At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS > repository, but since this repo updated to GRASS 7.4, I have the following > issue: > > GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help > ERROR: Module built against version $Revision: 70617 $ but trying to use >version $Revision: 70829 $. You need to rebuild GRASS GIS or >untangle multiple installations. > [Raster MASK present] > > Any pointers about how to resolve the version tangling? I've tried > recompiling geoPAT, but that didn't work. > > Cheers, > > Pierre > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Untangling geoPAT installation when updating GRASS version
Hi, I've been compiling the geoPAT extensions for GRASS from http://sil.uc.edu/gitlist/geoPAT/ At the time I was running GRASS 7.2.2 installed from the Ubuntu GIS repository, but since this repo updated to GRASS 7.4, I have the following issue: GRASS 7.4.0 (modis_lst_2015):~ > p.sig.polygons --help ERROR: Module built against version $Revision: 70617 $ but trying to use version $Revision: 70829 $. You need to rebuild GRASS GIS or untangle multiple installations. [Raster MASK present] Any pointers about how to resolve the version tangling? I've tried recompiling geoPAT, but that didn't work. Cheers, Pierre ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev