On Wed, 2017-10-11 at 20:36 +0200, nicolas.mailhot@xxxxxxxxxxx wrote: > De: "Frank Ch. Eigler" > > > nicolas.mailhot wrote: > > > > > [...] > > > extracting debug info from > > > /builddir/build/BUILDROOT/golang-github-performancecopilot-speed- > > > 2.0.0-1.el7.llt.x86_64/usr/bin/mmvdump > > > *** ERROR: No build ID note found in > > > /builddir/build/BUILDROOT/golang-github-performancecopilot-speed- > > > 2.0.0-1.el7.llt.x86_64/usr/bin/mmvdump > > > > See https://fedoraproject.org/wiki/PackagingDrafts/Go#Build_ID > > Thanks, I somewhat missed it in all the not-really current EL6- > oriented stuff in this document I CCed Jakub, who maintains the go package. He might have some update to this. We did recently discuss adding the support directly to the go linker, but I believe that isn't yet there. The problem indeed is that the golang linker doesn't insert a build-id note in the executable. In theory this can also be worked around by using %undefine _missing_build_ids_terminate_build in your spec file. But the workaround in the wiki is better. Once there is a build-id note rpm debugedit can update it (making it unique, but stable). Unfortunately rpm debugedit cannot insert it itself. The ELF note needs to be in an allocated section, meaning that to add it the runtime program headers also need to be update. And rpm debugedit cannot do that easily. Only a real linker can. Please let me know if there are any other issues with debuginfo packages for go programs that you cannot work around with the hints in the wiki page. Thanks, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
