git-annex 10.20230126-3 fails to build from source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ghc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
git-annex (Debian) |
Fix Released
|
Unknown
|
|||
git-annex (Ubuntu) |
Confirmed
|
High
|
Sergio Durigan Junior |
Bug Description
git-annex 10.20230126-3 fails to build from source:
```
[618 of 681] Compiling Assistant.
/usr/bin/ld.gold: error: dist/build/
collect2: error: ld returned 1 exit status
`x86_64-
```
Full amd64 build log: https:/
Changed in git-annex (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: update-excuse |
Changed in git-annex (Ubuntu): | |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
Changed in git-annex (Debian): | |
status: | Unknown → New |
Changed in git-annex (Debian): | |
status: | New → Fix Released |
I looked at this issue for quite a while. The package does *not* FTBFS in Debian. I tried passing various combinations of PIC and PIE flags to ghc, to no avail. Sadly, I wasn't able to even determine that the flags I gave made their way down to the linker invocation, since it's not possible for ghc to be loud in its invocation.
However, comparing the results of the Debian and Ubuntu compilation, the .o file contains in both cases the R_X86_64_PC32 relocation, which makes me think that it's a difference in linker behaviour. I wasn't able to find anything suspicious in our binutils delta with Debian.
I'm assigning this to GHC because it seems clearly a toolchain issue to me.
For whoever picks it up again, note that build parallelism is disabled at the top of d/rules. For your builds you might want to enable it again (simply use -j instead of -j1).