On Wed, 2012-01-18 at 09:15 -0800, Luis R. Rodriguez wrote: > On Wed, Jan 18, 2012 at 12:13 AM, Luciano Coelho <coelho@xxxxxx> wrote: > > If you're cross-compiling compat-wireless on a different host, you > > can't reliably use modprobe. The host system may not even have > > modprobe, so it doesn't make sense to run modprobe, unless you're > > installing the modules on the target machine. > > > > The modprobe command was being used unconditionally to set the MADWIFI > > and OLD_IWL variables. This commit adds a check to see whether > > modprobe exists before trying to use. It also adds a dependency on > > the modprobe commands to all recipes that rely on it, so we fail more > > gracefully if modprobe doesn't exist in the system. > > > > Reported by: William List <wlist@xxxxxx> > > Signed-off-by: Luciano Coelho <coelho@xxxxxx> > > Good point, I've propagated this into the linux-3.2.y and linux-3.1.y > branches of compat-wireless as well so that if a new release is made > the fixes go along with it. Excellent, thanks dude! -- Cheers, Luca. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
