On Thu, Jan 10, 2013 at 10:44:19PM +0000, Dag-Erling Smørgrav wrote:
> Author: des
> Date: Thu Jan 10 22:44:19 2013
> New Revision: 245269
> URL: http://svnweb.freebsd.org/changeset/base/245269
> 
> Log:
>   Remove all support for legacy NOFOO and NO_FOO build options.
> 

This commit caused

===> kerberos5/doc (buildincludes)
===> kerberos5/lib (buildincludes)
===> kerberos5/lib/libasn1 (buildincludes)
compile_et 
/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et
compile_et: No such file or directory
*** [asn1_err.h] Error code 1

Stop in /usr/src/kerberos5/lib/libasn1.
*** [buildincludes] Error code 1

Stop in /usr/src/kerberos5/lib.
*** [buildincludes] Error code 1

because I had forgotten that several years ago I added 
NO_KERBEROS to my /etc/make.conf.  After wasting a day
trying to figure out how and who broke world, including
reading the top of src/UPDATING, I recalled this commit
and checked my /etc/make.conf.  Setting WITHOUT_KERBEROS="YES"
in /etc/make.conf allowed buildworld to complete.  I 
suggest adding a blurb to src/UPDATING to help others
with memory loss issues.

Index: UPDATING
===================================================================
--- UPDATING    (revision 245426)
+++ UPDATING    (working copy)
@@ -26,6 +26,13 @@
        disable the most expensive debugging functionality run
        "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
 
+
+20130110:
+       Revision 245269 removed the legacy support for NOFOO and NO_FOO 
+       build options.  Individuals should review their /etc/make.conf
+       and /etc/src.conf for (long forgotten) NOFOO and NO_FOO, and 
+       changes these to WITHOUT_FOO.
+
 20121223:
        After switching to Clang as the default compiler some users of ZFS
        on i386 systems started to experience stack overflow kernel panics.


-- 
Steve
_______________________________________________
svn-src-head@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"

Reply via email to