SUMMARY: Kernel build problems on AlphaStation 200 4/233

From: John Deacon <jrd_at_star.ucl.ac.uk>
Date: Tue, 26 Mar 1996 15:18:08 +0000 (GMT)

Thanks to Knut Hellebo <Knut.Hellebo_at_nho.hydro.com> for a quick response
that solved the problems I was having getting a new kernel to build.

Summary of problem:

I'd deleted the LSM and ADVFS subsets and wanted to rebuild the kernel.
After removing the lsm and lsm_ted pseudo-device entries from the config
file the build failed saying "Can't open: bs_bmt_util.o (No such file or
directory)". If I used a config file generated by sizer the build complained
about multiply defined cam_ccb parameters.

Knut's suggestions:

>When deleting LSM and AdvFS, did you delete all LSM and ADvFS related subsets
>? Did the 'setld -d subset' command give any errors ? The first two errors
>indicate that there are still references to the LSM and the AdvFS subsets
>somewhere. Did you try 'rm -r /sys/SYSNAME' and then a 'doconfig -c SYSNAME'
>after removing the LSM and AdvFS subsets ?
>
>The messages
>
>> param.o compressed: cam_ccb_pool_size: multiply defined
>> param.o compressed: cam_ccb_low_water: multiply defined
>> param.o compressed: cam_ccb_increment: multiply defined
>
>indicate that the three defines also are defined in /sys/data/cam_data.c
>(from which they should have been removed). You can safely comment them out
>in /sys/data/cam_data.c and keep them in /sys/conf/param.c
>

AdvFS is selected via "options MSFS" in the config file, deleting this solved
the bs_bmt_util problem. The cam_ccb entries have been moved to
/sys/conf/param.c so they can be changed with /etc/sysconfigtab, commenting
out the entries in cam_data.c got rid of the multiple definition errors and
the kernel now builds.

Thanks again,

 John Deacon
 Starlink Manager
 Dept of Physics & Astronomy
 University College London
Received on Tue Mar 26 1996 - 17:05:55 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT