Compile help

Could anyone help a new guy compile GRASS 5b6

running linux mandrake 7

having ran ./configure then make i get the following error :-

root@localhost grass5.0beta]# make

if [ ! -d /usr/local/grass-5.0b ]; then mkdir /usr/local/grass-5.0b ; fi

if [ ! -d src/CMD/next_step ]; then mkdir src/CMD/next_step ; fi

/root/.bashrc UNIX_BIN=/usr/local/bin SRC=pwd GISBASE=/usr/local/grass-5.0b MACHINENAME=uname -n /bin/sh src/CMD/generic/CREATE_GMAKE.sh

/bin/sh: /root/.bashrc: Permission denied / ************ error ******************/

make: *** [pre-install] Error 126

[root@localhost grass5.0beta]#

Where have i gone wrong ?!

Thanks

David Armstrong

david.armstrong@dtn.ntl.com

On Sun, Mar 05, 2000 at 09:11:37PM +0000, David Armstrong wrote:

Could anyone help a new guy compile GRASS 5b6

running linux mandrake 7

having ran ./configure then make i get the following error :-
root@localhost grass5.0beta]# make

if [ ! -d /usr/local/grass-5.0b ]; then mkdir /usr/local/grass-5.0b ; fi

if [ ! -d src/CMD/next_step ]; then mkdir src/CMD/next_step ; fi

/root/.bashrc UNIX_BIN=/usr/local/bin SRC=`pwd` GISBASE=/usr/local/grass-5.0b MACHINENAME=`uname -n` /bin/sh src/CMD/generic/CREATE_GMAKE.sh

/bin/sh: /root/.bashrc: Permission denied / ************ error ******************/

What are the permissions on /root/.bashrc ? and does it exist?

The line in the Makefile that's giving you grief is in the pre-install:

        ${ENV} ${MAKE_GMAKE_ENV} ${MAKE_POST_ENV} ${SHELL}
  src/CMD/generic/CREATE_GMAKE.sh

It's calling the program "env" to modify the environment for
compilation, and it's trying to source your /root/.bashrc. If it doesn't
exist, just do "touch /root/.bashrc" to create an empty file.

Unfortunately, grass is still a little braindamaged in the
compilation/installation. It's generally recommended to never compile
things as root 'cause "Bad things can happen". I'd recommend giving
yourself write privledges to /usr/local. I don't know what the group
settings are for /usr/local on Mandrake, but mine are root.staff. So, by
adding myself to the group staff "adduser <username> <group>", I have
write persmission to /usr/local. Then I just "make install" as a normal
user. It'd be better if GRASS's "make" or "make all" would just compile
the binaries but not install them, then you could "su -c 'make
install'". But, for various reasons, that's currently not possible.

Hope the above helps.

--
+----------------------------------------------------+
| Eric G. Miller egm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
+----------------------------------------------------+

Hi all,

On Sun, Mar 05, 2000 at 02:05:45PM -0800, Eric G . Miller wrote:

On Sun, Mar 05, 2000 at 09:11:37PM +0000, David Armstrong wrote:
> Could anyone help a new guy compile GRASS 5b6
>
> running linux mandrake 7

[...]

The line in the Makefile that's giving you grief is in the pre-install:

        ${ENV} ${MAKE_GMAKE_ENV} ${MAKE_POST_ENV} ${SHELL}

[...]

It's calling the program "env" to modify the environment for
compilation, and it's trying to source your /root/.bashrc. If it doesn't
exist, just do "touch /root/.bashrc" to create an empty file.

Please check Makefile, if ${ENV} was expanded to "env" properly.
It fails on a few platforms (why?).

Unfortunately, grass is still a little braindamaged in the
compilation/installation. It's generally recommended to never compile
things as root 'cause "Bad things can happen". I'd recommend giving

Oh! What are the problems here? Then we can try to fix them.

It'd be better if GRASS's "make" or "make all" would just compile
the binaries but not install them, then you could "su -c 'make
install'". But, for various reasons, that's currently not possible.

