Re: F28 System Wide Change: Golang 1.10a

[Jakub Cajka]

----- Original Message -----
> From: "nicolas mailhot" 
> To: [e-mail], "Jakub Cajka" , "Development discussions related to Fedora"
>
> Sent: Friday, January 12, 2018 4:32:22 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
> Hi,
>
> With the new Go 1.10 I get
> echo
>
> /usr/share/gocode/src/github.com/hashicorp/go-discover/cmd/discover/main.go
> install -m 0755 -vd
>
> /builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin
> install: creating directory
> '/builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin'
> install -m 0755 -vp _bin/discover
>
> /builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin/
> '_bin/discover' ->
> '/builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin/discover'
> /usr/lib/rpm/find-debuginfo.sh -j4 --strict-build-id -m -i --build-id-seed
>
> 0-0.5.0.20180108git7642001.fc28.llt --unique-debug-suffix
> -0-0.5.0.20180108git7642001.fc28.llt.x86_64 --unique-debug-src-base
> golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64
> --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S
> debugsourcefiles.list
> /builddir/build/BUILD/go-discover-7642001b443a3723e2aba277054f16d1df172d97
> extracting debug info from
> /builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin/discover
> dwz: dwz.c:8790: write_die: Assertion `refd != NULL' failed.
> /usr/lib/rpm/find-debuginfo.sh: line 518:  1870 Aborted                 (core
> dumped) dwz $dwz_opts ${dwz_files[@]}
> /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match.
>
> in golang-github-hashicorp-discover
>
> Any idea if it's due to Go 1.10 or another fedora-devel change?
>
> Regards,
>
> --
> Nicolas Mailhot

I would suspect debug info extraction based on the log, turning off debug package should workaround the issue. Other question if debug info extraction fails due to bug in it or if it is broken by broken debug info in golang binaries. I haven't stumbled on this while rebuilding distro with 1.10 beta1(does the build pass in f27?), this package is not on the list of failed builds(still processing them).

JC