aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorEd Maste <emaste@FreeBSD.org>2019-12-16 19:08:49 +0000
committerEd Maste <emaste@FreeBSD.org>2019-12-16 19:08:49 +0000
commit16ae835140e002b8360b4ea93193a3e2d3625d1a (patch)
tree9f263f8e525bfb39a7e4464eb1897978cc66e02f /UPDATING
parent68e1c49a9635964050a51264025fb8193b1adc4e (diff)
downloadsrc-16ae835140e002b8360b4ea93193a3e2d3625d1a.tar.gz
src-16ae835140e002b8360b4ea93193a3e2d3625d1a.zip
UPDATING: remove outdated caution against make -j
Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D22836
Notes
Notes: svn path=/head/; revision=355816
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING11
1 files changed, 3 insertions, 8 deletions
diff --git a/UPDATING b/UPDATING
index 881c1e65fbef..eca137554460 100644
--- a/UPDATING
+++ b/UPDATING
@@ -1934,19 +1934,14 @@ COMMON ITEMS:
General Notes
-------------
- Avoid using make -j when upgrading. While generally safe, there are
- sometimes problems using -j to upgrade. If your upgrade fails with
- -j, please try again without -j. From time to time in the past there
- have been problems using -j with buildworld and/or installworld. This
- is especially true when upgrading between "distant" versions (eg one
- that cross a major release boundary or several minor releases, or when
- several months have passed on the -current branch).
-
Sometimes, obscure build problems are the result of environment
poisoning. This can happen because the make utility reads its
environment when searching for values for global variables. To run
your build attempts in an "environmental clean room", prefix all make
commands with 'env -i '. See the env(1) manual page for more details.
+ Occasionally a build failure will occur with "make -j" due to a race
+ condition. If this happens try building again without -j, and please
+ report a bug if it happens consistently.
When upgrading from one major version to another it is generally best to
upgrade to the latest code in the currently installed branch first, then