Bug#803474: src:systemd: Please use the default linker instead of gold on sparc64

Michael Biebl biebl at debian.org
Sun Nov 8 22:15:50 GMT 2015


Hi,

Am 07.11.2015 um 00:28 schrieb John Paul Adrian Glaubitz:
> On 11/05/2015 06:14 PM, Michael Biebl wrote:
>> Am 05.11.2015 um 17:53 schrieb John Paul Adrian Glaubitz:
>>> On Nov 5, 2015, at 5:31 PM, Michael Biebl <biebl at debian.org>
>>> wrote:
> 
>>>> Depending on what actually is broken, a workaround could also
>>>> be to make that functionality in gold on sparc a nop instead of
>>>> generating broken code.
>>>
>>> Which would probably involve much more patching and hacking than
>>> just using the working linker in the first place.
> 
>> Well, depending on how broken gold on sparc* actually is, wouldn't
>> it be an option to simply make /usr/bin/ld.gold a symlink to
>> ld.bfd? That workaround would be trivial to implement as well.
> 
> I'll try something similar now. I'll build binutils on sparc* explicitly
> without gold now. Do you know whether systemd will still build fine on
> systems where gold is not available at all or will it fail?
> 
> If systemd will still build fine in such cases and default to bfd, then
> I'll happily patch binutils instead.

A quick test-build, where I removed
 /usr/lib/gold-ld/
 /usr/bin/gold
 /usr/bin/ld.gold

was successful on amd64. So this approach might work.
Instead of removing gold on sparc, it might be better though to simply
rename it to something like gold-experimental or so.
So users/devs who explicitly want to test the linker could do so easily.


>> This would have the additional benefit that this workaround would
>> apply for all packages that use gold and this workaround can be
>> dropped exactly when gold has been fixed.
> 
> Yeah, I'll look into that now. I have done more digging and it actually
> seems that gold results in Qt5 FTBFS on sparc64 now. But I haven't fully
> confirmed that now.
> 
>>>> Don't you think we should first understand what is broken and
>>>> what the impact is?
>>>
>>> Well, gold is missing support for SPARCs STT-REGISTER
> 
>> I don't actually know what that is. Does that mean every executable
>> that has been built with gold is broken on sparc?
> 
> Looks like that. I'll do some more research now.

Btw, #790556 is marked as fixed-upstream. Apparently there are multiple
issues. The one involving STT-REGISTER is, as you are well aware, not
fixed upstream. I think it would be better to track those two issues
separately. Would be great if you can file a separate bug report against
binutils for that.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151108/7802c18a/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list