as I wrote. The wpa_supplicant build failed. No wpa_supplicant executable exists. Downloading the packet and build it due to the README in the package works. No madwifi needed. The download of madwifi is that what hurts me, not the build.
Regards Frank On Sat, 2005-01-15 at 18:28 +1300, Nick Rout wrote: > On Fri, 2005-01-14 at 08:38 +0100, Frank Schafer wrote: > > Hi, > > > > the original poster (me ;), got the card (ipw2200) working, would very > > like to use the gentoo methods, but wasn't able to get wpa_supplicant > > (masked) to work. > > He tried to ebuild wpa_supplicant and the (needless) madwifi was > > downloaded and installed too amd the build failed. > > I don't thhink madwifi does get installed, the madwifi package is not a > dependency of wpa_supplicant. the madwifi source does get downloaded > though, presumably it is needed in order to compile wpa-supplicant. > > did you take the steps stated at the end of the ebuild, ie make a config > file? > > did you start the wpa_supplicant service? > > > > The (gentoo installed) hotplug didn't load the firmware. That's why I > > unmerged this too and installed it by hand. It's working now. > > > > Maybe the firmware problem is caused by the fact that gentoo by some > > reason /usr/lib/hotplug moved to /lib/hotplug. > > > > Well, /usr could be a filesystem which still isn't mounted when the > > firmware is needed but I don't have an idea in which cases this could > > happen. > > > > Regards > > Frank > > > > On Thu, > > > > 2005-01-13 at 22:56 +0200, Matan Peled wrote: > > > Eugene Rosenzweig wrote: > > > > Is there such a thing as deep-dependency? If I try to emerge a ~x86 > > > > package which depends > > > > on a masked package of which I have installed the stable version, > > > > emerge will complain and > > > > I would have to install the dependency first, with all its > > > > dependencies. Seems to me all > > > > dependencies will be resolved. I've had to do it before but never > > > > deeper than one > > > > dependency, unlike my old RedHat 7 system of olden days where I was > > > > forever working out > > > > which rpms I needed and which version. > > > > > > Of course there exists such a beast. A good example would be the new > > > Enlightment > > > (sp?) window manager, which has some crazy dependencies. Also gnome, not > > > kde > > > because that is pretty simple package-wise. > > > > > > BTW, if you have an: > > > emerge sys-apps/foo > > > > > > That requires sys-libs/bar of version larger than or equal to 2.0.2, then > > > you > > > should not package.keywords ">=sys-libs/bar-2.0.2" and do an: > > > emerge sys-libs/bar > > > > > > You should add that line to package.keywords and do: > > > emerge sys-apps/foo > > > > > > So that the library would be added as a dependency, not into world, and > > > "emerge > > > depclean" would be able to get rid of it properly. > > > > > > I'm pretty sure you did not mean this, but it could be implied from your > > > mail, > > > so I thought I would clarify. > > > > > > And also, BTW, this ACX100 WiFi card works perfectly, with initscripts > > > from the > > > masked baselayout that configure it at boot. > > > > > > It seems that the original poster's problem was that he was trying to > > > avoid > > > using Gentoo's methods of making the card work, instead working around it > > > and > > > installing by hand (Which also works, but its harder...). > > > > > > > > > > > > > -- > > [email protected] mailing list > > -- [email protected] mailing list
