I keep my kernel source tree on a more powerful build box where I run my builds etc (including "make cscope") but run my editor from my workstation with an NFS mount to the source. This worked fine for me using relative paths for cscope. Using absolute paths in cscope breaks this previously working setup because the root path is not the same on both systems. I guess this is similar to moving the source tree around. Without wanting to start a flamewar it really sounds to me like we are working around a vim (or cscope) bug here, emacs with cscope bindings works fine in this configuration. Could we at least have an option to allow both variants to work? Would setting "make O=$(pwd) cscope" (where pwd is the source tree) not have provided a workaround for people who needed absolute paths for whatever reason? Ian. -- Ian Campbell Current Noise: Testament - D.N.R. (Do Not Resuscitate) What do you give a man who has everything? Penicillin. -- Jerry Lester -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
