mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-17 10:26:15 +00:00
We've removed the special case code for upgrading from FreeBSD 9 so
remove the special warning. It's in svn if we need it.
This commit is contained in:
parent
452a74bfee
commit
212967ff26
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=334373
19
UPDATING
19
UPDATING
@ -32,25 +32,6 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
|
||||
"ln -s 'abort:false,junk:false' /etc/malloc.conf".)
|
||||
|
||||
|
||||
****************************** SPECIAL WARNING: ******************************
|
||||
|
||||
Due to a bug in some versions of clang that's very hard to workaround in
|
||||
the upgrade process, to upgrade to -current you must first upgrade
|
||||
either stable/9 after r286035 or stable/10 after r286033 (including
|
||||
10.3-RELEASE) or current after r286007 (including stable/11 and
|
||||
11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
|
||||
you'll need to take the unusual step of upgrading to the tip of the
|
||||
stable branch before moving to 11 or -current via a source upgrade.
|
||||
stable/11 and 11.0-RELEASE have working newer compiler. This differs
|
||||
from the historical situation where one could upgrade from anywhere on
|
||||
the last couple of stable branches, so be careful.
|
||||
|
||||
If you're running a hybrid system on 9.x or 10.x with an updated clang
|
||||
compiler or are using an supported external toolchain, the build system
|
||||
will allow the upgrade. Otherwise it will print a reminder.
|
||||
|
||||
****************************** SPECIAL WARNING: ******************************
|
||||
|
||||
20180523:
|
||||
The on-disk format for hwpmc callchain records has changed to include
|
||||
threadid corresponding to a given record. This changes the field offsets
|
||||
|
Loading…
Reference in New Issue
Block a user