We are working on this, it is a non-trivial task due to GRASS
programming history. Currently we are lucky that at least "auto-conf"
is working :slight_smile: Our plans are to restructure the GRASS sources
to small content-oriented packages (GRASS-Core, GRASS-basic, ...)
with GNU-style make/make install. I hope we manage soon but
any help would be appreciated. Please contact me on this if
you could support us.

Regards
  
Markus Neteler

Markus Neteler wrote:

Hi all,

On Sun, Mar 05, 2000 at 02:05:45PM -0800, Eric G . Miller wrote:
> On Sun, Mar 05, 2000 at 09:11:37PM +0000, David Armstrong wrote:
> > Could anyone help a new guy compile GRASS 5b6
> >
> > running linux mandrake 7
[...]

I have It.....and I have no problem with compile......just....

> The line in the Makefile that's giving you grief is in the pre-install:
>
> ${ENV} ${MAKE_GMAKE_ENV} ${MAKE_POST_ENV} ${SHELL}
[...]

set the ENV variable to this: ENV =
and line: ${ENV} ${MAKE_GMAKE_ENV} ${MAKE_POST_ENV} ${SHELL}
rewrite to: ${MAKE_GMAKE_ENV}
                ${MAKE_POST_ENV}
                ${SHELL}

> It's calling the program "env" to modify the environment for
> compilation, and it's trying to source your /root/.bashrc. If it doesn't
> exist, just do "touch /root/.bashrc" to create an empty file.
Please check Makefile, if ${ENV} was expanded to "env" properly.
It fails on a few platforms (why?).

> Unfortunately, grass is still a little braindamaged in the
> compilation/installation. It's generally recommended to never compile
> things as root 'cause "Bad things can happen". I'd recommend giving
Oh! What are the problems here? Then we can try to fix them.

> It'd be better if GRASS's "make" or "make all" would just compile
> the binaries but not install them, then you could "su -c 'make
> install'". But, for various reasons, that's currently not possible.

We are working on this, it is a non-trivial task due to GRASS
programming history. Currently we are lucky that at least "auto-conf"
is working :slight_smile: Our plans are to restructure the GRASS sources
to small content-oriented packages (GRASS-Core, GRASS-basic, ...)
with GNU-style make/make install. I hope we manage soon but
any help would be appreciated. Please contact me on this if
you could support us.

Regards

Markus Neteler

        compile it and use it :slight_smile: ......
                    regards
                            Pavol Cvengros

PS: I have started rewrite of v.digit to Qt driven GUI enhanc.

On Mon, Mar 06, 2000 at 02:15:00PM +0100, Pavol Cvengros wrote:

PS: I have started rewrite of v.digit to Qt driven GUI enhanc.

Great.
BTW: Did you consider wxWindows or any other cross platform GUI?
It might have advantages in the long run.

  Bernhard
--
Free Software Projects and Consulting (intevation.net)
Association for a Free Informational Infrastructure (ffii.org)

I know there has been some answers given to the issue of compiling Grass, but why not use the binary version for linux? I installed Grass 5.0 Beta 6 on Linux Mandrake 7.0, and it is running well. Is there some advantage to compiling? If not, use the binary version.

David Armstrong wrote:

Could anyone help a new guy compile GRASS 5b6 running linux mandrake 7 having ran ./configure then make i get the following error :-root@localhost grass5.0beta]# make


Michael Pool, RPA
Anthropology/Geography Department
Austin Community College
mpool@austin.cc.tx.us

On Mon, Mar 06, 2000 at 02:27:56PM -0600, Michael Pool wrote:

    I know there has been some answers given to the issue of
    compiling Grass, but why not use the binary version for linux? I
    installed Grass 5.0 Beta 6 on Linux Mandrake 7.0, and it is
    running well. Is there some advantage to compiling? If not, use
    the binary version.

Well a bunch of possible reasons come to mind:

* Hacking around the source code of GRASS
* Using updated development versions from CVS.
* Nonstandard Configuration of the system

  Bernhard
--
Free Software Projects and Consulting (intevation.net)
Association for a Free Informational Infrastructure (ffii.org)