I think it is port-dependent. Some ports worked fine with the symlink, but some (e.g., gcc) failed due to differences in the headers from what they were expecting.
> On Sep 23, 2019, at 9:53 PM, Vincent <vi...@macports.org> wrote: > > Hey, > >> On 24 Sep 2019, at 00:12, Ralph Castain <r...@pmix.org> wrote: >> >> I tried uninstalling all ports and reinstalling them, but that didn't >> help. Ditto for simply creating a MacOSX10.14.sdk symlink. > > The symlink kludge worked with me, so I wonder what may be wrong in your case. > > Vincent
