MacPorts missing links

[Lawrence Velázquez]

> On Sep 12, 2016, at 11:02 PM, Al Varnell <alvarnell at mac.com> wrote:
> 
> Perhaps the Wiki page needs to state more clearly that this only needs to be done for major OS X/macOS upgrades, that is from 10.11.x to 10.12, for instance.

I don't think this a problem, at all. The wiki can't get much clearer on the issue.

        A MacPorts installation is designed to work with a particular
        operating system and a particular hardware architecture.
        Problems may occur after major system changes, such as:

                - major operating system upgrades (e.g., from 10.9
                  Mavericks to 10.10 Yosemite).
		- architecture migrations (e.g., from PowerPC to Intel).

        Please follow this procedure to ensure a smooth transition.
        (This isn't necessary if you only upgrade Xcode.)

Frankly, I would not support any attempt to downplay the need to reinstall because we have the *opposite* problem: Some users don't even reinstall MacPorts after major upgrades.

> In all the years I've been using MacPorts I have never needed to reinstall the MacPorts base for a minor upgrade.

Nor should you have.

> I would also encourage somebody to look into the need for both Xcode and Command Line Tools since Xcode 7. Apple makes it quite clear on the download page that Xcode now contains the CLTs, so installing both might well cause issues and clearly waste valuable space.

Some stubborn build systems look for stuff in /usr/include and similar locations and complain if they don't exist. If anything, working on the inverse configuration (CLT only, no Xcode) would be a better use of time.

vq