[GRASS-dev] Gaining write privileges to usr/local and subdirectories

Paul Schrum paul.schrum at gmail.com
Fri May 26 12:43:39 PDT 2017


Helmut,

My GSoC mentor (Vashek) just now helped me work through this.

I turns out that in my newbie confusion I was calling ./configure from
./configure, so it wasn't an endless loop, it was an endless recursion.

Thank you very much for your help.

- Paul

On Thu, May 25, 2017 at 3:58 AM, Helmut Kudrnovsky <hellik at web.de> wrote:

> Paul Schrum wrote
> > Going by
> > https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#GRASS_GIS
> and
> > focusing on GRASS GIS 7 trunk:
> >
> > 1. Last week I did
> >
> > svn co https://svn.osgeo.org/grass/grass/trunk grass7_trunk
> >
> > On a directory under my ownership.
> >
> > 2.  Today in that same directory I ran
> > svn up
> >
> > 3. I ran the large statement which begins with
> >
> > CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
> >
> > Here is where the problem is.  It seems to go into an infinite loop.*
> >
> >
> > Also note that when I run it from /usr/local/src/grass7_trunk -- where I
> > was running it when I started this thread -- it succeeded.  It did not go
> > into the infinite loop.
> >
> > * When the process starts, the first few lines read:
> > ./configure: 229: ./configure: Cannot fork
> > ./configure: 300: ./configure: Cannot fork
> > ./configure: 300: ./configure: Cannot fork
> >
> > There is a lot more I could send but have not, including the last lines
> > before it restarts at the top of the loop.
> >
> > Please let me know what more information to five you or what changes I
> > should make.
> >
> > - Paul
> >
> >
> >
> > On Tue, May 23, 2017 at 11:44 AM, Helmut Kudrnovsky <
>
> > hellik@
>
> > > wrote:
> >
> >> Paul Schrum wrote
> >> > I started off trying to build it in a directory under my home
> directory
> >> > using the instructions here
> >> > <https://grasswiki.osgeo.org/wiki/Compile_and_Install_
> >> Ubuntu#Dependencies>,
> >> > but I could not get it to build.  The only part of those instructions
> >> that
> >> > I was not following were the path.  So I started using the paths
> >> indicated
> >> > in those instructions and then it would build.  That is why my copy of
> >> the
> >> > source is where it is.
> >> >
> >> > Based on yall's comments, I now think it was something other than the
> >> path
> >> > where I was storing the source code, but I have no idea what.
> >>
> >> please post here your steps and error (?)/warning(?) messages of
> >> compiling.
> >>
> >>
> >>
> >>
> >> -----
> >> best regards
> >> Helmut
> >> --
> >> View this message in context: http://osgeo-org.1560.x6.
> >> nabble.com/Gaining-write-privileges-to-usr-local-and-subdirectories-
> >> tp5321487p5321504.html
> >> Sent from the Grass - Dev mailing list archive at Nabble.com.
> >> _______________________________________________
> >> grass-dev mailing list
> >>
>
> > grass-dev at .osgeo
>
> >> https://lists.osgeo.org/mailman/listinfo/grass-dev
> >>
> >
> > _______________________________________________
> > grass-dev mailing list
>
> > grass-dev at .osgeo
>
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>
> no configure/compiling guru here on my side, googling
>
> e.g. configure + "Cannot fork"
>
> may show some issues with too many processes in your computer.
>
> as your issue has changed from "Gaining write privileges to usr/local and
> subdirectories" to some other, maybe changing the subject line of the
> thread
> to get more devs involved.
>
>
>
>
>
> -----
> best regards
> Helmut
> --
> View this message in context: http://osgeo-org.1560.x6.
> nabble.com/Gaining-write-privileges-to-usr-local-and-subdirectories-
> tp5321487p5321772.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170526/3e5a6695/attachment.html>


More information about the grass-dev mailing list