From: BlaisorBlade <bla...@ya...> - 2004-10-22 17:29:32
|
Q: Why does "make linux ARCH=um" fail? R: Just use "make vmlinux ARCH=um", which creates the "vmlinux" binary, which is what you must use. Or even simply do "make ARCH=um", which is the same as: make vmlinux modules ARCH=um * Q: Why did you do this change? R: This is the result of a change which allows /proc/kallsyms to work, allowing UML to print stack traces on panic. * Q: Why did not you added a notice about "make linux ARCH=um"? R: I did that, only it was merged after 2.6.9. * Q: What did you do? R: within next version, each time you do "make linux ARCH=um", a hardlink is created from linux to vmlinux. I.e. they are two copies of the same file, sharing the content. If you do a "make vmlinux ARCH=um", instead of leaving a stale linux file with the old content, or relinking it, we simply remove the vmlinux file. It is assumed that if you do "make vmlinux ARCH=um", you already know of this change. * Q: Why didn't you do simply "mv vmlinux linux"? R: because that way another "make linux" would relink again the files. Bye -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |