[MacPorts] FAQ modified

[MacPorts Wiki]

Page "FAQ" was changed by jmroot
Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=183>
Revision 183
Comment: further explain difficulty of fixing /usr/local issue
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 182)
+++ FAQ (version: 183)
@@ -78,6 +78,7 @@
 No. Even though MacPorts is installed elsewhere, software installed in `/usr/local` can still interfere with MacPorts.
 Some software (especially the GNU auto* tools and gcc) looks into `/usr/local` for external headers, libraries, and binaries. Certain ports might (and do) fail to build because during their build something incompatible is found and picked up
 from `/usr/local`. Good ports avoid this by explicitly specifying `--with-libfoo=/opt/local/lib/` or explicitly disabling all such possible dependencies altogether with `--disable-foo` or `--without-bar` but not all ports are able to do that.
+And even if all files that should be found in `/opt/local` are correctly used, headers and libraries provided by the operating system in `/usr` will still be overridden if files of the same name exist in `/usr/local`.
 
 If you ask us for help with a port failing to build because of something
 that it found in `/usr/local` you will be asked to remove what you've installed in `/usr/local`
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/FAQ>
MacPorts <https://www.macports.org/>
Ports system for macOS

This is an automated message. Someone added your email address to be
notified of changes on 'FAQ' page.
If it was not you, please report to admin at macports.org.