Author: imp
Date: Mon Jan 28 22:50:54 2013
New Revision: 246043
URL: http://svnweb.freebsd.org/changeset/base/246043

Log:
  Add notes for breakage points for traditional building of the kernel
  as a guide to others. buildkernel, etc was not broken at these points,
  so document that as well.

Modified:
  stable/9/UPDATING

Modified: stable/9/UPDATING
==============================================================================
--- stable/9/UPDATING   Mon Jan 28 21:10:35 2013        (r246042)
+++ stable/9/UPDATING   Mon Jan 28 22:50:54 2013        (r246043)
@@ -35,6 +35,13 @@ Items affecting the ports and packages s
         Please refer to the "ZFS notes" section of this file for information
         on upgrading boot ZFS pools.
 
+20121114:
+       The commit introducing bsd.compiler.mk breaks the traditional
+       building of kernels before this point. Add -m ${SRC}/share/mk
+       (for the right value of SRC) to your command lines to work
+       around; update your useland to a point after this; or use the
+       buildkernel/installkernel top-level targets.
+
 20121102:
        The IPFIREWALL_FORWARD kernel option has been removed. Its
        functionality now turned on by default.
@@ -47,6 +54,12 @@ Items affecting the ports and packages s
        option, so the change only affects the custom kernel
        configurations.
 
+20120829:
+       The amd64 kernel now uses xsetbv, xrstor instructions. To compile with
+       the traditional method, you must update your system with an installworld
+       before the kernel will build. The documented make 
buildkernel/installkernel
+       interfaces (coupled with fresh make kernel-toolchain) continue to work.
+
 20120727:
        The sparc64 ZFS loader has been changed to no longer try to auto-
        detect ZFS providers based on diskN aliases but now requires these
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-stable-9
To unsubscribe, send any mail to "[email protected]"

Reply via email to