osxfuse build failure with Xcode 6.3

[gallafent]

Fragment of main.log below. Fragile script (build.sh) which demands exact version of Xcode (I do not use the term fragile as a perjorative here! For the purposes of system code I agree that one should be very exact regarding versions and this type of breakage is good :) …

:debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc1913b" && ./build.sh -t homebrew -f /opt/local'
:debug:build Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc1913b" && ./build.sh -t homebrew -f /opt/local 
:info:build OSXFUSEBuildTool()            : skip unsupported Xcode version in '/Applications/Xcode.app/Contents/Developer'.
:info:build OSXFUSEBuildTool() failed: no supported version of Xcode found.
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc1913b" && ./build.sh -t homebrew -f /opt/local 
:info:build Exit code: 1

I have successfully patched build.sh and built the package using my patched version. I have not tested extensively, but curlftpfs builds and appears to work fine against my freshly built version. Portfile is unchanged, just the additions to the buildsystem patch.

Revised patch (and patch patch, to see easily what I added; it was completely mechanical) will be attached.

[gallafent]

Revised buildsystem patch, adding detection of Xcode 6.3

[gallafent]

Differences between previous buildsystem patch and revised buildsystem patch

[ryandesign (Ryan Carsten Schmidt)]

Fixed in r136008. Rather than modifying the existing patch, I added a new patch containing only the upstream commit that added support for Xcode 6.3 (and 6.4). That should make it easier to remove again once a new version is released that already contains this fix.

[drkp (Dan Ports)]

Thanks! Not sure how I missed this ticket entirely before...