Date: Tue, 17 Nov 2009 01:03:42 +0000 From: Rui Paulo <rpaulo@freebsd.org> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: wpa_supplicant + wpi0 won't lock in on today's -current Message-ID: <35695A2B-6ADD-4060-9A47-0C9C4C57DFD9@freebsd.org> In-Reply-To: <4B01EE51.2040904@FreeBSD.org> References: <4B0087C2.9070508@FreeBSD.org> <4B00BA99.5000009@FreeBSD.org> <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> <4B01B66F.1040903@FreeBSD.org> <4B01C3A6.5060101@FreeBSD.org> <D1A55515-703E-4775-8F90-0CB9491CCC7B@freebsd.org> <4B01EE51.2040904@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Nov 2009, at 00:29, Doug Barton wrote: > Rui Paulo wrote: >> On 16 Nov 2009, at 21:27, Doug Barton wrote: >>=20 >>> 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. >>=20 >> Well, when I did this change I did build with -DNOCLEAN and it = rebuilt a good wpa_supplicant. >=20 > I'm not in any way implying that you did not test the change = thoroughly. >=20 > Please let me know your intentions regarding the UPDATING entry. I'll > be glad to augment it myself if necessary. I'm ok with mentioning that wpa_supplicant must also be rebuilt and/or = mentioning that NOCLEAN must be disabled. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35695A2B-6ADD-4060-9A47-0C9C4C57DFD9>