Date: Thu, 12 Jan 2017 14:26:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 215985] Cannot build world of 11.0.1 on 10.1-RELEASE Message-ID: <bug-215985-8-ryUIbLslnM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215985-8@https.bugs.freebsd.org/bugzilla/> References: <bug-215985-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215985 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #1 from Warner Losh <imp@FreeBSD.org> --- >From UPDATING: ***************************** SPECIAL WARNING: ****************************= ** Due to a bug in some versions of clang that's very hard to workarou= nd 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 cl= ang compiler or are using an supported external toolchain, the build sy= stem will allow the upgrade. Otherwise it will print a reminder. It was too late to include this in 11.0 when it was discovered. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215985-8-ryUIbLslnM>