Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Nov 2009 14:30:51 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Doug Barton <dougb@freebsd.org>
Cc:        Rui Paulo <rpaulo@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: wpa_supplicant + wpi0 won't lock in on today's -current
Message-ID:  <20091116223051.GA90683@troutmask.apl.washington.edu>
In-Reply-To: <4B01C3A6.5060101@FreeBSD.org>
References:  <4B0087C2.9070508@FreeBSD.org> <4B00BA99.5000009@FreeBSD.org> <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> <4B01B66F.1040903@FreeBSD.org> <4B01C3A6.5060101@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 16, 2009 at 01:27:02PM -0800, Doug Barton wrote:
> Doug Barton wrote:
> > Rui, it would be nice to include a note about this in UPDATING.
> 
> To be fair someone else drew my attention to the fact that there is an
> entry in UPDATING about the change, however it doesn't mention
> wpa_supplicant, and merely recompiling wpa_supplicant wasn't
> sufficient to fix the problem, so perhaps that entry could be expanded.
> 
> Doug
> 

After reviewing this thread and with the speed with which head
can change, I'll suggest the following for UPDATING

Index: UPDATING
===================================================================
--- UPDATING    (revision 199277)
+++ UPDATING    (working copy)
@@ -878,12 +878,16 @@
        -------------
        Avoid using make -j when upgrading.  While generally safe, there are
        sometimes problems using -j to upgrade.  If your upgrade fails with
-       -j, please try again wtihout -j.  From time to time in the past there
+       -j, please try again without -j.  From time to time in the past there
        have been problems using -j with buildworld and/or installworld.  This
        is especially true when upgrading between "distant" versions (eg one
        that cross a major release boundary or several minor releases, or when
        several months have passed on the -current branch).
 
+       Avoid using make -DNO_CLEAN when upgrading.  While generally safe, 
+       there are sometimes problems using -DNO_CLEAN to upgrade.  If your
+       upgrade fails with -DNO_CLEAN, please try again without -DNO_CLEAN.  
+

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091116223051.GA90683>