[CUWiN-Dev] 0.5.4 questions

[Bill Comisky]

I built an upgrade image and successfully installed it last week (rev 2460 
of the cuw-0.5.4 branch).  Is there a checklist of tests I should perform 
on a new build to provide you with the best feedback?  And more 
specifically, what new features should be working in 0.5.4 that I should 
test?

First thing I did was to pull up the web interface (cool!), though I'm not 
sure everything was working right; I had one other node up and while it 
was in the routing table it didn't show up in the routeViz display.  I 
didn't have time to investigate though (and now my connection to our build 
box is down).

I did have one last build glitch.  I changed the name of the directory 
holding the CUWiN source to reflect my switch to the 0.5.4 branch (mv 
cuw-trunk cuw-0.5.4), but when I rebuilt I consistently got the error 
message at the bottom, where it was still looking for iswlan.c in the old 
path, which was no longer there.  I even rebuilt without -u -o.  Is there 
a directory I should clean out or a 'make clean'-esque command I could run 
to fix?  I just symlinked cuw-0.5.4 to cuw-trunk as a temp fix.

bill

--
Bill Comisky
bcomisky at pobox.com


all ===> iswlan
nbmake: don't know how to make 
/usr/local/cuwin/cuw-trunk/src/iswlan/iswlan.c. Stop

nbmake: stopped in /usr/local/cuwin/cuw-0.5.4/src/iswlan

*** Failed target:  all-iswlan
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; 
shift; case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .) this=""; 
real="/usr/local/cuwin/cuw-0.5.4/src" ;; *) this="${dir}/"; 
real="/usr/local/cuwin/cuw-0.5.4/src/${dir}" ;; esac; show=${this:-.}; 
echo "${target} ===> ${show%/}${1:+ (with: $@)}"; cd "${real}" && 
/usr/local/cuwin/build/T/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; 
_makedirtarget iswlan all
*** Error code 2

Stop.