macports reports broken port, broken files after installing audacity 3.0.2.129

[dyne2meter]

... suggests a rebuild, which succeeds, but broken port and files found again, and the rebuild process goes into a loop that ends after several failures.

Some of what I read about this (type of) problem suggested to me that the build is not finding the right SDK. This report is for Mac OS 10.13, but with a brand new xcode 9.4.1 install, adding the command line tools only gives me the 10.14 SDK. I tried a symlink to the 10.13 SDK in the Xcode.app package, but no joy there, either.

The report for port health on this OS is at variance with what I'm finding. Furthermore, on a system running MacOS 10.14, the old "macOS 10.14 SDK does not appear to be installed" is reported, and yet I have this SDK.

Audacity, even in its "broken" state still runs, and I'm curious what the problem (if any) really is.

It has cost me a lot of time downloading and re-installing Xcode and so on, so if the port isn't really broken, the linking checker should not be telling me that it is. I read the message about how this port is now "pinned" to the 10.13 SDK, but even with a link to this SDK in /Library/Developer/..., the build-from-distfile still goes haywire. What's up with all this?

I know about audacity-legacy, so if this one is really broken for me, I know the legacy version installs without issues.