[MacPorts] #65532: isl @0.25: builds failing for 10.13: call to unavailable member function 'value' (was: isl @0.25 build failure on 10.13 -- call to unavailable member function 'value': introduced in macOS 10.14)

[MacPorts]

#65532: isl @0.25: builds failing for 10.13: call to unavailable member function
'value'
-------------------------+---------------------------------
  Reporter:  dyne2meter  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.2
Resolution:              |   Keywords:
      Port:  isl         |
-------------------------+---------------------------------
Changes (by mascguy):

 * cc: mascguy (added)


Comment:

 Builds also failing for 10.7, albeit with a difference issue:

 {{{
 libtool: link: /opt/local/bin/clang++-mp-14 -std=c++11 -std=gnu++17 -pipe
 -Os -stdlib=libc++ -arch x86_64 -Wl,-headerpad_max_install_names -arch
 x86_64 -o .libs/isl_test_cpp17-checked isl_test_cpp17-checked.o
 -L/opt/local/lib ./.libs/libisl.dylib /opt/local/lib/libgmp.dylib
 Undefined symbols for architecture x86_64:
   "std::bad_optional_access::~bad_optional_access()", referenced from:
       std::__1::__throw_bad_optional_access() in isl_test_cpp17-checked.o
   "typeinfo for std::bad_optional_access", referenced from:
       std::__1::__throw_bad_optional_access() in isl_test_cpp17-checked.o
   "vtable for std::bad_optional_access", referenced from:
       std::__1::__throw_bad_optional_access() in isl_test_cpp17-checked.o
   NOTE: a missing vtable usually means the first non-inline virtual member
 function has no definition.
 ld: symbol(s) not found for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see
 invocation)
 make[2]: *** [isl_test_cpp17-checked] Error 1
 }}}

 For the 10.13 case, the issue can potentially be solved by expanding the
 Clang blacklist. But that won't help for the 10.7 case, since we're
 already using `mp-clang-14` in that case.

 Thoughts relative to the best approach to fixing this...?

-- 
Ticket URL: <https://trac.macports.org/ticket/65532#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS