What | Removed | Added |
---|---|---|
CC | msuchanek@suse.com |
(In reply to Martin Li������ka from comment #0) > Thus a suggested fix can be putting the > vdso a separate kernel-source-userspace package or so. It'd have to be in kernel-%{flavor}-vdso instead -- it's different for different flavors. In that case kernel-%{flavor}-vdso-debug* should be created automatically. I think it's not that hard to do that on the kernel side. The questions is: do we also need "Require: kernel-%{flavor}-vdso" in kernel-%{flavor} to drag it automatically in? I.e. what tools read vdso.so if any at all?