[MacPorts] #62226: osxfuse fails to build on Big Sur: Assertion 'common_is_variable DEFAULT_SDK_11_1_ARCHITECURES' failed

[MacPorts]

#62226: osxfuse fails to build on Big Sur: Assertion 'common_is_variable
DEFAULT_SDK_11_1_ARCHITECURES' failed
----------------------+--------------------
  Reporter:  islaeh   |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.6.4
Resolution:           |   Keywords:
      Port:  osxfuse  |
----------------------+--------------------

Comment (by DanielSmedegaardBuus):

 Alright, I used my immaculate braining skills to do some digging. It
 looked like the build was being configured with the correct info about the
 system, i.e. SDK 12.0 and Xcode 13.1 etc., but then there's a list of SDK
 compiler configs to work with, up to SDK 10.14, but then none for SDKs
 after that.

 So, I grepped the source code dir,

 `grep -R DEFAULT_SDK_10_9_COMPILER
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_fuse_osxfuse/osxfuse/work
 /osxfuse-osxfuse-48bc246/`,

 and found the

 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_fuse_osxfuse/osxfuse/work
 /osxfuse-osxfuse-48bc246/build.d/defaults.sh`

 file. In that, I added

 {{{
 declare -ra DEFAULT_SDK_12_0_ARCHITECURES=("x86_64")
 declare -r  DEFAULT_SDK_12_0_COMPILER="com.apple.compilers.llvm.clang.1_0"
 }}}

 and added 12.0 to the list here:
 {{{
 declare -ra DEFAULT_SDK_SUPPORTED=("10.5" "10.6" "10.7" "10.8" "10.9"
 "10.10" "10.11" "10.12" "10.13" "10.14" "12.0")
 }}}

 This stops the aforementioned error, as the build script now has those
 variables with compiler and SDK info to work with (`DEFAULT_SDK_12_0_*`),
 but it still fails to build (attaching that log as well).

 Makes me wonder... I'm thinking this cannot have been broken on 10.15,
 11.x for two years with no-one noticing? I wasn't on Big Sur or whatever
 10.15 was called, but I'm wondering if whatever fix was done (if any) was
 to hardwire the build process for 10.15 and 11.x to use the 10.14 SDK
 somehow? It clearly hasn't been updated to use neither the 10.15 nor the
 11.0 SDK, so either it's just remained broken, or there's some directive
 somewhere else that says, "if on 10.15 or 11, tell the build process to
 target for 10.14." Or something like that?

 Before editing files as described here, I did put the 10.14 SDK in
 `/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk`, but obviously
 to no avail.

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