Changes between Version 182 and Version 183 of FAQ
- Timestamp:
- Feb 22, 2021, 1:42:12 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v182 v183 79 79 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 80 80 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. 81 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`. 81 82 82 83 If you ask us for help with a port failing to build because of something