Chris,
Chris Needham wrote:
I've also encountered this on two separate builds, but I found a work around
Switch to he wireless directory, do a make clean and then do a make, this builds all the objects, if you then switch back to the main build it then runs through fine ( the objects are up to date ). I don't use a wireless client so can't comment on if this still allows wireless devices run.
Thanks for this workaround. I have looked a bit deeper and am now wondering if the "error" isn't in the iwlib.h header file.
lines 130-131 of iwlib.h say:
/* Private copy of Wireless extensions */ #include <wireless.h>
if I change this to
/* Private copy of Wireless extensions */ #include "wireless.h"
then the wireless.h file is indeed picked up and the linuxboot.iso build succeeds. But unfortunately I am in the same position as you and I don't use the wireless stuff so I can't say if the soo built binaries are good ones.
So there is three ways of dealing with this.
1. uncomment the building of the wireless_tools from the Makefile altogether (if you don't need it)
2. do the individual build the way you suggested for the wireless tools first before doing the complete linuxboot build
3. possibly get the wireless_tools developer(s) to look at whether my small change from <wireless.h> to "wireless.h" is actually what was originally intended
Regards,
Urs Rau
PS: I have copied the wireless_tools developer, Jean, from HP on this and we might hear back from him on this. Jean I will send you the beginning of this email thread in a couple minutes, seperately.
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
