On 03/20/2017 01:46 AM, Mark Wielaard wrote:
> Hi,
> 
> In case people didn't notice in the somewhat long analysis of the issue in 
> the bug, the workaround is just a simple oneliner:
> 
> diff --git a/kernel.spec b/kernel.spec
> index cb3dec8..29c198a 100644
> --- a/kernel.spec
> +++ b/kernel.spec
> @@ -183,6 +183,9 @@ Summary: The Linux kernel
>  %define _enable_debug_packages 0
>  %endif
>  %define debuginfodir /usr/lib/debug
> +# Needed because we override almost everything involving build-ids
> +# and debuginfo generation. Currently we rely on the old alldebug setting.
> +%global _build_id_links alldebug
>  
>  # kernel PAE is only built on i686 and ARMv7.
>  %ifnarch i686 armv7hl
> 
> Of course it would be nice if someone could cleanup the various places that 
> the kernel.spec overrides rpm find-debuginfo.sh and debugedit and provides 
> some requirements that would make this all easier for the kernel build. It 
> looks like the current build does a lot redundant extra work that might be 
> prevented if rpm provided better hooks to do automagically what the kernel 
> spec build requires. One thing rpm wants to introduce in the future (already 
> upstream) is parallel processing of debug files. Which the current 
> kernel.spec seems to prevent because it serializes the processing itself 
> already.
> 
> I would be happy to review any feedback on why the kernel.spec has the 
> current hacks and suggestions for improvements to make this smoother.
> 
> Cheers,
> 
> Mark

I spent some time looking at this and I have something that produces
debuginfo without overriding find-debuginfo.sh or calling debugedit
manually. I have no idea if this debuginfo is useful/correct so this
needs more review/testing. Patch is attached if anyone wants to
review and there is a scratch build going at 
https://koji.fedoraproject.org/koji/taskinfo?taskID=18701457.

One area that could really use improvement is the filtering. The
kernel filters everything into many different debuginfo packages
using the -p filter. Debugging those regexes is an absolute nightmare
and my current proposal relies on knowing how find-debuginfo.sh
sets the build-id. Do you have any suggestions on how to make
the filtering more sustainable?

Thanks,
Laura
_______________________________________________
kernel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to