On Tue, 2009-09-22 at 11:52 -0700, Roland McGrath wrote:
> Could it be that we search .../build because of vmlinux? If one
makes a
> custom kernel and does a "make modules_install", then all of the modules
> get copied into /lib/modules/RELEASE/kernel/, but the unstripped,
> uncompressed vmlinux is only available in the original build path.
I think it was stap users doing this and requesting it work that I was
thinking of.
That makes sense. So we need the uncompressed vmlinux under build/ for
the debuginfo? Then wouldn't it be possible to only reach into build/
for the vmlinux file and not traverse it fully also for the modules
(which are under kernel/)?
I admit to never build a kernel from scratch, I always just rebuild my
distros kernel package and install the result. I'll try and do an
"upstream" build and see what happens.
Cheers,
Mark