installing addon problem for regular users (ubuntu newbies)

13 messages Options
Embed this post
Permalink
Horacio Samaniego

installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
Dear Nathan,

I discovered that the origin of the problem seem to be that the grass package in ubuntu is not compiled using 64bit libs and that to my understanding it's what's giving us problems. I concluded that by the nature of the error I was getting. So., I kind of went the long way... I repackaged grass for my architecture using:


sudo apt-get source grass # downloads the source tree in current dir
cd grass*
dpkg-buildpackage -rfakeroot # will generate all the -dev -doc packages. best to use sudo?
sudo dpkg -i ../*grass*deb # will install everything

Once you've gone through that, you can simply install addons the normel way. Which is:

download addon to /usr/lib/grass64/ raster or vector (depending on the type of addon) and make, make compile


that solved the problem and created a real 64bit grass package along the way. The key seem to be that the installation of the -dev package provides all the libraries to install new addon. The problem arises when you simply install grass from the repository which is NOT 64bit!! but nonetheless functional.

I hope that this will help!

I'll post this solution to the wiki if nobody objects my assessment of this particular issue. So, please, comment on it if you have a deeper understanding of this than we have...

Cheers,

H


On Fri, Oct 23, 2009 at 11:26 PM, Currit, Nathan Allen <[hidden email]> wrote:
Hi Horacio,

I saw you question posted on <org.osgeo.lists.grass-user>, but I do not see any responses.  Did you find a solution to your problem?  I have the same problem.

Thanks,

Nate

***********
Nate Currit
Texas State University - San Marcos
Department of Geography
San Marcos, Texas 78666-4616



--
Horacio Samaniego, PhD
Instituto de Silvicultura
Facultad de Ciencias Forestales
Universidad Austral de Chile
Valdivia, Chile

+56 (63) 222480 [of.]
http://www.ecoinformatica.cl

_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Alex Mandel-2

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
Were you using the default package in Ubuntu or the ones from Ubuntugis PPA?

Alex

Horacio Samaniego wrote:

> Dear Nathan,
>
> I discovered that the origin of the problem seem to be that the grass
> package in ubuntu is not compiled using 64bit libs and that to my
> understanding it's what's giving us problems. I concluded that by the nature
> of the error I was getting. So., I kind of went the long way... I repackaged
> grass for my architecture using:
>
>
> sudo apt-get source grass # downloads the source tree in current dir
> cd grass*
> dpkg-buildpackage -rfakeroot # will generate all the -dev -doc packages.
> best to use sudo?
> sudo dpkg -i ../*grass*deb # will install everything
>
> Once you've gone through that, you can simply install addons the normel way.
> Which is:
>
> download addon to /usr/lib/grass64/ raster or vector (depending on the type
> of addon) and make, make compile
>
>
> that solved the problem and created a real 64bit grass package along the
> way. The key seem to be that the installation of the -dev package provides
> all the libraries to install new addon. The problem arises when you simply
> install grass from the repository which is NOT 64bit!! but nonetheless
> functional.
>
> I hope that this will help!
>
> I'll post this solution to the wiki if nobody objects my assessment of this
> particular issue. So, please, comment on it if you have a deeper
> understanding of this than we have...
>
> Cheers,
>
> H
>
>
> On Fri, Oct 23, 2009 at 11:26 PM, Currit, Nathan Allen
> <[hidden email]>wrote:
>
>> Hi Horacio,
>>
>> I saw you question posted on <org.osgeo.lists.grass-user>, but I do not see
>> any responses.  Did you find a solution to your problem?  I have the same
>> problem.
>>
>> Thanks,
>>
>> Nate
>>
>> ***********
>> Nate Currit
>> Texas State University - San Marcos
>> Department of Geography
>> San Marcos, Texas 78666-4616
>
>

_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Horacio Samaniego

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
At this point I'm not sure... but believe that I had the ppa on my repositories...


On Sat, Oct 24, 2009 at 4:48 PM, Alex Mandel <[hidden email]> wrote:
Were you using the default package in Ubuntu or the ones from Ubuntugis PPA?

Alex

Horacio Samaniego wrote:
> Dear Nathan,
>
> I discovered that the origin of the problem seem to be that the grass
> package in ubuntu is not compiled using 64bit libs and that to my
> understanding it's what's giving us problems. I concluded that by the nature
> of the error I was getting. So., I kind of went the long way... I repackaged
> grass for my architecture using:
>
>
> sudo apt-get source grass # downloads the source tree in current dir
> cd grass*
> dpkg-buildpackage -rfakeroot # will generate all the -dev -doc packages.
> best to use sudo?
> sudo dpkg -i ../*grass*deb # will install everything
>
> Once you've gone through that, you can simply install addons the normel way.
> Which is:
>
> download addon to /usr/lib/grass64/ raster or vector (depending on the type
> of addon) and make, make compile
>
>
> that solved the problem and created a real 64bit grass package along the
> way. The key seem to be that the installation of the -dev package provides
> all the libraries to install new addon. The problem arises when you simply
> install grass from the repository which is NOT 64bit!! but nonetheless
> functional.
>
> I hope that this will help!
>
> I'll post this solution to the wiki if nobody objects my assessment of this
> particular issue. So, please, comment on it if you have a deeper
> understanding of this than we have...
>
> Cheers,
>
> H
>
>
> On Fri, Oct 23, 2009 at 11:26 PM, Currit, Nathan Allen
> <[hidden email]>wrote:
>
>> Hi Horacio,
>>
>> I saw you question posted on <org.osgeo.lists.grass-user>, but I do not see
>> any responses.  Did you find a solution to your problem?  I have the same
>> problem.
>>
>> Thanks,
>>
>> Nate
>>
>> ***********
>> Nate Currit
>> Texas State University - San Marcos
>> Department of Geography
>> San Marcos, Texas 78666-4616
>
>




--
Horacio Samaniego, PhD
Instituto de Silvicultura
Facultad de Ciencias Forestales
Universidad Austral de Chile
Valdivia, Chile

+56 (63) 222480 [of.]
http://www.ecoinformatica.cl

_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
I just installed from ubuntugis, and the package is
grass_6.4.0~rc5-3~karmic1_amd64.deb, which I presume to be 64bit.

I have problems compiling addons (using ubuntugis).

Mark

On Sat, Oct 24, 2009 at 7:17 PM, Horacio Samaniego
<[hidden email]> wrote:

> At this point I'm not sure... but believe that I had the ppa on my
> repositories...
>
>
> On Sat, Oct 24, 2009 at 4:48 PM, Alex Mandel <[hidden email]>
> wrote:
>>
>> Were you using the default package in Ubuntu or the ones from Ubuntugis
>> PPA?
>>
>> Alex
>>
>> Horacio Samaniego wrote:
>> > Dear Nathan,
>> >
>> > I discovered that the origin of the problem seem to be that the grass
>> > package in ubuntu is not compiled using 64bit libs and that to my
>> > understanding it's what's giving us problems. I concluded that by the
>> > nature
>> > of the error I was getting. So., I kind of went the long way... I
>> > repackaged
>> > grass for my architecture using:
>> >
>> >
>> > sudo apt-get source grass # downloads the source tree in current dir
>> > cd grass*
>> > dpkg-buildpackage -rfakeroot # will generate all the -dev -doc packages.
>> > best to use sudo?
>> > sudo dpkg -i ../*grass*deb # will install everything
>> >
>> > Once you've gone through that, you can simply install addons the normel
>> > way.
>> > Which is:
>> >
>> > download addon to /usr/lib/grass64/ raster or vector (depending on the
>> > type
>> > of addon) and make, make compile
>> >
>> >
>> > that solved the problem and created a real 64bit grass package along the
>> > way. The key seem to be that the installation of the -dev package
>> > provides
>> > all the libraries to install new addon. The problem arises when you
>> > simply
>> > install grass from the repository which is NOT 64bit!! but nonetheless
>> > functional.
>> >
>> > I hope that this will help!
>> >
>> > I'll post this solution to the wiki if nobody objects my assessment of
>> > this
>> > particular issue. So, please, comment on it if you have a deeper
>> > understanding of this than we have...
>> >
>> > Cheers,
>> >
>> > H
>> >
>> >
>> > On Fri, Oct 23, 2009 at 11:26 PM, Currit, Nathan Allen
>> > <[hidden email]>wrote:
>> >
>> >> Hi Horacio,
>> >>
>> >> I saw you question posted on <org.osgeo.lists.grass-user>, but I do not
>> >> see
>> >> any responses.  Did you find a solution to your problem?  I have the
>> >> same
>> >> problem.
>> >>
>> >> Thanks,
>> >>
>> >> Nate
>> >>
>> >> ***********
>> >> Nate Currit
>> >> Texas State University - San Marcos
>> >> Department of Geography
>> >> San Marcos, Texas 78666-4616
>> >
>> >
>>
>
>
>
> --
> Horacio Samaniego, PhD
> Instituto de Silvicultura
> Facultad de Ciencias Forestales
> Universidad Austral de Chile
> Valdivia, Chile
>
> +56 (63) 222480 [of.]
> http://www.ecoinformatica.cl
>
> _______________________________________________
> grass-user mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Markus Neteler

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
On Tue, Nov 3, 2009 at 1:32 PM, M S <[hidden email]> wrote:
> I just installed from ubuntugis, and the package is
> grass_6.4.0~rc5-3~karmic1_amd64.deb, which I presume to be 64bit.
>
> I have problems compiling addons (using ubuntugis).

Perhaps you are hit by this one:
http://trac.osgeo.org/grass/ticket/620

Markus
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
It appears so.  I'm going to look at the posts and see if I can get
mine to work.

Thanks,
Mark

On Tue, Nov 3, 2009 at 7:38 AM, Markus Neteler <[hidden email]> wrote:

> On Tue, Nov 3, 2009 at 1:32 PM, M S <[hidden email]> wrote:
>> I just installed from ubuntugis, and the package is
>> grass_6.4.0~rc5-3~karmic1_amd64.deb, which I presume to be 64bit.
>>
>> I have problems compiling addons (using ubuntugis).
>
> Perhaps you are hit by this one:
> http://trac.osgeo.org/grass/ticket/620
>
> Markus
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
In reply to this post by Markus Neteler
Markus,

Based on http://lists.osgeo.org/pipermail/grass-user/2009-August/052074.html,
is there a checklist of variables I can go through in the
Platform.make file to change variable values to /usr/lib/grass64 ?

Thanks,
Mark

On Tue, Nov 3, 2009 at 7:38 AM, Markus Neteler <[hidden email]> wrote:

> On Tue, Nov 3, 2009 at 1:32 PM, M S <[hidden email]> wrote:
>> I just installed from ubuntugis, and the package is
>> grass_6.4.0~rc5-3~karmic1_amd64.deb, which I presume to be 64bit.
>>
>> I have problems compiling addons (using ubuntugis).
>
> Perhaps you are hit by this one:
> http://trac.osgeo.org/grass/ticket/620
>
> Markus
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Markus Neteler

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
Mark,

On Tue, Nov 10, 2009 at 2:24 PM, M S <[hidden email]> wrote:
> Markus,
>
> Based on http://lists.osgeo.org/pipermail/grass-user/2009-August/052074.html,
> is there a checklist of variables I can go through in the
> Platform.make file to change variable values to /usr/lib/grass64 ?

Since I have no ubuntu I can only suggest to try (and to report back
which didn't appear to happen in August).

Sorry for no better answer (I still hope that a Makefile guru takes a look
and fixes the missing pieces)

Markus
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
I'll try some things and report findings.  With some guidance from a
'make guru', I'm would think this could be resolved.


Thanks,
Mark

On Tue, Nov 10, 2009 at 3:33 PM, Markus Neteler <[hidden email]> wrote:

> Mark,
>
> On Tue, Nov 10, 2009 at 2:24 PM, M S <[hidden email]> wrote:
>> Markus,
>>
>> Based on http://lists.osgeo.org/pipermail/grass-user/2009-August/052074.html,
>> is there a checklist of variables I can go through in the
>> Platform.make file to change variable values to /usr/lib/grass64 ?
>
> Since I have no ubuntu I can only suggest to try (and to report back
> which didn't appear to happen in August).
>
> Sorry for no better answer (I still hope that a Makefile guru takes a look
> and fixes the missing pieces)
>
> Markus
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
I'm on Kubuntu 9.10, using both 32 and 64 bit systems.  This output is
from 32bit.  It is GRASS 6.4 RC5.  Seems to be the same logged issue
of defaulting to /build rather than /var/lib/grass64

-------------------------
I ran "sudo make MODULE_TOPDIR=/usr/lib/grass64"

This is the first line of output"  gcc
-I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include  -Wall
-g -O    -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
-I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include -o
OBJ.i486-pc-linux-gnu/close.o -c close.c  "
---------------------------

If I apply the GRASS_HOME=/usr/lib/grass64:

--------------------------
$ sudo make MODULE_TOPDIR=/usr/lib/grass64 GRASS_HOME=/usr/lib/grass64

gcc -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include  -Wall -g -O
-I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
-I/usr/lib/grass64/dist.i486-pc-linux-gnu/include -o
OBJ.i486-pc-linux-gnu/close.o -c close.c
close.c:1:23: error: grass/gis.h: No such file or  directory
close.c:2:27: error: grass/glocale.h: No such file or directory
close.c:3:24: error: grass/dbmi.h: No such file or directory
close.c:4:24: error: grass/Vect.h: No such file or directory
-------------------------

Should it be looking in /usr/lib/grass64/include, instead of
/usr/lib/grass64/dist.i486-pc-linux-gnu/include ?   The latter
directory is empty.

If so, how do I remove the "dist.i486-pc-linux--gnu" portion from the
gcc statement?


Mark

>
> On Tue, Nov 10, 2009 at 3:33 PM, Markus Neteler <[hidden email]> wrote:
>> Mark,
>>
>> On Tue, Nov 10, 2009 at 2:24 PM, M S <[hidden email]> wrote:
>>> Markus,
>>>
>>> Based on http://lists.osgeo.org/pipermail/grass-user/2009-August/052074.html,
>>> is there a checklist of variables I can go through in the
>>> Platform.make file to change variable values to /usr/lib/grass64 ?
>>
>> Since I have no ubuntu I can only suggest to try (and to report back
>> which didn't appear to happen in August).
>>
>> Sorry for no better answer (I still hope that a Makefile guru takes a look
>> and fixes the missing pieces)
>>
>> Markus
>>
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Glynn Clements

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink

M S wrote:

> I'm on Kubuntu 9.10, using both 32 and 64 bit systems.  This output is
> from 32bit.  It is GRASS 6.4 RC5.  Seems to be the same logged issue
> of defaulting to /build rather than /var/lib/grass64
>
> -------------------------
> I ran "sudo make MODULE_TOPDIR=/usr/lib/grass64"
>
> This is the first line of output"  gcc
> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include  -Wall
> -g -O    -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include -o
> OBJ.i486-pc-linux-gnu/close.o -c close.c  "
> ---------------------------
>
> If I apply the GRASS_HOME=/usr/lib/grass64:
>
> --------------------------
> $ sudo make MODULE_TOPDIR=/usr/lib/grass64 GRASS_HOME=/usr/lib/grass64
>
> gcc -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include  -Wall -g -O
> -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
> -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include -o
> OBJ.i486-pc-linux-gnu/close.o -c close.c
> close.c:1:23: error: grass/gis.h: No such file or  directory
> close.c:2:27: error: grass/glocale.h: No such file or directory
> close.c:3:24: error: grass/dbmi.h: No such file or directory
> close.c:4:24: error: grass/Vect.h: No such file or directory
> -------------------------
>
> Should it be looking in /usr/lib/grass64/include, instead of
> /usr/lib/grass64/dist.i486-pc-linux-gnu/include ?   The latter
> directory is empty.
>
> If so, how do I remove the "dist.i486-pc-linux--gnu" portion from the
> gcc statement?

You could try ARCH_DISTDIR=/usr/lib/grass64, but this may not be
sufficient for complex cases. If you need to search both the installed
version and the build directory for headers and/or libraries, you will
need to set ARCH_INC and/or ARCH_LIBPATH explicitly.

If you still have problems, look at the first two sections of
Grass.make; this defines the most important variables.

6.x is still a bit of a mess in this regard.

In 7.0, ARCH_DISTDIR controls where output files go, while GISBASE
controls where existing libraries and headers are found. Both
$(ARCH_DISTDIR)/include and $(GISBASE)/include are searched for
headers, and both $(ARCH_DISTDIR)/lib and $(GISBASE)/lib are searched
for libraries. This allows a package to use both existing headers and
libraries and those which are part of the package.

RUN_GISBASE is the value of GISBASE used when running GRASS modules as
part of the build process (on Windows, this will be in Windows format
rather than MSys format).

MODULE_TOPDIR is only used to locate the *.make files; everything else
uses the variables from those files.

--
Glynn Clements <[hidden email]>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
Thanks Glynn. I failed to mention the GRASS 6.4RC5 is from UbuntuGIS
with binaries and grass-dev package installed.

It seemed to have worked (?) with errors, or I've been mucking around
too much and missed some detail from prior trial.  Seems to have
error'd while making the manpages.  I can launch r.stream.extract, and
it runs the module. (Nice!).  Here is the input/output (should long
outputs like this go to pastebin or the like?):

$ sudo make MODULE_TOPDIR=/usr/lib/grass64 ARCH_DISTDIR=/usr/lib/grass64
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/close.o -c close.c

close.c: In function ‘close_streamvect’:
close.c:33: warning: format not a string literal and no format arguments
close.c:155: warning: format not a string literal and no format arguments
close.c:187: warning: format not a string literal and no format arguments
close.c:213: warning: format not a string literal and no format arguments
close.c:221: warning: format not a string literal and no format arguments
close.c: In function ‘close_maps’:
close.c:245: warning: format not a string literal and no format arguments
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/del_streams.o -c del_streams.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/do_astar.o -c do_astar.c
do_astar.c: In function ‘do_astar’:
do_astar.c:33: warning: format not a string literal and no format
arguments
do_astar.c: In function ‘heap_add’:
do_astar.c:154: warning: format not a string literal and no format
arguments
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_clr_all.o -c flag_clr_all.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_create.o -c flag_create.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_destroy.o -c flag_destroy.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_get.o -c flag_get.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_set.o -c flag_set.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/flag_unset.o -c flag_unset.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/load.o -c load.c
load.c: In function ‘load_maps’:
load.c:44: warning: format not a string literal and no format
arguments
load.c:46: warning: format not a string literal and no format
arguments
load.c:56: warning: format not a string literal and no format
arguments
load.c:65: warning: format not a string literal and no format
arguments
load.c:75: warning: format not a string literal and no format
arguments
load.c:217: warning: format not a string literal and no format
arguments
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/main.o -c main.c
main.c: In function ‘main’:
main.c:195: warning: format not a string literal and no format
arguments
main.c:246: warning: format not a string literal and no format
arguments
main.c:254: warning: format not a string literal and no format
arguments
main.c:259: warning: format not a string literal and no format
arguments
main.c:267: warning: format not a string literal and no format
arguments
main.c:276: warning: format not a string literal and no format
arguments
main.c:281: warning: format not a string literal and no format
arguments
main.c:287: warning: format not a string literal and no format
arguments
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/rbtree.o -c rbtree.c
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/streams.o -c streams.c
streams.c: In function ‘do_accum’:
streams.c:234: warning: format not a string literal and no format
arguments
streams.c: In function ‘extract_streams’:
streams.c:460: warning: format not a string literal and no format
arguments
gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
-DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
OBJ.i486-pc-linux-gnu/thin.o -c thin.c
thin.c: In function ‘thin_streams’:
thin.c:92: warning: format not a string literal and no format
arguments
gcc -L/usr/lib/grass64/lib -Wl,-Bsymbolic-functions
-Wl,--export-dynamic -Wl,-rpath-link,/usr/lib/grass64/lib    -o
/usr/lib/grass64/bin/r.stream.extract OBJ.i486-pc-linux-gnu/close.o
OBJ.i486-pc-linux-gnu/del_streams.o OBJ.i486-pc-linux-gnu/do_astar.o
OBJ.i486-pc-linux-gnu/flag_clr_all.o
OBJ.i486-pc-linux-gnu/flag_create.o
OBJ.i486-pc-linux-gnu/flag_destroy.o OBJ.i486-pc-linux-gnu/flag_get.o
OBJ.i486-pc-linux-gnu/flag_set.o OBJ.i486-pc-linux-gnu/flag_unset.o
OBJ.i486-pc-linux-gnu/load.o OBJ.i486-pc-linux-gnu/main.o
OBJ.i486-pc-linux-gnu/rbtree.o OBJ.i486-pc-linux-gnu/streams.o
OBJ.i486-pc-linux-gnu/thin.o  -lgrass_vect -lgrass_dbmibase
-lgrass_gis -lgrass_datetime -lz      -lgrass_dbmiclient
-lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz      -lgrass_gis
-lgrass_datetime -lz      -lgrass_dgl -lgrass_dig2 -lgrass_gis
-lgrass_datetime -lz     -lgrass_rtree  -lgrass_gis -lgrass_datetime
-lz     -lgrass_linkm -lgrass_rtree  -lgrass_dig2 -lgrass_gis
-lgrass_datetime -lz     -lgrass_rtree  -lgrass_dgl -lgrass_rtree
-lgrass_linkm -lgrass_dbmiclient -lgrass_dbmibase -lgrass_gis
-lgrass_datetime -lz      -lgrass_gis -lgrass_datetime -lz
-lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz       -L/usr/lib
-lgdal1.6.0 -lgrass_dbmiclient -lgrass_dbmibase -lgrass_gis
-lgrass_datetime -lz      -lgrass_gis -lgrass_datetime -lz
-lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz       -lgrass_gis
-lgrass_datetime -lz     -lm  -lz
make htmlcmd
make[1]: Entering directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make /usr/lib/grass64/docs/html/r.stream.extract.html
HTMLSRC=/usr/lib/grass64/bin/r.stream.extract
make[2]: Entering directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
if [ "/usr/lib/grass64/bin/r.stream.extract" != "" ] ; then
GISRC=/usr/lib/grass64/demolocation/.grassrc64
GISBASE=/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu
PATH="/usr/lib/grass64/bin:$PATH"
LD_LIBRARY_PATH="/usr/lib/grass64/bin:/usr/lib/grass64/lib:" LC_ALL=C
fakeroot /usr/lib/grass64/bin/r.stream.extract --html-description <
/dev/null | grep -v '</body>\|</html>' > r.stream.extract.tmp.html ;
true ; fi
ERROR: G_getenv(): Variable LOCATION_NAME not set
/usr/lib/grass64/tools/mkhtml.sh r.stream.extract ; mkdir -p
/usr/lib/grass64/docs/html ; /usr/bin/install -c  -m 644
r.stream.extract.tmp.html
/usr/lib/grass64/docs/html/r.stream.extract.html ; for file in  *.png
*.jpg ; do head -n 1 $file | grep '^#!' > /dev/null ; if [ $? -ne 0 ]
; then /usr/bin/install -c  -m 644 $file /usr/lib/grass64/docs/html ;
fi done 2> /dev/null ; true
/bin/sh: /usr/lib/grass64/tools/mkhtml.sh: not found
make[2]: Leaving directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make[1]: Leaving directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make mancmd
make[1]: Entering directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make /usr/lib/grass64/man/man1/r.stream.extract.1
MANSRC=/usr/lib/grass64/docs/html/r.stream.extract.html
make[2]: Entering directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
mkdir -p /usr/lib/grass64/man/man1
GRASS_PERL=/usr/bin/perl VERSION_NUMBER=6.4.0RC5 sh
/build/buildd/grass-6.4.0~rc5/tools/g.html2man/g.html2man
/usr/lib/grass64/docs/html/r.stream.extract.html
/usr/lib/grass64/man/man1/r.stream.extract.1 1
sh: Can't open /build/buildd/grass-6.4.0~rc5/tools/g.html2man/g.html2man
make[2]: *** [/usr/lib/grass64/man/man1/r.stream.extract.1] Error 2
make[2]: Leaving directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make[1]: *** [mancmd] Error 2
make[1]: Leaving directory
`/usr/lib/grass64/grass-addons/raster/r.stream.extract'
make: *** [cmd] Error 2


On Thu, Nov 12, 2009 at 10:32 AM, Glynn Clements
<[hidden email]> wrote:

>
> M S wrote:
>
>> I'm on Kubuntu 9.10, using both 32 and 64 bit systems.  This output is
>> from 32bit.  It is GRASS 6.4 RC5.  Seems to be the same logged issue
>> of defaulting to /build rather than /var/lib/grass64
>>
>> -------------------------
>> I ran "sudo make MODULE_TOPDIR=/usr/lib/grass64"
>>
>> This is the first line of output"  gcc
>> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include  -Wall
>> -g -O    -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
>> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include -o
>> OBJ.i486-pc-linux-gnu/close.o -c close.c  "
>> ---------------------------
>>
>> If I apply the GRASS_HOME=/usr/lib/grass64:
>>
>> --------------------------
>> $ sudo make MODULE_TOPDIR=/usr/lib/grass64 GRASS_HOME=/usr/lib/grass64
>>
>> gcc -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include  -Wall -g -O
>> -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
>> -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include -o
>> OBJ.i486-pc-linux-gnu/close.o -c close.c
>> close.c:1:23: error: grass/gis.h: No such file or  directory
>> close.c:2:27: error: grass/glocale.h: No such file or directory
>> close.c:3:24: error: grass/dbmi.h: No such file or directory
>> close.c:4:24: error: grass/Vect.h: No such file or directory
>> -------------------------
>>
>> Should it be looking in /usr/lib/grass64/include, instead of
>> /usr/lib/grass64/dist.i486-pc-linux-gnu/include ?   The latter
>> directory is empty.
>>
>> If so, how do I remove the "dist.i486-pc-linux--gnu" portion from the
>> gcc statement?
>
> You could try ARCH_DISTDIR=/usr/lib/grass64, but this may not be
> sufficient for complex cases. If you need to search both the installed
> version and the build directory for headers and/or libraries, you will
> need to set ARCH_INC and/or ARCH_LIBPATH explicitly.
>
> If you still have problems, look at the first two sections of
> Grass.make; this defines the most important variables.
>
> 6.x is still a bit of a mess in this regard.
>
> In 7.0, ARCH_DISTDIR controls where output files go, while GISBASE
> controls where existing libraries and headers are found. Both
> $(ARCH_DISTDIR)/include and $(GISBASE)/include are searched for
> headers, and both $(ARCH_DISTDIR)/lib and $(GISBASE)/lib are searched
> for libraries. This allows a package to use both existing headers and
> libraries and those which are part of the package.
>
> RUN_GISBASE is the value of GISBASE used when running GRASS modules as
> part of the build process (on Windows, this will be in Windows format
> rather than MSys format).
>
> MODULE_TOPDIR is only used to locate the *.make files; everything else
> uses the variables from those files.
>
> --
> Glynn Clements <[hidden email]>
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
MS-5

Re: installing addon problem for regular users (ubuntu newbies)

Reply Threaded More More options
Print post
Permalink
Excellent.  Seems to be working ok. I just ran the same command "sudo
make MODULE_TOPDIR=/usr/lib/grass64 ARCH_DIST=/usr/lib/grass64" for
the r.inund.fluv and it ran without error.

Thanks for the help.  Most excellent!

Mark

On Thu, Nov 12, 2009 at 11:00 AM, M S <[hidden email]> wrote:

> Thanks Glynn. I failed to mention the GRASS 6.4RC5 is from UbuntuGIS
> with binaries and grass-dev package installed.
>
> It seemed to have worked (?) with errors, or I've been mucking around
> too much and missed some detail from prior trial.  Seems to have
> error'd while making the manpages.  I can launch r.stream.extract, and
> it runs the module. (Nice!).  Here is the input/output (should long
> outputs like this go to pastebin or the like?):
>
> $ sudo make MODULE_TOPDIR=/usr/lib/grass64 ARCH_DISTDIR=/usr/lib/grass64
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/close.o -c close.c
>
> close.c: In function ‘close_streamvect’:
> close.c:33: warning: format not a string literal and no format arguments
> close.c:155: warning: format not a string literal and no format arguments
> close.c:187: warning: format not a string literal and no format arguments
> close.c:213: warning: format not a string literal and no format arguments
> close.c:221: warning: format not a string literal and no format arguments
> close.c: In function ‘close_maps’:
> close.c:245: warning: format not a string literal and no format arguments
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/del_streams.o -c del_streams.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/do_astar.o -c do_astar.c
> do_astar.c: In function ‘do_astar’:
> do_astar.c:33: warning: format not a string literal and no format
> arguments
> do_astar.c: In function ‘heap_add’:
> do_astar.c:154: warning: format not a string literal and no format
> arguments
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_clr_all.o -c flag_clr_all.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_create.o -c flag_create.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_destroy.o -c flag_destroy.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_get.o -c flag_get.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_set.o -c flag_set.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/flag_unset.o -c flag_unset.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/load.o -c load.c
> load.c: In function ‘load_maps’:
> load.c:44: warning: format not a string literal and no format
> arguments
> load.c:46: warning: format not a string literal and no format
> arguments
> load.c:56: warning: format not a string literal and no format
> arguments
> load.c:65: warning: format not a string literal and no format
> arguments
> load.c:75: warning: format not a string literal and no format
> arguments
> load.c:217: warning: format not a string literal and no format
> arguments
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/main.o -c main.c
> main.c: In function ‘main’:
> main.c:195: warning: format not a string literal and no format
> arguments
> main.c:246: warning: format not a string literal and no format
> arguments
> main.c:254: warning: format not a string literal and no format
> arguments
> main.c:259: warning: format not a string literal and no format
> arguments
> main.c:267: warning: format not a string literal and no format
> arguments
> main.c:276: warning: format not a string literal and no format
> arguments
> main.c:281: warning: format not a string literal and no format
> arguments
> main.c:287: warning: format not a string literal and no format
> arguments
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/rbtree.o -c rbtree.c
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/streams.o -c streams.c
> streams.c: In function ‘do_accum’:
> streams.c:234: warning: format not a string literal and no format
> arguments
> streams.c: In function ‘extract_streams’:
> streams.c:460: warning: format not a string literal and no format
> arguments
> gcc -I/usr/lib/grass64/include  -Wall -g -O    -I/usr/include/gdal
> -DPACKAGE=\""grassmods"\"  -I/usr/lib/grass64/include -o
> OBJ.i486-pc-linux-gnu/thin.o -c thin.c
> thin.c: In function ‘thin_streams’:
> thin.c:92: warning: format not a string literal and no format
> arguments
> gcc -L/usr/lib/grass64/lib -Wl,-Bsymbolic-functions
> -Wl,--export-dynamic -Wl,-rpath-link,/usr/lib/grass64/lib    -o
> /usr/lib/grass64/bin/r.stream.extract OBJ.i486-pc-linux-gnu/close.o
> OBJ.i486-pc-linux-gnu/del_streams.o OBJ.i486-pc-linux-gnu/do_astar.o
> OBJ.i486-pc-linux-gnu/flag_clr_all.o
> OBJ.i486-pc-linux-gnu/flag_create.o
> OBJ.i486-pc-linux-gnu/flag_destroy.o OBJ.i486-pc-linux-gnu/flag_get.o
> OBJ.i486-pc-linux-gnu/flag_set.o OBJ.i486-pc-linux-gnu/flag_unset.o
> OBJ.i486-pc-linux-gnu/load.o OBJ.i486-pc-linux-gnu/main.o
> OBJ.i486-pc-linux-gnu/rbtree.o OBJ.i486-pc-linux-gnu/streams.o
> OBJ.i486-pc-linux-gnu/thin.o  -lgrass_vect -lgrass_dbmibase
> -lgrass_gis -lgrass_datetime -lz      -lgrass_dbmiclient
> -lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz      -lgrass_gis
> -lgrass_datetime -lz      -lgrass_dgl -lgrass_dig2 -lgrass_gis
> -lgrass_datetime -lz     -lgrass_rtree  -lgrass_gis -lgrass_datetime
> -lz     -lgrass_linkm -lgrass_rtree  -lgrass_dig2 -lgrass_gis
> -lgrass_datetime -lz     -lgrass_rtree  -lgrass_dgl -lgrass_rtree
> -lgrass_linkm -lgrass_dbmiclient -lgrass_dbmibase -lgrass_gis
> -lgrass_datetime -lz      -lgrass_gis -lgrass_datetime -lz
> -lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz       -L/usr/lib
> -lgdal1.6.0 -lgrass_dbmiclient -lgrass_dbmibase -lgrass_gis
> -lgrass_datetime -lz      -lgrass_gis -lgrass_datetime -lz
> -lgrass_dbmibase -lgrass_gis -lgrass_datetime -lz       -lgrass_gis
> -lgrass_datetime -lz     -lm  -lz
> make htmlcmd
> make[1]: Entering directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make /usr/lib/grass64/docs/html/r.stream.extract.html
> HTMLSRC=/usr/lib/grass64/bin/r.stream.extract
> make[2]: Entering directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> if [ "/usr/lib/grass64/bin/r.stream.extract" != "" ] ; then
> GISRC=/usr/lib/grass64/demolocation/.grassrc64
> GISBASE=/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu
> PATH="/usr/lib/grass64/bin:$PATH"
> LD_LIBRARY_PATH="/usr/lib/grass64/bin:/usr/lib/grass64/lib:" LC_ALL=C
> fakeroot /usr/lib/grass64/bin/r.stream.extract --html-description <
> /dev/null | grep -v '</body>\|</html>' > r.stream.extract.tmp.html ;
> true ; fi
> ERROR: G_getenv(): Variable LOCATION_NAME not set
> /usr/lib/grass64/tools/mkhtml.sh r.stream.extract ; mkdir -p
> /usr/lib/grass64/docs/html ; /usr/bin/install -c  -m 644
> r.stream.extract.tmp.html
> /usr/lib/grass64/docs/html/r.stream.extract.html ; for file in  *.png
> *.jpg ; do head -n 1 $file | grep '^#!' > /dev/null ; if [ $? -ne 0 ]
> ; then /usr/bin/install -c  -m 644 $file /usr/lib/grass64/docs/html ;
> fi done 2> /dev/null ; true
> /bin/sh: /usr/lib/grass64/tools/mkhtml.sh: not found
> make[2]: Leaving directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make[1]: Leaving directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make mancmd
> make[1]: Entering directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make /usr/lib/grass64/man/man1/r.stream.extract.1
> MANSRC=/usr/lib/grass64/docs/html/r.stream.extract.html
> make[2]: Entering directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> mkdir -p /usr/lib/grass64/man/man1
> GRASS_PERL=/usr/bin/perl VERSION_NUMBER=6.4.0RC5 sh
> /build/buildd/grass-6.4.0~rc5/tools/g.html2man/g.html2man
> /usr/lib/grass64/docs/html/r.stream.extract.html
> /usr/lib/grass64/man/man1/r.stream.extract.1 1
> sh: Can't open /build/buildd/grass-6.4.0~rc5/tools/g.html2man/g.html2man
> make[2]: *** [/usr/lib/grass64/man/man1/r.stream.extract.1] Error 2
> make[2]: Leaving directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make[1]: *** [mancmd] Error 2
> make[1]: Leaving directory
> `/usr/lib/grass64/grass-addons/raster/r.stream.extract'
> make: *** [cmd] Error 2
>
>
> On Thu, Nov 12, 2009 at 10:32 AM, Glynn Clements
> <[hidden email]> wrote:
>>
>> M S wrote:
>>
>>> I'm on Kubuntu 9.10, using both 32 and 64 bit systems.  This output is
>>> from 32bit.  It is GRASS 6.4 RC5.  Seems to be the same logged issue
>>> of defaulting to /build rather than /var/lib/grass64
>>>
>>> -------------------------
>>> I ran "sudo make MODULE_TOPDIR=/usr/lib/grass64"
>>>
>>> This is the first line of output"  gcc
>>> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include  -Wall
>>> -g -O    -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
>>> -I/build/buildd/grass-6.4.0~rc5/dist.i486-pc-linux-gnu/include -o
>>> OBJ.i486-pc-linux-gnu/close.o -c close.c  "
>>> ---------------------------
>>>
>>> If I apply the GRASS_HOME=/usr/lib/grass64:
>>>
>>> --------------------------
>>> $ sudo make MODULE_TOPDIR=/usr/lib/grass64 GRASS_HOME=/usr/lib/grass64
>>>
>>> gcc -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include  -Wall -g -O
>>> -I/usr/include/gdal    -DPACKAGE=\""grassmods"\"
>>> -I/usr/lib/grass64/dist.i486-pc-linux-gnu/include -o
>>> OBJ.i486-pc-linux-gnu/close.o -c close.c
>>> close.c:1:23: error: grass/gis.h: No such file or  directory
>>> close.c:2:27: error: grass/glocale.h: No such file or directory
>>> close.c:3:24: error: grass/dbmi.h: No such file or directory
>>> close.c:4:24: error: grass/Vect.h: No such file or directory
>>> -------------------------
>>>
>>> Should it be looking in /usr/lib/grass64/include, instead of
>>> /usr/lib/grass64/dist.i486-pc-linux-gnu/include ?   The latter
>>> directory is empty.
>>>
>>> If so, how do I remove the "dist.i486-pc-linux--gnu" portion from the
>>> gcc statement?
>>
>> You could try ARCH_DISTDIR=/usr/lib/grass64, but this may not be
>> sufficient for complex cases. If you need to search both the installed
>> version and the build directory for headers and/or libraries, you will
>> need to set ARCH_INC and/or ARCH_LIBPATH explicitly.
>>
>> If you still have problems, look at the first two sections of
>> Grass.make; this defines the most important variables.
>>
>> 6.x is still a bit of a mess in this regard.
>>
>> In 7.0, ARCH_DISTDIR controls where output files go, while GISBASE
>> controls where existing libraries and headers are found. Both
>> $(ARCH_DISTDIR)/include and $(GISBASE)/include are searched for
>> headers, and both $(ARCH_DISTDIR)/lib and $(GISBASE)/lib are searched
>> for libraries. This allows a package to use both existing headers and
>> libraries and those which are part of the package.
>>
>> RUN_GISBASE is the value of GISBASE used when running GRASS modules as
>> part of the build process (on Windows, this will be in Windows format
>> rather than MSys format).
>>
>> MODULE_TOPDIR is only used to locate the *.make files; everything else
>> uses the variables from those files.
>>
>> --
>> Glynn Clements <[hidden email]>
>>
>
_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user