[MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path

[MacPorts]

#66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for
'macosx10.11' using --show-sdk-path
-----------------------------------+---------------------------------
  Reporter:  thetrial              |      Owner:  MarcusCalhoun-Lopez
      Type:  defect                |     Status:  assigned
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.8.0
Resolution:                        |   Keywords:  elcapitan legacy-os
      Port:  qt511-qtimageformats  |
-----------------------------------+---------------------------------

Comment (by kencu):

 It looks like adding the {{{DEVELOPER_DIR=${configure.developer_dir}}}
 part was the culprit.

 On a system that does not have MacOSX10.11.sdk in either SDKs folder, we
 see this:

 {{{
 $ ls /Library/Developer/CommandLineTools/SDKs
 MacOSX.sdk      MacOSX10.12.sdk

 $ ls
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
 MacOSX.sdk      MacOSX10.12.sdk

 $ /usr/bin/xcrun --sdk macosx10.11 --find ld
 xcodebuild: error: SDK "macosx10.11" cannot be located.
 xcrun: error: unable to find utility "ld", not a developer tool or in PATH

 DEVELOPER_DIR=/Library/Developer/CommandLineTools /usr/bin/xcrun --sdk
 macosx10.11 --find ld
 /Library/Developer/CommandLineTools/usr/bin/ld

 }}}


 We want to know if the MacOSX10.11.sdk exists, and adding the
 DEVELOPER_DIR part makes the test succeed in finding "ld" even if the SDK
 is not there.

 So we have to remove that from everywhere it was added, and we should be
 good.

 and that initially seems to work:

 {{{
 DEBUG: qt511 Portfile: the initial SDK value is: macosx10.11
 DEBUG: qt511 Portfile: testing for system-specific SDK:
 DEBUG: qt511 Portfile: system-specific SDK was not found, looking for
 generic SDK.
 DEBUG: qt511-qtbase: using generic macosx SDK as macosx10.11 was not found
 DEBUG: qt511 Portfile: the final SDK value is: macosx
 }}}

 however it comes around again for testing using the block of code in the
 qmake5 PortGroup, and that now fails to work properly, for no good reason
 I can see at present:

 {{{
 DEBUG: qmake5 Portfile: the initial SDK value is: macosx10.11
 DEBUG: qmake5 Portfile: testing for system-specific SDK macosx10.11:
 DEBUG: qmake5 Portfile: system-specific SDK was found.
 DEBUG: qmake5 Portfile: the final SDK value is: macosx10.11
 }}}

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