Richard, I have not really followed this thread, but you might want to read: http://en.opensuse.org/Configure%2C_Build_and_Install_a_Custom_Linux_Kernel I happened to have a uncompiled suse kernel sitting in /usr/src/linux-2.6.27.25-0.1 As root I did: cd /usr/src/linux-2.6.27.25-0.1 # just to be sure this is a virgin setup make clean make mrproper # Verify include/asm does not exist ls -l include/asm # not found in virgin setup # cloneconfig is a suse specific target, but I think you are compiling suse's kernel make cloneconfig ls -l include/asm # still not there (as expected) make prepare ls -l include/asm # We have a symlink, hurray! "make prepare" is not normally called directly. It is a part of other make processes, but it is the specific make target that creates the symlink. I don't think there is any harm in calling it directly. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org