Well, if the errors are only about documentation, I can live with them.
So I went on to create the installation package. I had to manually download
PackageMaker from Apple (Late 2012 version).
After creating and installing the package, when I run it, I get the startup
dialog (choose location
Just to update my last message, although wxgui won't start, GRASS will
start in text mode.
In python I tried the import statment:
from grass.pygrass import messages
Traceback (most recent call last):
File stdin, line 1, in module
File
I believe what happens is it compiles with links to where it will be installed,
but during documentation creation it uses DYLD_LIBRARY_PATH to make it look in
the build dir. This is what is not working.
On Jul 23, 2015, at 7:40 PM, Carlos Grohmann carlos.grohm...@gmail.com wrote:
On thing
On thing that I found weird id this:
dyld: Library not loaded:
/Applications/GRASS-7.0.app/Contents/MacOS/lib/libgrass_gis.7.0.1RC2.dylib
Referenced from:
/Users/guano/Documents/installs/release_20150720_grass_7_0_1RC2/dist.x86_64-apple-darwin15.0.0/bin/g.parser
Reason: image not found
Hi
I'm trying to compile GRASS7 on OSX 10.11 Beta, but I'm stuck with GDAL.
I'm using Kyngesburye's frameworks, and I have gdal-config in my PATH as
export PATH=/Library/Frameworks/GDAL.framework/Programs:$PATH
this minimum example of configure fails:
export MACOSX_DEPLOYMENT_TARGET=10.10
The GDAL detection has a problem with framework link flags. There is an
alternate gdal-config at
/Library/Frameworks/GDAL.framework/unix/bin/gdal-config
that returns library link flags that configure likes better.
On Jul 22, 2015, at 12:36 PM, Carlos Grohmann carlos.grohm...@gmail.com wrote:
Thanks, William.
That worked, at least for the configure part. Now the problem is at
compiling. At the end of make, I get a ton of errors in modules:
Errors in:
/Users/guano/Documents/installs/grass70_release/scripts/d.correlate
I don't see any GDAL problem there. It looks like DYLD_LIBRARY_PATH is not
working when running the modules to create documentation.
I don't know where to go from there.
On Jul 22, 2015, at 8:18 PM, Carlos Grohmann carlos.grohm...@gmail.com wrote:
Thanks, William.
That worked, at least
