Re: [GRASS-dev] wx.metadata ready for testing

On 07-10-15 22:29, Martin Landa wrote: Hi, 2015-10-07 12:30 GMT+02:00 Paulo van Breugel : I tried fresh installation (trunk) in installed to /usr/local. I cannot reproduce any of reported errors. Please send me related environmental variables: env | grep GIS env |

Re: [GRASS-dev] [GRASS GIS] #2750: LZ4 when writing raster rows; better than double I/O bound r.mapcalc speed

#2750: LZ4 when writing raster rows; better than double I/O bound r.mapcalc speed --+--- Reporter: sprice | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.1.0 Component:

[GRASS-dev] r.stream.watersheds & r.stream.variables add-on

Hi, we have developed 2 grass add-on "r.stream.watersheds" that performs (for each single grid cell of a stream network) the sub-watershed delineation based on the drainage direction and a gridded stream network "r.stream.variables" which will calculate and relate the upstream-contributing

[GRASS-dev] GRASS will not not find laslib

With a lot of effort and some help, I've rebuilt liblas with new GDAL. Now GRASS will not find liblas with the same configuration script that I've used before. Here it is: ./configure --with-macosx-sdk=/Developer/SDKs/MacOSX10.7.sdk --with-freetype

Re: [GRASS-dev] GRASS will not not find laslib

On Thu, Oct 8, 2015 at 5:24 PM, Michael Barton wrote: > With a lot of effort and some help, I've rebuilt liblas with new GDAL. Now > GRASS will not find liblas with the same configuration script that I've > used before. Here it is: > Was there some specific trick that

Re: [GRASS-dev] GRASS will not not find laslib

I could try that. I originally build liblas with dual architecture. But current OS X and boost choke on dual architecture. So I built it 64 bit. I assumed that that means I needed to build laslib also only 64 bit. If you think I can get away with dual architecture there, I can give it a try.

Re: [GRASS-dev] GRASS will not not find laslib

On Thu, Oct 8, 2015 at 6:26 PM, Michael Barton wrote: > I built boost with both bjam and b2 for i86_64. Here are the setups I > used: > > cd /Users/Shared/grass_dev/boost_1_59_0 > edit > /Users/cmbarton/grass_source/LAS/boost_1_59_0/tools/build/src/tools/darwin.jam > to

Re: [GRASS-dev] GRASS will not not find laslib

I built boost with both bjam and b2 for i86_64. Here are the setups I used: cd /Users/Shared/grass_dev/boost_1_59_0 edit /Users/cmbarton/grass_source/LAS/boost_1_59_0/tools/build/src/tools/darwin.jam to delete -gdwarf-2 ] export CXXFLAGS=-stdlib=libstdc++ ./bootstrap.sh

Re: [GRASS-dev] GRASS will not not find laslib

On Thu, Oct 8, 2015 at 7:33 PM, Michael Barton wrote: > I could try that. I originally build liblas with dual architecture. But > current OS X and boost choke on dual architecture. So I built it 64 bit. I > assumed that that means I needed to build laslib also only 64

[GRASS-dev] WARNING TO MAC USERS - WAIT UPDATING TO EL CAPITAN (OS X 10.11)

I've had reports of GRASS not running for users updating to El Capitan. There is a possible workaround, but it is cumbersome and not guaranteed to work. I recommend that you do wait to update while we try to solve this. I've also heard that El Capitan breaks R. Michael C.

Re: [GRASS-dev] GRASS will not not find laslib

On Thu, Oct 8, 2015 at 8:02 PM, Michael Barton wrote: > Nope. > > It starts to launch and gets to the start up screen, but has this error: > > Starting GRASS GIS... > Unable to import pyGRASS: >

Re: [GRASS-dev] GRASS will not not find laslib

The first thing is to compile boost with 2 architectures. That might solve the whole thing Michael Barton School of Human Evolution Change Center for Social Dynamics & Complexity Arizona State University ...Sent from my iPad On Oct 8, 2015, at 5:14 PM, Anna Petrášová

Re: [GRASS-dev] GRASS will not not find laslib

Nope. It starts to launch and gets to the start up screen, but has this error: Starting GRASS GIS... Unable to import pyGRASS: dlopen(/Users/cmbarton/grass_source/release_20150730_grass_7_0_1/macosx/dist/GRASS-7.0.app/Contents/MacOS/lib/libgrass_gis.7.0.1.dylib, 10): no suitable image found.

Re: [GRASS-dev] GRASS will not not find laslib

If I configure only for x86_64, it configures. I'm building now to see if it actually makes and runs. I'm concerned most about wxPython 2.8.12, which is still 32 bit. We'll see if the workaround that William came up with still works. Michael C. Michael Barton Director,

Re: [GRASS-dev] GRASS will not not find laslib

I got errors in... Errors in: /Users/cmbarton/grass_source/release_20150730_grass_7_0_1/scripts/v.what.strds /Users/cmbarton/grass_source/release_20150730_grass_7_0_1/temporal/t.create /Users/cmbarton/grass_source/release_20150730_grass_7_0_1/temporal/t.support

Re: [GRASS-dev] GRASS will not not find laslib

Nope. ld: symbol(s) not found for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [bin/Release/liblas.2.3.0.dylib] Error 1 make[1]: *** [src/CMakeFiles/las.dir/all] Error 2 make: *** [all] Error 2 C. Michael

Re: [GRASS-dev] GRASS will not not find laslib

Michael Barton wrote: > But wximgview would not compile with what appears to be a 32/64 bit conflict wximgview is (AFAIK) the only program which links against the wxWidgets libraries. But it has been obsoleted by wxpyimgview (a wxPython version), so I see no reason not to simply remove it (and