https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217695
Dimitry Andric <d...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|New |Closed
--- Comment #1 from Dimitry Andric <d...@freebsd.org> ---
Please follow the clearly marked section at the top of /usr/src/UPDATING, e.g.:
****************************** 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: ******************************
Your host system seems to be 10.2, so you should upgrade to stable/10 r286033
or later first.
*** This bug has been marked as a duplicate of bug 215985 ***
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
