On 10/2/07, Alistair John Strachan <[EMAIL PROTECTED]> wrote: > This is certainly a tool issue, but if I use Debian's kernel-image "make-kpkg" > wrapper around the kernel build system, it fails with: > > cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory > > Obviously, this file has moved to arch/x86/boot, but it seems like possibly > unnecessary breakage. I've been copying bzImage for years from > arch/x86_64/boot, and I'm sure there's a handful of scripts (other than > Debian's kernel-image) doing this too.
I believe most sane tools would be using the output of uname -m, so a possible way to fix this would be fixing the data passed to userspace from uname. However, that might be the case that it creates a new set of problems too, with tools relying on the output of uname -m to determine wheter the machine is 32 or 64 bit, and so on. -- Glauber de Oliveira Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
