Glad to hear it!
73 & best regards de K7AAY °|||° j...@503bartley.com 503-227-8539
On Thu, Jul 18, 2019, 17:12 John Jason Jordan wrote:
> On Thu, 18 Jul 2019 11:39:46 -0700
> "John Bartley K7AAY j...@503bartley.com" dijo:
>
> >Car trouble, can't get into town
>
> No problem. Stephen, Conor
On Thu, 18 Jul 2019 11:39:46 -0700
"John Bartley K7AAY j...@503bartley.com" dijo:
>Car trouble, can't get into town
No problem. Stephen, Conor and I handled it, although we missed your
excellent sales skills. We should have several newcomers to upcoming
events.
__
Ah, very good.
On Thu, Jul 18, 2019 at 4:06 PM Dick Steffens wrote:
> On 7/18/19 4:03 PM, elcaseti . wrote:
> > I'm probably stating the obvious here, but I hope both screens are from
> the
> > same laptop model. Otherwise, you're talking about a whole different
> > league of a procedure.
>
> I
On 7/18/19 4:03 PM, elcaseti . wrote:
I'm probably stating the obvious here, but I hope both screens are from the
same laptop model. Otherwise, you're talking about a whole different
league of a procedure.
I brought this up a couple of months ago on this list and heard that
they should be com
I'm probably stating the obvious here, but I hope both screens are from the
same laptop model. Otherwise, you're talking about a whole different
league of a procedure.
On Tue, Jul 16, 2019 at 9:38 PM John Jason Jordan wrote:
> On Tue, 16 Jul 2019 16:54:54 -0700
> Ben Koenig dijo:
>
> >Or maybe
On Thu, 18 Jul 2019, Michael C Robinson wrote:
I wrote a simple script that greps an mbox for the subjects of every
email in it. Problem is, a lot of these subjects are htmlized or
something similar and are not plain text. Any suggestions on
alternative approaches to extracting the subjects
Car trouble, can't get into town
73 & best regards de K7AAY °|||° j...@503bartley.com 503-227-8539
On Thu, Jul 18, 2019, 09:46 wrote:
> Send PLUG mailing list submissions to
> plug@pdxlinux.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.pdxl
On Thu, 18 Jul 2019, tomas.kuchta.li...@gmail.com wrote:
Did you run .configure with correct --prefix for your system?
Does running ./configure gives you a hint?
The problem was the need to re-compile and re-install the proj -> geos ->
gdal stack, the run ldconfig. Grass built to completion an
On Thu, 18 Jul 2019, tomas.kuchta.li...@gmail.com wrote:
Not the response I expected - maybe just a wording.
Just to be sure:
My comment was about executing not reading ./configure prior to running make.
./configure command scans your system, reports dependencies and generates config
fil
Not the response I expected - maybe just a wording.
Just to be sure:
My comment was about executing not reading ./configure prior to running make.
./configure command scans your system, reports dependencies and generates config
files specific to your build.
If you did not run './configure' s
On Thu, 18 Jul 2019, bro...@netgate.net wrote:
You want to let ldconfig manage those files.
Ah, yes. Forgot all about ldconfig.
Thanks,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
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
On Thu, 18 Jul 2019, tomas.kuchta.li...@gmail.com 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 ->
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, tomas.kuchta.li...@gmail.com wrote:
>
> > Did you run .configure with correct --prefix
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
On Thu, 18 Jul 2019, tomas.kuchta.li...@gmail.com 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.
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
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 $HOM
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 o
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
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, tomas.kuchta.li...@gmail.com wrote
On Wed, 17 Jul 2019, tomas.kuchta.li...@gmail.com 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
22 matches
Mail list logo
