On Tuesday 14 May 2002 01:31, Keith Owens wrote: - sed -e "s:\(.*\):cp -fa \1 $(module_dir)kernel/\1:" $(objfile .tmp_vmlinux_modules) | $(KBUILD_SHELL) + sed -e "s:\(.*\):cp \1 $(module_dir)kernel/\1:" $(objfile +.tmp_vmlinux_modules) | $(KBUILD_SHELL)
I thought you'd leave the -f in, but that does not matter here because the tree is removed anyway. More importantly, I think the same change should be done for the other files that are installed (vmlinux, System.map, ...), so they end up with proper attributes in INSTALL_PREFIX. At least that was the behavior in kbuild-2.4 and I see no reason to change it. > OTOH, I can detect if some makefile associated data has changed at > install time and issue warnings. What do people think, is it worth > checking for CML and makefile changes during install or is the message > "Using existing global Makefile for install" enough of a hint that CML > and makefile changes are ignored. This is only a problem when building > as one user and installing as another, doing make oldconfig install all > as root does a full check. AFAICS, the problem case is even more limited. I hit it only because I changed the /install/ procedure after making the installable. If I make installable and then su to make install, I expect the build system to install the kernel that I have just made, so that is ok. Maybe it would be nice to check the install related files (/Makefile.in, /arch/$(ARCH)/boot/Makefile.in, ...) before installing as another user. Arnd <>< _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
