summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorbdrewery <bdrewery@FreeBSD.org>2015-12-01 19:00:43 +0000
committerbdrewery <bdrewery@FreeBSD.org>2015-12-01 19:00:43 +0000
commitdb2cac2a60d91280013fd96a9b5c1587e032fe38 (patch)
tree62d850c91f2f56ba530c7d7df9067f763091079c /UPDATING
parent179e96016ad7ebaa44e955d6a0435cd2156c0d5c (diff)
downloadFreeBSD-src-db2cac2a60d91280013fd96a9b5c1587e032fe38.zip
FreeBSD-src-db2cac2a60d91280013fd96a9b5c1587e032fe38.tar.gz
Fix errors being ignored in many phases of the build since the bmake integration.
Say it with me, "I will not chain commands with && in Makefiles" This was originally fixed and explained quite well by bde@ in r36074. The initial bmake integration caused 'set -e' to stop being used which lead to r252419. Later 'set -e' expectations were fixed with bmake in r254980. Because of the && here, errors would be ignored when building in parallel and a dependency failed. Such as bootstrap-tools since it builds everything in parallel. If any tool failed in obj/depend/all, it would just ignore the error and continue to build. This later would result in cascaded errors that only confused the real issue. This could also cause commands after the failed command to still execute, leading to more confusion. This should be fine if the command is in a sub-shell such as: (cmd1 && cmd2) This reverts r252419. MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING8
1 files changed, 0 insertions, 8 deletions
diff --git a/UPDATING b/UPDATING
index 1c90c2c..4169a10 100644
--- a/UPDATING
+++ b/UPDATING
@@ -849,14 +849,6 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
keep 64-bits counters. Thus all tools, that work with networking
statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
-20130629:
- Fix targets that run multiple make's to use && rather than ;
- so that subsequent steps depend on success of previous.
-
- NOTE: if building 'universe' with -j* on stable/8 or stable/9
- it would be better to start the build using bmake, to avoid
- overloading the machine.
-
20130618:
Fix a bug that allowed a tracing process (e.g. gdb) to write
to a memory-mapped file in the traced process's address space
OpenPOWER on IntegriCloud