Car trouble, can't get into town 73 & best regards de K7AAY °|||||||° [email protected] 503-227-8539
On Thu, Jul 18, 2019, 09:46 <[email protected]> wrote: > Send PLUG mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.pdxlinux.org/mailman/listinfo/plug > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of PLUG digest..." > > > Today's Topics: > > 1. Re: Copying to new host, excluding a directory tree (Rich Shepard) > 2. Re: Copying to new host, excluding a directory tree > (David Bridges) > 3. C program build error in Makefile (Rich Shepard) > 4. Re: C program build error in Makefile (Rich Shepard) > 5. Re: Copying to new host, excluding a directory tree > ([email protected]) > 6. Re: C program build error in Makefile > ([email protected]) > 7. Re: C program build error in Makefile (Rich Shepard) > 8. Symlink syntax refresher (Rich Shepard) > 9. Re: C program build error in Makefile > ([email protected]) > 10. Re: C program build error in Makefile (Rich Shepard) > 11. Re: Symlink syntax refresher ([email protected]) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 18 Jul 2019 06:20:16 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] Copying to new host, excluding a directory tree > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On Wed, 17 Jul 2019, [email protected] wrote: > > > ... adding to this ... > > you can use --exclude dirOrFileName multiple times - it will form a list > > > > in this particular case: --exclude data would work too, but it would > exclude all > > other directories and files called data inside your recursive directory. > This > > can be handy, or not, depending on the situation. > > Tohas, > > In ~/ there's only one data/ directory. Perhaps I'm mis-understanding. > > Thanks, > > Rich > > > ------------------------------ > > Message: 2 > Date: Thu, 18 Jul 2019 08:37:18 -0500 > From: David Bridges <[email protected]> > To: [email protected] > Subject: Re: [PLUG] Copying to new host, excluding a directory tree > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > Exclusions can also be added to a file one per line, When using a file > listing excluded files/directories you would add something like the > following to your command line. > > --exclude-from='/some/directory/excludes.txt' > > -- > David > > On Wed, 2019-07-17 at 23:20 -0400, [email protected] wrote: > > ... adding to this ... > > you can use --exclude dirOrFileName multiple times - it will form a > > list > > > > in this particular case: --exclude data would work too, but it would > > exclude all > > other directories and files called data inside your recursive > > directory. This > > can be handy, or not, depending on the situation. > > > > -T > > > > On Wed, 2019-07-17 at 16:08 -0700, Rich Shepard wrote: > > > On Wed, 17 Jul 2019, Ben Koenig wrote: > > > > > > > --exclude ~/data/ > > > > > > Thanks, Ben. I missed that option when I read the rsync man page. > > > > > > Regards, > > > > > > Rich > > > _______________________________________________ > > > PLUG mailing list > > > [email protected] > > > http://lists.pdxlinux.org/mailman/listinfo/plug > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > ------------------------------ > > Message: 3 > Date: Thu, 18 Jul 2019 07:22:24 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: [email protected] > Subject: [PLUG] C program build error in Makefile > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > It's been more than a dozen years since I last coded in C and built a > Makefile. Depending on project needs I use the GRASS GIS for terrain and > hydrologic modeling, and I need it now. Since the late 1990s I've built the > latest development version from code checked out from the subversion > repository. A couple of weeks ago the devs completed the migration from SVN > to GIT using a github repo. > > I cloned the repository and tried building the most current version. It > failed (see below), as did prior versions and the SlackBuilds.org version. > Same error on each of three hosts: one 32-bit and two 64-bit. I need help > in > learning why this build error occurs (and not apparently on other > distributions used by others) and in fixing it. > > ----- > Finished compilation: Fri Jul 12 07:16:54 PDT 2019 > Makefile:57: recipe for target 'default' failed > make: *** [default] Error 1 > > Looking at line 57 in Makefile I see: > > default: > @echo "GRASS GIS > $(GRASS_VERSION_MAJOR).$(GRASS_VERSION_MINOR).$(GR > > $(ERRORLOG) > @echo "--------------------------------------------------" >> > $(ERR > @echo "Started compilation: `date`" >> > $(ERR > @echo "--" >> > $(ERR > @echo "Errors in:" >> > $(ERR > -$(CHMOD) 755 install-sh > $(MAKE) subdirs > $(MAKE) $(FILES_DST) > $(MAKE) manifests > @if [ `wc -l < "$(ERRORLOG)"` -gt 5 ] ; then \ > echo "--" >> $(ERRORLOG) ; \ > ... > ----- > > I need help identifying why the Makefile is not finding the recipe on my > systems. Can send Makefile and other information off the mail list; the > Makefile is 4k in length. > > TIA, > > Rich > > > ------------------------------ > > Message: 4 > Date: Thu, 18 Jul 2019 07:59:14 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] C program build error in Makefile > Message-ID: > <[email protected]> > Content-Type: text/plain; format=flowed; charset=US-ASCII > > On Thu, 18 Jul 2019, Rich Shepard wrote: > > > I cloned the repository and tried building the most current version. It > > failed (see below), as did prior versions and the SlackBuilds.org > version. > > Same error on each of three hosts: one 32-bit and two 64-bit. I need > help in > > learning why this build error occurs (and not apparently on other > > distributions used by others) and in fixing it. > > When I look at the end of the build process (I tee'd the output to a text > file) I see that almost no file built. So, now I know where to start > looking. > > Rich > > > ------------------------------ > > Message: 5 > Date: Thu, 18 Jul 2019 11:00:00 -0400 > From: [email protected] > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] Copying to new host, excluding a directory tree > Message-ID: <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > What I meant to say about using --exclude ~/data > is that - if you would, hypothetically, use '--exclude data' it would > exclude > ~/data and any other directory or file called data - including the content > of > any said 'data' directory. > > BTW: Everybody probably knows, but ~/data will be expanded to $HOME/data - > it is > just an alias for users home, not an file name. If you would to change > user's > home dir to /users/$USER, for example, in the /etc/passwd file '~' would > expand > to correct directory the next time you login. And, if some user dirs are in > /home/$USER, others in /users/$USER, others in /abc/$USERS - '~' will > expand to > correct user's home dir, even when you refer to them as ~userName. > > -T > > On Thu, 2019-07-18 at 06:20 -0700, Rich Shepard wrote: > > On Wed, 17 Jul 2019, [email protected] wrote: > > > > > ... adding to this ... > > > you can use --exclude dirOrFileName multiple times - it will form a > list > > > > > > in this particular case: --exclude data would work too, but it would > exclude > > > all > > > other directories and files called data inside your recursive > directory. > > > This > > > can be handy, or not, depending on the situation. > > > > Tohas, > > > > In ~/ there's only one data/ directory. Perhaps I'm mis-understanding. > > > > Thanks, > > > > Rich > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > ------------------------------ > > Message: 6 > Date: Thu, 18 Jul 2019 11:04:44 -0400 > From: [email protected] > To: [email protected] > Subject: Re: [PLUG] C program build error in Makefile > Message-ID: <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > Did you run .configure with correct --prefix for your system? > Does running ./configure gives you a hint? > > -T > > On Thu, 2019-07-18 at 07:22 -0700, Rich Shepard wrote: > > It's been more than a dozen years since I last coded in C and built a > > Makefile. Depending on project needs I use the GRASS GIS for terrain and > > hydrologic modeling, and I need it now. Since the late 1990s I've built > the > > latest development version from code checked out from the subversion > > repository. A couple of weeks ago the devs completed the migration from > SVN > > to GIT using a github repo. > > > > I cloned the repository and tried building the most current version. It > > failed (see below), as did prior versions and the SlackBuilds.org > version. > > Same error on each of three hosts: one 32-bit and two 64-bit. I need > help in > > learning why this build error occurs (and not apparently on other > > distributions used by others) and in fixing it. > > > > ----- > > Finished compilation: Fri Jul 12 07:16:54 PDT 2019 > > Makefile:57: recipe for target 'default' failed > > make: *** [default] Error 1 > > > > Looking at line 57 in Makefile I see: > > > > default: > > @echo "GRASS GIS > $(GRASS_VERSION_MAJOR).$(GRASS_VERSION_MINOR).$(GR > > > $(ERRORLOG) > > @echo "--------------------------------------------------" >> > $(ERR > > @echo "Started compilation: `date`" >> > $(ERR > > @echo "--" >> > $(ERR > > @echo "Errors in:" >> > $(ERR > > -$(CHMOD) 755 install-sh > > $(MAKE) subdirs > > $(MAKE) $(FILES_DST) > > $(MAKE) manifests > > @if [ `wc -l < "$(ERRORLOG)"` -gt 5 ] ; then \ > > echo "--" >> $(ERRORLOG) ; \ > > ... > > ----- > > > > I need help identifying why the Makefile is not finding the recipe on my > > systems. Can send Makefile and other information off the mail list; the > > Makefile is 4k in length. > > > > TIA, > > > > Rich > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > ------------------------------ > > Message: 7 > Date: Thu, 18 Jul 2019 08:19:04 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] C program build error in Makefile > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On Thu, 18 Jul 2019, [email protected] wrote: > > > Did you run .configure with correct --prefix for your system? > > Does running ./configure gives you a hint? > > Tomas, > > Yes. And no. It's the same configure file I've used for years. I have the > 2M > build output and I'll start going through that. There are > 200 files that > did not build. > > Thanks, > > Rich > > > ------------------------------ > > Message: 8 > Date: Thu, 18 Jul 2019 09:11:08 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: [email protected] > Subject: [PLUG] Symlink syntax refresher > Message-ID: > <[email protected]> > Content-Type: text/plain; format=flowed; charset=US-ASCII > > Found the problem building the grass source. It's look for > libgeos-3.7.0.so > and my systems have libgeos-3.7.2 installed. On this system the libraries > are: > > $ ll /usr/lib/libgeos* > -rwxr-xr-x 1 root root 1689316 May 20 08:55 /usr/lib/libgeos-3.7.2.so* > -rwxr-xr-x 1 root root 931 May 20 08:55 /usr/lib/libgeos.la* > lrwxrwxrwx 1 root root 16 May 20 08:56 /usr/lib/libgeos.so -> > libgeos-3.7.2.so* > > (it is /usr/lib64/ on those hosts). > > I need to make a symbolic link so grass sees libgeos-3.7.0.so and it's > been > a while since I've run 'ln -s ...'. The man page still doesn't clearly tell > me which is the target and which is the link name. > > I _think_ what I need is libgeos-3.7.0.so -> libgeos-3.7.2.so and want to > confirm this before I make a mistake. > > TIA, > > Rich > > > ------------------------------ > > Message: 9 > Date: Thu, 18 Jul 2019 12:38:16 -0400 > From: [email protected] > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] C program build error in Makefile > Message-ID: <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > Did you execute: ./configure > before running make? > > Did it find all dependencies? > Or is it different build system/process ... > > Tomas > > On Thu, 2019-07-18 at 08:19 -0700, Rich Shepard wrote: > > On Thu, 18 Jul 2019, [email protected] wrote: > > > > > Did you run .configure with correct --prefix for your system? > > > Does running ./configure gives you a hint? > > > > Tomas, > > > > Yes. And no. It's the same configure file I've used for years. I have > the 2M > > build output and I'll start going through that. There are > 200 files > that > > did not build. > > > > Thanks, > > > > Rich > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > ------------------------------ > > Message: 10 > Date: Thu, 18 Jul 2019 09:42:12 -0700 (PDT) > From: Rich Shepard <[email protected]> > To: Portland Linux/Unix Group <[email protected]> > Subject: Re: [PLUG] C program build error in Makefile > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On Thu, 18 Jul 2019, [email protected] wrote: > > > Did you execute: ./configure > > before running make? > > Tomas, > > I read in the configuration file. So, yes. > > And the issue is the Makefile looking for a specific libgeos version > (3.7.0) > while 3.7.2 is installed. I'm rebuilding the chain proj -> geos -> gdal. > > Thanks, > > Rich > > > ------------------------------ > > Message: 11 > Date: Thu, 18 Jul 2019 09:45:20 -0700 (PDT) > From: [email protected] > To: Rich Shepard <[email protected]>, Portland Linux/Unix Group > <[email protected]> > Subject: Re: [PLUG] Symlink syntax refresher > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > > You want to let ldconfig manage those files. > > Instead of messing with your system libraries you might try telling grass > it's okay use libgeos-3.7.2. If it's not happy with that you might have > mess around with configure options, or worst. > > > On Thu, 18 Jul 2019, Rich Shepard wrote: > > > Found the problem building the grass source. It's look for > libgeos-3.7.0.so > > and my systems have libgeos-3.7.2 installed. On this system the libraries > > are: > > > > $ ll /usr/lib/libgeos* > > -rwxr-xr-x 1 root root 1689316 May 20 08:55 /usr/lib/libgeos-3.7.2.so* > > -rwxr-xr-x 1 root root 931 May 20 08:55 /usr/lib/libgeos.la* > > lrwxrwxrwx 1 root root 16 May 20 08:56 /usr/lib/libgeos.so -> > > libgeos-3.7.2.so* > > > > (it is /usr/lib64/ on those hosts). > > > > I need to make a symbolic link so grass sees libgeos-3.7.0.so and it's > been > > a while since I've run 'ln -s ...'. The man page still doesn't clearly > tell > > me which is the target and which is the link name. > > > > I _think_ what I need is libgeos-3.7.0.so -> libgeos-3.7.2.so and want > to > > confirm this before I make a mistake. > > > > TIA, > > > > Rich > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > > ------------------------------ > > _______________________________________________ > PLUG: http://pdxlinux.org > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > > > End of PLUG Digest, Vol 178, Issue 25 > ************************************* > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
