Paul Wain writes:
 > 
 > >  config DACO
 > >  cd ../compile/DACO
 > >  make depend
 > >  make
 > >
 > > and then after 1H45 min, i obtain this error :
 > >
 > > ld -Ttext F0000020 -e start -x -o netbsd ${SYSTEM_OBJ} vers.o
 > > collect2: ld returned 1 exit status
 > > shell_shell.0 (.text+0x136c): undefined reference to 'asc_dump'
 > > *** error code 1
 > 
 > At a 1st guess I would say that you have a problem in your configuration file. 
 > Take a look in the file shell_shell.c (in my version of the kernel its in 
 > arch/arm32/kshell/kshell_shell.c but if you cd to arch/arm32 and do a 'find . 
 > -name shell_shell.c' you should be able to locate it). This is, for some 
 > reason, believeing that it needs asc_dump. 

In my (recently supped tree), I have kshell/shell_shell.c. In this
file all references to asc_dump are guarded by #if NASC > 0/#endif
pairs... I have noticed some problems in the past with dependencies in
that things sometimes get confused.

 > Now asc_dump() is defined in asc.c which only gets included if you turn on the 
 > "asc*" device. Looking at the code, it would appear that you will need to 
 > configure in the asc device in your kernel because of a clash with some other 
 > device you are using? (I am I must admit using a different source tree however 
 > so you will need to do a bit of digging to find what is conflicting etc. - 
 > config/files.arm32 is a good-ish place to start looking - be careful not to 
 > damage this file however - it is a good deal more complicated than a config 
 > file).

It appears that the config may have been editted from having the asc
to not having it, but shell_shell.o failed to get rebuilt. try:

cd ../compile/DACO
rm shell_shell.o
make

 > Paul.

Cheers Scott

-- 
Scott Stevens, Network Services Group, Computer Centre, Imperial College
"He who controls the spice controls the universe"
                                                  - Baron Harkonnen, Dune