Changes between Version 147 and Version 148 of ProblemHotlist

Timestamp:

Aug 9, 2020, 10:32:30 AM (4 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

Fix guide links

ProblemHotlist

@@ -56 +56 @@
 strip: object: libbar.dylib malformed object (unknown load command 9)
 }}}
-indicates that your `install_name_tool` or `strip` commands (both are part of the Xcode command line tools) are too old to deal with the types of objects produced by the compiler. (The number after "unknown load command" may be different.) This can happen if you have forgotten to [https://guide.macports.org/chunked/installing.xcode.html update the Xcode command line tools] to a version designed for your version of OS X.
+indicates that your `install_name_tool` or `strip` commands (both are part of the Xcode command line tools) are too old to deal with the types of objects produced by the compiler. (The number after "unknown load command" may be different.) This can happen if you have forgotten to [https://guide.macports.org/chunked/installing.html#installing.xcode update the Xcode command line tools] to a version designed for your version of OS X.
 
 == Incompatible library version: X requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0 == #libiconv-version
@@ -133 +133 @@
 Another possible reason is that you previously had MacPorts (and expat and probably other ports) installed, then somehow uninstalled MacPorts itself, or at least its registry of which ports are installed, without actually uninstalling those ports, and have now installed MacPorts again with a clean registry, which therefore thinks no ports are installed, though some still are.
 
-Either way, the cleanest solution at this point is to follow the [http://guide.macports.org/chunked/installing.macports.uninstalling.html MacPorts uninstallation instructions]. This will remove the 3rd-party software package that installed itself unannounced into MacPorts' prefix, and/or ports installed by your prior MacPorts installation. Then you can [http://guide.macports.org/chunked/installing.macports.html install MacPorts] again.
+Either way, the cleanest solution at this point is to follow the [https://guide.macports.org/chunked/installing.macports.uninstalling.html MacPorts uninstallation instructions]. This will remove the 3rd-party software package that installed itself unannounced into MacPorts' prefix, and/or ports installed by your prior MacPorts installation. Then you can [https://guide.macports.org/chunked/installing.macports.html install MacPorts] again.
 
 == A port failed to build with a message referring to 1/lib: No such file or directory == #lib-spaces
@@ -299 +299 @@
 The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build.
 You can install them from Xcode's Preferences in the Downloads section.
-See http://guide.macports.org/chunked/installing.xcode.html#installing.xcode.lion.43 for more information.
+See https://guide.macports.org/chunked/installing.html#installing.xcode.lion for more information.
 }}}
 }}}
@@ -321 +321 @@
 {{{
 You can install them from Xcode's Preferences in the Downloads section.
-See http://guide.macports.org/chunked/installing.xcode.html#installing.xcode.lion.43 for more information.
+See https://guide.macports.org/chunked/installing.html#installing.xcode.lion for more information.
 }}}
 }}}