[MacPorts] #63741: macports reports broken port, broken files after installing audacity 3.0.2.129

[MacPorts]

#63741: macports reports broken port, broken files after installing audacity
3.0.2.129
-------------------------+--------------------
  Reporter:  dyne2meter  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.1
Resolution:              |   Keywords:
      Port:  audacity    |
-------------------------+--------------------
Description changed by dyne2meter:

Old description:

> ... 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.
>
> 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", and yet it is.
>
> 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?

New description:

 ... 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.

 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?

--

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