[gdal-dev] "symbol(s) not found for architecture x86_64" when compiling GDAL 2.1.0 on Mac OS X

Lucian Plesea LPlesea at esri.com
Sun Feb 12 13:06:49 PST 2017

MRF depends on JPEG, PNG, zlib and TIFF.  Since those are always available as GDAL internal, it doesn’t makes sense to change the code to make it work without some of them.  It would only create seldom used configurations that would have to be tested and maintained.
Turning MRF off if any of the dependencies are missing would be safer and simpler.


From: Even Rouault [mailto:even.rouault at spatialys.com]
Sent: Sunday, February 12, 2017 11:38 AM
To: gdal-dev at lists.osgeo.org
Cc: Michal Migurski; Lucian Plesea
Subject: Re: [gdal-dev] "symbol(s) not found for architecture x86_64" when compiling GDAL 2.1.0 on Mac OS X

On dimanche 12 février 2017 10:52:59 CET Michal Migurski wrote:

> Hi,


> I’ve recently switched to a new laptop, and I’m attempting to compile GDAL.

> I have libpng and jpeg in /urs/local via a fresh installation of Homebrew,

> and I am attempting to follow instructions for minimal drivers. This has

> worked without incident for me in the past, but I’m running into a problem

> I’ve not seen before.


You need to disable the MRF driver as well since it needs libpng and libjpeg. Unfortunetely I just discovered that the intended --without-mrf option didn't work because of a typo. I fixed this by a simple patch in https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_gdal_ticket_6811&d=DwIGaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=0orhATy81rhG89NwPqBqSPUWjOvyYU8QxFh5_mt-XF8&m=zspmUIO7S_ZVn-9UgO9SW5klMbpNfrJggIKRaHNbkZQ&s=CkAIea7yNc6i_N2r7C8oLBtDRo9vSrZf5jRj712nkwE&e=  that you can apply.


wouldn't it make sense to either be able to build MRF without PNG and/or JPEG support, or if that doesn't make sense automatically disable MRF when they are not available ?



Spatialys - Geospatial professional services

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170212/9624c506/attachment.html>

More information about the gdal-dev mailing list