[MacPorts] #56908: gdal @2.3.1: error: thread-local storage is not supported for the current target

[MacPorts]

#56908: gdal @2.3.1: error: thread-local storage is not supported for the current
target
-----------------------------------------+----------------------
 Reporter:  ryandesign                   |      Owner:  Veence
     Type:  defect                       |     Status:  assigned
 Priority:  Normal                       |  Milestone:
Component:  ports                        |    Version:
 Keywords:  mavericks yosemite haspatch  |       Port:  gdal
-----------------------------------------+----------------------
 gdal @2.3.1 fails to build
 [https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/62190/steps
 /install-port/logs/stdio on OS X 10.9 with Xcode 6.2] and
 [https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/61105/steps
 /install-port/logs/stdio on OS X 10.10 with Xcode 7.2.1] when using
 Xcode's clang, with:

 {{{
 ersdataset.cpp:612:12: error: thread-local storage is not supported for
 the current target
     static thread_local int nRecLevel = 0;
            ^
 ersdataset.cpp:987:16: error: thread-local storage is not supported for
 the current target
         static thread_local int nRecLevel = 0;
                ^
 2 errors generated.
 }}}

 I wonder if using a newer compiler from MacPorts would fix that. Apple
 didn't include thread local storage in Xcode's clang until Xcode 8, but
 open-source clang got that feature much earlier.

 It builds fine on OS X 10.11 and later using Xcode clang, and on Mac OS X
 10.7 and 10.8 using MacPorts clang 5.0 (which happens because the cxx11
 1.1 portgroup blacklists `{clang < 500}`).

 I suggest adding `compiler.blacklist-append {clang < 800}` to the
 Portfile.

-- 
Ticket URL: <https://trac.macports.org/ticket/56908>
MacPorts <https://www.macports.org/>
Ports system for macOS